api-error-handling
Implements standardized API error responses with proper status codes, logging, and user-friendly messages. Use when building production APIs, implementing error recovery patterns, or integrating error monitoring services.
88
82%
Does it follow best practices?
Impact
97%
1.49xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
77%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured description that clearly articulates specific capabilities and includes explicit 'Use when' guidance. The main weakness is moderate trigger term coverage - it uses technical but somewhat narrow terminology that may miss common user phrasings for error handling needs.
Suggestions
Add more natural trigger terms users might say, such as 'exception handling', 'HTTP errors', '4xx/5xx responses', or 'error middleware'
Consider adding file type or framework hints (e.g., 'REST APIs', 'Express', 'FastAPI') to improve distinctiveness from general API skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'standardized API error responses', 'proper status codes', 'logging', and 'user-friendly messages'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('implements standardized API error responses with proper status codes, logging, and user-friendly messages') and when ('Use when building production APIs, implementing error recovery patterns, or integrating error monitoring services'). | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'API', 'error responses', 'status codes', 'error monitoring', but misses common variations users might say like 'exception handling', 'HTTP errors', '500 errors', '4xx', or 'error middleware'. | 2 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to API error handling, but could overlap with general API development skills or logging/monitoring skills. The 'production APIs' trigger is somewhat broad. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong skill with excellent code examples and efficient token usage. The error class, global handler, and circuit breaker implementations are production-ready. The main weakness is the lack of explicit workflow guidance showing how to integrate these components together or validate the implementation.
Suggestions
Add a brief integration workflow section showing the sequence: 1) Define error classes, 2) Implement global handler, 3) Test error responses, 4) Add circuit breaker for external calls
Include a simple validation step or test example to verify error handling is working correctly (e.g., curl command showing expected error response)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient with no unnecessary explanations. Every section provides concrete value without explaining what APIs or error handling are—assumes Claude's competence. | 3 / 3 |
Actionability | Provides fully executable JavaScript code for error classes, global error handlers, and circuit breaker pattern. Code is copy-paste ready with complete implementations. | 3 / 3 |
Workflow Clarity | Provides individual components but lacks explicit workflow sequencing for implementing error handling end-to-end. No validation checkpoints or step-by-step integration guide showing how pieces connect. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, concise overview content, and appropriate reference to external file for Python/Flask implementation. Single-level deep reference is clearly signaled. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
90d6bd7
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.