Skip to main content

Error Handling Patterns

Skill Verified Active

Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.

Purpose

Master error handling patterns across languages to build resilient applications by understanding exceptions, Result types, error propagation, and graceful degradation.

Features

  • Explains error handling philosophies (exceptions vs. Result types)
  • Details error categories (recoverable vs. unrecoverable)
  • Provides language-specific patterns (Python, TS/JS, Rust, Go)
  • Illustrates universal patterns (circuit breaker, error aggregation, graceful degradation)
  • Offers best practices and common pitfalls

Use Cases

  • Implementing error handling in new features
  • Designing error-resilient APIs
  • Debugging production issues
  • Improving application reliability and creating better error messages

Non-Goals

  • Implementing specific error handling for frameworks not explicitly mentioned
  • Providing runtime error handling for the skill itself
  • Covering all possible edge cases for every language and scenario

Installation

First, add the marketplace

/plugin marketplace add wshobson/agents
/plugin install developer-essentials@claude-code-workflows

Quality Score

Verified
95 /100
Analyzed about 14 hours ago

Trust Signals

Last commit2 days ago
Stars35.3k
LicenseMIT
Status
View Source

Similar Extensions

Csharp Async

100

Get best practices for C# async programming

Skill
github

Circuit Breaker Pattern

100

Implement circuit breaker logic for agentic tool calls — tracking tool health, transitioning between closed/open/half-open states, reducing task scope when tools fail, routing to alternatives via capability maps, and enforcing failure budgets to prevent error accumulation. Separates orchestration (deciding what to attempt) from execution (calling tools), following the expeditor pattern. Use when building agents that depend on multiple tools with varying reliability, designing fault-tolerant agentic workflows, recovering gracefully from tool outages mid-task, or hardening existing agents against cascading tool failures.

Skill
pjt222

Neon Postgres

100

Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.

Skill
neondatabase

Sdk Dx

100

Design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: "SDK design", "developer experience", "API design", "SDK DX", "error messages", "type safety", "IDE integration", "SDK versioning", "migration guides", "client library design", "making SDKs feel native", "SDK best practices"

Skill
jonathimer

Dart Matcher Best Practices

100

Best practices for using `expect` and `package:matcher`. Focuses on readable assertions, proper matcher selection, and avoiding common pitfalls.

Skill
flutter

Golang Concurrency Patterns

100

Go concurrency patterns for production services: context cancellation, errgroup, worker pools, bounded parallelism, fan-in/fan-out, and common race/deadlock pitfalls

Skill
bobmatnyc

© 2025 SkillRepo · Find the right skill, skip the noise.