error-handling

Implement structured error classification, unified responses, and secure logging across projects.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/silbaram/artifact-driven-agent --skill error-handling-silbaram
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-handling
Source: https://github.com/silbaram/artifact-driven-agent/tree/main/core/skills/error-handling
Command: npx skills add https://github.com/silbaram/artifact-driven-agent --skill error-handling-silbaram

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralize and standardize error handling and user-friendly messaging across software projects to reduce debugging time and prevent sensitive details from leaking.

Core Features & Use Cases

  • Error classification hierarchy to guide handling strategies and reporting (ValidationError, NotFoundError, AuthenticationError, etc.).
  • Unified error response formats that avoid internal details while delivering actionable feedback to users and clients.
  • Structured logging with contextual data to streamline debugging, monitoring, and incident response.
  • Retry and resilience patterns with clear fallbacks for transient failures and graceful degradation.

Quick Start

Identify an error-prone operation in your codebase and apply the standard error-handling patterns described above.

Frequently Asked Questions about error-handling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement consistent error handling and logging across an application?

Standardize application error handling by defining a classification hierarchy, unified response formats, and structured logging with contextual data to streamline debugging and prevent sensitive details from leaking.

What is the best way to prevent sensitive information from leaking in error responses?

Prevent sensitive data leaks in error responses by adopting unified response formats that deliver actionable user feedback while safely exposing only non-sensitive details through structured logging.

How do I set up retry policies for transient failures without causing cascading system crashes?

Implement resilience patterns and retry policies with clear fallbacks to manage transient failures gracefully, ensuring system stability through structured error classification and graceful degradation strategies.

When do I need a standardized error classification hierarchy in software development?

You need a standardized error classification hierarchy when guiding handling strategies and reporting for distinct types like ValidationError or NotFoundError to ensure consistent application behavior and feedback.

Does this approach to error handling work for application workflows requiring structured incident response?

Yes, this approach works for application workflows requiring structured incident response by providing robust logging with contextual data, standardized response formats, and clear error classification strategies.