express-route-generator
Express Route Generator - Auto-activating skill for Backend Development. Triggers on: express route generator, express route generator Part of the Backend Development skill category.
35
3%
Does it follow best practices?
Impact
93%
1.00xAverage 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/express-route-generator/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 essentially a title repeated with boilerplate metadata rather than a functional skill description. It lacks concrete actions, natural trigger terms, and any 'Use when...' guidance, making it nearly useless for Claude to distinguish when to select this skill from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Express.js route files with CRUD endpoints, middleware setup, request validation, and error handling.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create Express routes, add API endpoints, scaffold a REST API, set up an Express router, or generate route handlers.'
Include natural keyword variations users would say: 'Express.js', 'API routes', 'REST endpoints', 'route handler', 'router', 'CRUD routes', 'Node.js backend'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Express Route Generator') but does not describe any concrete actions. There are no specific capabilities listed like 'generates CRUD endpoints', 'creates middleware', or 'scaffolds route files'. | 1 / 3 |
Completeness | The 'what' is extremely vague (just the name 'Express Route Generator') and the 'when' is missing entirely. There is no 'Use when...' clause or equivalent explicit trigger guidance. The description fails to answer either question meaningfully. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'express route generator' repeated twice. Missing natural variations users would say like 'create express routes', 'add API endpoint', 'scaffold routes', 'Express.js', 'REST API', 'router', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Express' and 'Route Generator' provides some specificity that distinguishes it from generic backend skills, but the lack of detail about what exactly it generates could cause overlap with other Express.js or backend scaffolding skills. | 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 is a hollow template with no actual instructional content. It repeatedly references 'express route generator' without ever defining what that means, providing code examples, or giving any actionable guidance. It reads as auto-generated boilerplate that would provide zero value to Claude.
Suggestions
Add concrete, executable Express.js route code examples (e.g., a complete route file with GET/POST/PUT/DELETE handlers, middleware, and error handling).
Replace the abstract 'Capabilities' and 'When to Use' sections with an actual workflow: e.g., 1) Define route structure, 2) Generate route file, 3) Register routes in app, 4) Validate with a test request.
Include specific patterns like route parameter validation, async error wrapping, and middleware composition rather than vague claims about 'best practices'.
Remove all meta-description content (trigger phrases, 'when to use' boilerplate) that provides no instructional value and wastes tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague idea ('express route generator') without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of Express route generation. The skill describes rather than instructs, offering no executable or copy-paste-ready content whatsoever. | 1 / 3 |
Workflow Clarity | No workflow, steps, or sequence is provided. The mention of 'step-by-step guidance' in the Capabilities section is a claim with no actual steps defined. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of meta-descriptions with no references to detailed files, no structured navigation, and no meaningful content organization beyond boilerplate headings. | 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
3e83543
- 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.