error

What This Skill Does

The error skill serves as a comprehensive knowledge base and command-line interface for best practices in software resilience, debugging, and fault tolerance. It acts as an expert assistant for developers designing robust systems, providing immediate access to industry-standard patterns such as exponential backoff, circuit breaker implementation, and structured logging strategies. Instead of manually searching through documentation for HTTP status code definitions or debugging methodologies, the skill streamlines these tasks by providing context-aware commands that guide users through error-handling implementation and root cause analysis.

Installation

To integrate the error handling documentation into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/ckchzh/error

Once installed, the skill will be available to respond to system commands via scripts/script.sh. You can configure the local storage directory by setting the ERROR_DIR environment variable to point to your preferred path.

Use Cases

This skill is essential for:

• Architects designing fault-tolerant distributed systems.
• Junior to Senior developers building APIs who need to ensure correct semantic HTTP status code usage.
• DevOps engineers performing post-mortem root cause analysis on production incidents.
• UI/UX teams needing guidance on crafting user-friendly error messages that balance clarity with security.
• Backend developers implementing retry logic to prevent cascading failures in microservice architectures.

Example Prompts

1. "@error run the retry strategy guide, I need to understand how to implement jitter to prevent thundering herd problems."
2. "@error check my current implementation against the production checklist for error handling."
3. "@error explain the difference between a 401 and 403 HTTP status code and tell me which one I should use for invalid tokens."

Tips & Limitations

To maximize the utility of this skill, ensure that your log formats are compatible with the structured logging standards discussed in the logging command. Remember that while this tool provides structural templates and architectural guidance, it is not a diagnostic agent that can directly access your production logs unless explicitly granted scope. Always prioritize security by ensuring that detailed error messages returned to clients do not leak sensitive stack traces or database architecture details, a practice outlined in the messages documentation. Use the checklist tool during your deployment pipeline to catch common pitfalls early.