fastapi-router-creator
Fastapi Router Creator - Auto-activating skill for Backend Development. Triggers on: fastapi router creator, fastapi router creator Part of the Backend Development skill category.
33
3%
Does it follow best practices?
Impact
84%
1.06xAverage 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/fastapi-router-creator/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 skill title restated with boilerplate category metadata. It provides no concrete actions, no natural trigger terms beyond the skill name, and no explicit guidance on when Claude should select it. It would be nearly indistinguishable in a large skill library and fails to help Claude make informed selection decisions.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates FastAPI router modules with endpoint handlers, request/response models, and dependency injection setup.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create API routes, add FastAPI endpoints, scaffold a router, or build REST API handlers in Python.'
Include common keyword variations users might say: 'FastAPI', 'API endpoint', 'route handler', 'REST API', 'CRUD endpoints', 'router file', '.py API'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Fastapi Router Creator') and mentions 'Backend Development' but lists no concrete actions like 'creates route handlers', 'generates endpoint boilerplate', or 'scaffolds CRUD routes'. It is essentially a title repeated with no actionable detail. | 1 / 3 |
Completeness | There is no explicit 'what does this do' beyond the name, and no 'when should Claude use it' clause. Both dimensions are essentially absent, making this description minimally informative. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the exact skill name repeated twice ('fastapi router creator'). It misses natural user phrases like 'create an API endpoint', 'add a route', 'FastAPI', 'REST endpoint', 'router', 'CRUD', or '.py API file'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'FastAPI' and 'router' gives it some domain specificity that distinguishes it from generic backend skills, but the lack of concrete actions or explicit triggers means it could still overlap with other backend or API-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 an empty shell with no actual instructional content. It repeatedly references 'fastapi router creator' without ever defining what a FastAPI router is, how to create one, or providing any code examples. The entire file reads as auto-generated boilerplate with zero educational or operational value.
Suggestions
Replace the abstract descriptions with concrete, executable FastAPI router code examples (e.g., a complete router with CRUD endpoints using APIRouter).
Add a step-by-step workflow for creating a FastAPI router: define the router, add endpoints, register it in the app, and validate with a test request.
Include specific patterns and best practices such as dependency injection, response models, error handling, and file organization for routers.
Remove all meta-sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the task—these waste tokens on information Claude doesn't need.
| 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 'fastapi router creator' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no FastAPI router patterns, no executable commands, no specific API structures. The content describes rather than instructs, offering nothing Claude could act on. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. Sections like 'When to Use', 'Capabilities', and 'Example Triggers' all restate the same vague information. No references to detailed materials or external files. | 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.