fastapi-templates
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
78
52%
Does it follow best practices?
Impact
95%
1.11xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/api-scaffolding/skills/fastapi-templates/SKILL.mdQuality
Discovery
75%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 is a solid description that clearly identifies its niche (FastAPI project creation) and includes an explicit 'Use when' clause. Its main weaknesses are that the capability descriptions lean toward architectural qualities rather than concrete actions, and the trigger terms could cover more natural variations of how users might request API development help.
Suggestions
Add more concrete actions like 'scaffold routes, configure middleware, set up Pydantic models, define endpoints' to increase specificity.
Expand trigger terms to include common variations like 'REST API', 'Python API', 'web server', 'ASGI', or 'endpoints' that users might naturally use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (FastAPI) and some patterns (async patterns, dependency injection, error handling), but doesn't list multiple concrete actions like 'create routes, configure middleware, set up database models'. The actions are more about qualities of the output than specific tasks. | 2 / 3 |
Completeness | Clearly answers both 'what' (create production-ready FastAPI projects with async patterns, dependency injection, error handling) and 'when' (when building new FastAPI applications or setting up backend API projects) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes 'FastAPI', 'backend API', and 'API projects' which are relevant keywords, but misses common variations users might say like 'REST API', 'Python API', 'web server', 'endpoints', or 'ASGI'. Coverage of natural terms is incomplete. | 2 / 3 |
Distinctiveness Conflict Risk | FastAPI is a specific framework, making this clearly distinguishable from generic web framework skills, Django skills, Flask skills, or general Python skills. The triggers are distinct enough to avoid conflicts. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
29%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, executable FastAPI code examples covering common patterns (CRUD, auth, testing), which is its primary strength. However, it is excessively verbose for a skill file—explaining concepts Claude already knows, lacking any workflow sequencing for project setup, and dumping everything into a single monolithic document without progressive disclosure. It reads more like a tutorial than an actionable skill reference.
Suggestions
Remove the 'Core Concepts' section entirely and the 'When to Use This Skill' bullets—Claude knows what DI, async patterns, and project structure are. Replace with a minimal project scaffold command or checklist.
Add a clear numbered workflow: 1) Create project structure, 2) Install dependencies (with requirements.txt content), 3) Configure database, 4) Run migrations, 5) Verify with test suite—including validation checkpoints at each step.
Split the large code patterns into separate referenced files (e.g., REPOSITORY.md, AUTH.md, TESTING.md) and keep SKILL.md as a concise overview with the main.py pattern and links to detailed patterns.
Add a concrete 'Quick Start' section at the top showing the minimal steps to get a running FastAPI app with one endpoint, before diving into advanced patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines. Explains concepts Claude already knows well (what dependency injection is, what async patterns are, project structure conventions). The 'Core Concepts' section is entirely unnecessary filler. The 'When to Use This Skill' bullet list adds no value. Much of this could be condensed to key patterns with brief annotations. | 1 / 3 |
Actionability | The code examples are concrete, executable, and copy-paste ready. Complete implementations are provided for the repository pattern, service layer, endpoints, authentication, database setup, and testing with proper imports and type hints throughout. | 3 / 3 |
Workflow Clarity | There is no clear workflow for actually setting up a project. The patterns are presented as isolated code blocks without sequencing, validation checkpoints, or guidance on order of operations. No instructions for installing dependencies, running migrations, or verifying the setup works. For a project template skill, missing setup/verification steps is a significant gap. | 1 / 3 |
Progressive Disclosure | Monolithic wall of code with no references to external files despite the content being long enough to warrant splitting. The repository pattern, service layer, auth, and testing sections could each be separate referenced files. No bundle files exist to support progressive disclosure. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (541 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
112197c
- 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.