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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill error-handler-middlewareOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It names the concept but fails to describe what actions the skill performs, what technologies or frameworks it supports, or when Claude should choose it over other skills. The repeated trigger term suggests auto-generated content without human refinement.
Suggestions
Add specific actions the skill performs, e.g., 'Creates error handling middleware for Express/Node.js applications, configures custom error responses, implements error logging and monitoring hooks.'
Include a 'Use when...' clause with natural trigger terms like 'Use when setting up error handling, catching exceptions in APIs, creating custom error responses, or implementing try-catch middleware.'
Specify the technology stack or framework (Express, Koa, Fastify, etc.) to distinguish from other error handling skills and reduce conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the concept 'Error Handler Middleware' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs like 'creates', 'configures', 'handles', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the concept, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'error handler middleware' repeated twice, which is technical jargon. Missing natural variations users might say like 'error handling', 'catch errors', 'exception handling', 'error responses', or framework-specific terms. | 1 / 3 |
Distinctiveness Conflict Risk | While 'error handler middleware' is somewhat specific to backend development, it could overlap with general error handling skills, logging skills, or framework-specific middleware skills. The lack of specificity about what kind of middleware or framework increases conflict risk. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is entirely meta-description with no actionable content. It describes what the skill should do without providing any actual implementation guidance, code examples, or concrete instructions for error handler middleware in any of the mentioned languages (Node.js, Python, Go). The content is essentially a placeholder that would provide no value to Claude when activated.
Suggestions
Add concrete, executable code examples for error handler middleware in at least one language (e.g., Express.js error middleware, FastAPI exception handlers, or Go error handling patterns)
Replace the 'Capabilities' section with actual implementation steps showing how to create, configure, and use error handler middleware
Include specific patterns like centralized error handling, error logging, error response formatting, and async error catching with copy-paste ready code
Add a quick reference section with common error types and how to handle them (validation errors, authentication errors, database errors, etc.)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains what the skill does rather than how to do it. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The entire content describes the skill abstractly without showing any actual error handler middleware implementation patterns, code examples, or specific instructions. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for implementing error handler middleware in any language or framework. | 1 / 3 |
Progressive Disclosure | No structure for progressive disclosure exists. There are no references to detailed documentation, no code examples to expand upon, and no links to language-specific implementations despite mentioning Node.js, Python, and Go. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.