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 as a description with no substantive content. It lacks concrete actions, meaningful trigger terms, and explicit guidance on when Claude should select this skill. The duplicate trigger term and boilerplate category mention add no value.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Express.js route handlers, creates CRUD endpoints, scaffolds middleware and router files with proper error handling.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks to create Express routes, add API endpoints, scaffold REST APIs, or generate route handlers for Node.js/Express.js applications.'
Include natural keyword variations users would say: 'express routes', 'API endpoints', 'REST routes', 'Node.js router', 'route handler', '.js routes', 'Express.js'.
| 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 description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a redundant restatement of the skill name rather than explicit trigger guidance. There is no 'Use when...' clause with meaningful context. | 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 'Backend Development' is broad and could overlap with many other backend-related 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 essentially a placeholder template with no actual technical content. It repeatedly references 'express route generator' without ever defining what that means, providing code examples, or giving any actionable instructions. It fails on every dimension because it contains zero substance—no Express.js route code, no patterns, no commands, no workflows.
Suggestions
Add concrete, executable Express.js route generation code examples (e.g., a complete route file with GET/POST/PUT/DELETE handlers, middleware, and error handling).
Replace the meta-description sections ('When to Use', 'Capabilities', 'Example Triggers') with actual step-by-step instructions for generating routes, including validation and testing steps.
Include a quick-start section with a copy-paste ready Express route template and a clear workflow (e.g., 1. Define route, 2. Add middleware, 3. Implement handler, 4. Add error handling, 5. Register in app).
If advanced patterns exist (e.g., route factories, parameterized routes, authentication middleware), reference them via separate files with clear one-level-deep links.
| 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 information about 'express route generator' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no commands, no Express route patterns, no executable snippets. The skill describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow, steps, or sequence of any kind is present. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any procedural content whatsoever. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed files, no layered organization, and the sections are redundant rather than progressively informative. | 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
3076d78
- 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.