jbvc/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.
59
59%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 capabilities listed are more about architectural qualities than concrete actions, and the trigger terms could be broader to capture more natural user phrasings like 'REST API' or 'Python web server'.
Suggestions
Add more concrete actions like 'scaffold routes, configure middleware, set up Pydantic models, define database schemas' to increase specificity.
Expand trigger terms to include natural variations like 'REST API', 'Python API', 'web server', 'endpoints', or 'ASGI app'.
| 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', 'ASGI', or 'uvicorn'. | 2 / 3 |
Distinctiveness Conflict Risk | FastAPI is a specific framework, making this clearly distinguishable from general Python skills, Django skills, or Flask skills. The triggers are narrow enough to avoid conflicts with other backend or API-related skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
22%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 that defers all substantive content to an external file while providing only generic, non-actionable instructions in the main body. It lacks any concrete code examples, specific FastAPI patterns, project structure templates, or meaningful workflow guidance. The content fails to teach Claude anything it doesn't already know and provides no executable guidance for creating FastAPI projects.
Suggestions
Add a concrete project structure example (directory tree) and a minimal working FastAPI application code snippet directly in the SKILL.md as a quick-start section.
Replace the generic instructions ('Apply relevant best practices', 'Validate outcomes') with specific, sequenced steps for scaffolding a FastAPI project (e.g., create directory structure, set up main.py with app factory, configure middleware, add dependency injection).
Include at least one executable code example showing a core pattern like async endpoint with dependency injection or error handling middleware.
Remove the 'Do not use this skill when' section as it adds no useful information, and tighten the 'Use this skill when' to be more concise.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively short but includes generic filler like 'Do not use this skill when the task is unrelated to fastapi project templates' and vague instructions like 'Clarify goals, constraints, and required inputs' that add no value. The 'Use this skill when' section is somewhat redundant with the description. | 2 / 3 |
Actionability | There is no concrete code, no executable commands, no project structure example, no specific FastAPI patterns shown. The instructions are entirely vague ('Apply relevant best practices', 'Provide actionable steps') with zero specificity. Everything actionable is deferred to an external file. | 1 / 3 |
Workflow Clarity | There is no clear workflow or sequence of steps for creating a FastAPI project. The four bullet points under Instructions are generic platitudes ('Clarify goals', 'Apply best practices', 'Validate outcomes') with no specific sequencing, validation checkpoints, or concrete process. | 1 / 3 |
Progressive Disclosure | There is a reference to an external resource file (resources/implementation-playbook.md) which is good structure, but the SKILL.md itself contains almost no substantive overview content. It's essentially an empty shell pointing to another file rather than a useful overview with well-signaled references. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents