CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/api-error-handling/skills/api-error-handling/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with executable code examples and a well-structured format. Its main weaknesses are the lack of an explicit integration workflow showing how to wire everything together, and some unnecessary best-practice advice that Claude already knows. The progressive disclosure is well-handled with a clear reference to supplementary material.

Suggestions

Add a brief integration workflow showing the sequence: 1) Define error classes, 2) Register global handler, 3) Use in routes, 4) Verify with a test request

Remove or significantly trim the 'Best Practices' section — these are standard knowledge for Claude and consume tokens without adding value

DimensionReasoningScore

Conciseness

Mostly efficient with executable code examples, but the 'Best Practices' section contains guidance Claude already knows (e.g., 'never expose stack traces to clients', 'distinguish client errors from server errors'). The circuit breaker pattern adds useful but somewhat tangential content.

2 / 3

Actionability

Provides fully executable JavaScript 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 give clear 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 an API project. There's no validation step to verify error handling works correctly, and no explicit workflow for implementing error handling end-to-end.

2 / 3

Progressive Disclosure

Clean structure with a concise overview in the main file and a clear one-level-deep reference to python-flask.md for additional implementations. Content is well-organized into logical sections with appropriate detail levels, though the referenced bundle file doesn't actually exist.

3 / 3

Total

10

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-structured with a clear 'what' and 'when' clause, making it functionally complete. However, it could be more specific about the concrete actions it performs and include more natural trigger terms that users would actually say when needing this skill. The domain is reasonably distinct but broad enough to risk overlap with adjacent API or logging skills.

Suggestions

Add more natural trigger terms users would say, such as 'error handling', 'exception handling', 'REST API errors', '4xx/5xx responses', or 'error middleware'.

List more specific concrete actions, e.g., 'creates error handler middleware, maps exceptions to HTTP status codes, formats error payloads with error codes and messages, integrates with Sentry/Datadog'.

DimensionReasoningScore

Specificity

Names the domain (API error responses) and some actions (standardized responses, proper status codes, logging, user-friendly messages), but doesn't list multiple distinct concrete actions in detail—e.g., it doesn't specify which status codes, what logging formats, or what specific error recovery patterns.

2 / 3

Completeness

Clearly answers both 'what' (implements standardized API error responses with status codes, logging, and user-friendly messages) and 'when' (building production APIs, implementing error recovery patterns, integrating error monitoring services) with an explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Includes relevant terms like 'API error responses', 'status codes', 'error monitoring', and 'error recovery patterns', but misses common natural user phrases like 'error handling', 'exception handling', 'REST API errors', '4xx/5xx', 'error middleware', or 'try-catch'.

2 / 3

Distinctiveness Conflict Risk

Fairly specific to API error handling, but could overlap with general API development skills, logging skills, or monitoring integration skills. The scope of 'production APIs' and 'error monitoring services' is broad enough to potentially conflict with other skills.

2 / 3

Total

9

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
secondsky/claude-skills
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.