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.
86
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 solid description that clearly states what the skill does and when to use it, with specific capabilities listed. Its main weaknesses are moderate trigger term coverage (missing common user phrasings like 'exception handling', 'HTTP errors', or specific status codes) and some potential overlap with broader API development or logging skills.
Suggestions
Add more natural trigger terms users might say, such as 'exception handling', 'HTTP errors', '500 error', '404', 'REST error handling', or 'error middleware'.
Sharpen distinctiveness by specifying what differentiates this from general API development or logging skills, e.g., mentioning specific patterns like centralized error handlers or error response schemas.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'standardized API error responses', 'proper status codes', 'logging', 'user-friendly messages'. These are concrete, actionable capabilities rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (implements standardized API error responses with status codes, logging, and user-friendly messages) and 'when' (explicit 'Use when' clause covering building production APIs, implementing error recovery patterns, or integrating error monitoring services). | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'API', 'error responses', 'status codes', 'error monitoring', 'error recovery'. However, it misses common natural variations users might say such as 'exception handling', 'HTTP errors', '500 error', '404', 'REST API errors', or 'error middleware'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on API error responses is fairly specific, but terms like 'production APIs' and 'logging' could overlap with general API development skills, logging skills, or monitoring skills. The niche of 'API error handling' is reasonably distinct but not uniquely carved out. | 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 well-crafted skill that provides concrete, executable code examples with minimal verbosity. Its main weakness is the lack of a clear integration workflow—it presents building blocks without sequencing how to wire them together or verify correctness. The progressive disclosure is well done with a clean reference to additional language implementations.
Suggestions
Add a brief integration workflow showing the order of steps: 1) Define error classes, 2) Register global handler, 3) Use in routes, 4) Verify with a test request to confirm error format
Include a quick validation step such as a curl command or test snippet to verify the error response format is working correctly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It jumps straight into the error response format and executable code without explaining what APIs are, what error handling is, or other concepts Claude already knows. The best practices section is a concise bullet list with no fluff. | 3 / 3 |
Actionability | Provides fully executable Node.js code for the ApiError class, global error handler middleware, and circuit breaker pattern. The JSON response format is concrete and copy-paste ready. Static factory methods show specific usage patterns. | 3 / 3 |
Workflow Clarity | The skill presents components (error class, handler, circuit breaker) but doesn't clearly sequence how to integrate them into a project workflow. There's no explicit validation step to verify error handling works correctly (e.g., testing error responses), and no guidance on the order of implementation or integration checkpoints. | 2 / 3 |
Progressive Disclosure | The main file provides a clear overview with executable Node.js examples, then appropriately references a separate file for Python/Flask implementations and advanced patterns like Sentry integration. References are one level deep and clearly signaled with a descriptive list. | 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
88da5ff
- 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.