error-handler-middleware
Error Handler Middleware - Auto-activating skill for Backend Development. Triggers on: error handler middleware, error handler middleware Part of the Backend Development skill category.
36
Quality
3%
Does it follow best practices?
Impact
99%
1.03xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/error-handler-middleware/SKILL.mdQuality
Discovery
7%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 description is severely underdeveloped, consisting only of a title and category metadata without any substantive content. It fails to describe what the skill does, when to use it, or provide natural trigger terms that users would actually say. The repeated trigger term suggests auto-generated content that wasn't properly reviewed.
Suggestions
Add specific actions the skill performs, e.g., 'Creates error handling middleware that catches exceptions, formats error responses, and logs errors with stack traces'
Add a 'Use when...' clause with natural trigger terms like 'error handling', 'catch errors', 'exception middleware', 'error responses', '500 errors', 'try-catch'
Include framework-specific context if applicable (e.g., Express.js, Koa, FastAPI) to improve distinctiveness and help Claude select the right skill
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the concept 'Error Handler Middleware' without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what the skill actually does (e.g., catches exceptions, formats error responses, logs errors). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the concept, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('error handler middleware' repeated twice) and overly specific/technical. Missing natural variations users might say like 'error handling', 'catch errors', 'exception handling', 'error responses', or 'middleware errors'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'error handler middleware' is somewhat specific to backend development, the lack of detail means it could overlap with general error handling skills, logging skills, or other middleware-related skills. The Backend Development category provides some context but isn't sufficient. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a placeholder template with no actual instructional value. It describes what a skill should do rather than providing any concrete guidance on implementing error handler middleware. The content contains zero executable code, no specific patterns, and no actionable steps.
Suggestions
Add concrete, executable code examples for error handler middleware in at least one language (Node.js, Python, or Go) showing actual implementation patterns
Include specific error handling patterns such as centralized error handling, error classification, logging integration, and response formatting
Provide a clear workflow with steps: 1) Create error classes, 2) Implement middleware, 3) Register middleware, 4) Test error scenarios
Remove the meta-description sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actual technical content that teaches implementation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no actual technical substance. It explains what the skill does in abstract terms without providing any concrete implementation details, wasting tokens on meta-description rather than actionable content. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The content only describes what the skill 'could' do (provides guidance, generates code, validates outputs) without actually doing any of it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no validation checkpoints, and no actual process for implementing error handler middleware. The content is purely descriptive metadata. | 1 / 3 |
Progressive Disclosure | No structure for progressive disclosure exists. There are no references to detailed documentation, no examples, and no links to related materials. The content is a shallow placeholder with no depth. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
994edc4
- 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.