handling-api-errors
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill handling-api-errorsImplement standardized error handling with proper HTTP status codes and error responses. Use when implementing standardized error handling. Trigger with phrases like "add error handling", "standardize errors", or "implement error responses".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill fails to deliver on its stated purpose of implementing standardized error handling. Instead of providing concrete error handling patterns, HTTP status code mappings, and error response schemas, it offers generic API development boilerplate. The content explains nothing Claude doesn't already know and provides no actionable, copy-paste-ready code for error handling.
Suggestions
Add concrete error response schemas with specific HTTP status codes (e.g., 400 for validation errors, 404 for not found, 500 for server errors) and example JSON response structures
Include executable code examples showing error handling middleware implementation for at least one framework (e.g., Express.js error handler)
Remove generic API development prerequisites and instructions that don't relate to error handling specifically
Provide a clear mapping table of error types to HTTP status codes and standardized error response formats
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that doesn't add value. The overview repeats itself, prerequisites list obvious items Claude already knows, and the instructions are generic API development steps rather than specific error handling guidance. | 1 / 3 |
Actionability | No concrete code examples, no specific error handling patterns, no HTTP status code mappings, no error response schemas. Instructions like 'Plan error handling and validation strategies' are vague descriptions rather than executable guidance. | 1 / 3 |
Workflow Clarity | Steps are poorly organized with duplicate numbered lists (two separate '1-5' sequences), no validation checkpoints, and the workflow describes general API development rather than the specific task of implementing standardized error handling. | 1 / 3 |
Progressive Disclosure | References to external files (implementation.md, errors.md, examples.md) are present and one-level deep, but the main content is poorly organized and the skill body itself contains almost no useful information, making the references feel like deflection rather than progressive disclosure. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
82%This description is functional with good trigger term coverage and explicit 'Use when' guidance. However, the capability description is somewhat thin on specific actions, and the skill could potentially conflict with broader API or backend development skills. The description would benefit from more concrete details about what standardization entails.
Suggestions
Add more specific actions to the capability description, such as 'create error classes, configure middleware, map exceptions to status codes, format JSON error responses'
Include technology context if applicable (e.g., 'for REST APIs', 'in Express/FastAPI') to reduce conflict risk with other error handling approaches
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (error handling) and mentions some actions (HTTP status codes, error responses), but lacks comprehensive detail about what specific actions are performed (e.g., creating error classes, middleware setup, logging integration). | 2 / 3 |
Completeness | Clearly answers both what (implement standardized error handling with HTTP status codes and error responses) and when (explicit 'Use when' clause plus 'Trigger with phrases' providing clear activation guidance). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'add error handling', 'standardize errors', 'implement error responses'. Also includes relevant keywords like 'HTTP status codes' and 'error responses'. | 3 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to error handling but could overlap with general API development skills, backend framework skills, or middleware skills. The focus on 'standardized' helps but doesn't fully distinguish from other error-related skills. | 2 / 3 |
Total | 10 / 12 Passed |
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.