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.
Overall
score
80%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.08xAgent success when using this skill
Validation for skill structure
Discovery
85%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 strong skill description that clearly articulates specific capabilities and includes explicit 'Use when' guidance. The main weakness is trigger term coverage - it could benefit from additional natural language variations users might employ when seeking API development help. The FastAPI-specific focus provides good distinctiveness.
Suggestions
Add common trigger term variations like 'REST API', 'Python API', 'web service', or 'API endpoints' to capture users who may not specifically mention FastAPI
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create production-ready FastAPI projects', 'async patterns', 'dependency injection', and 'comprehensive error handling'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling') and when ('Use when building new FastAPI applications or setting up backend API projects') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes good terms like 'FastAPI', 'backend API projects', and 'async patterns', but missing common variations users might say like 'REST API', 'Python API', 'web service', or 'API endpoints'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on FastAPI framework with distinct triggers. Unlikely to conflict with general Python skills or other web framework skills due to explicit FastAPI focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable FastAPI skill with excellent code examples covering the full stack from configuration to testing. The main weaknesses are verbosity in introductory sections that explain concepts Claude already knows, and lack of a clear step-by-step workflow with validation checkpoints for actually setting up a new project.
Suggestions
Remove or significantly condense the 'When to Use This Skill' and 'Core Concepts' sections - Claude knows what FastAPI is and when to use it
Add a 'Quick Start Workflow' section with numbered steps and validation checkpoints (e.g., '1. Create structure, 2. Verify imports work, 3. Add database config, 4. Test connection before proceeding')
Consolidate 'Best Practices' and 'Common Pitfalls' into the relevant code patterns as inline comments rather than separate sections
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations (e.g., 'FastAPI's built-in DI system using Depends' followed by a list of what it does). The 'When to Use This Skill' section and 'Core Concepts' explanations add tokens without providing actionable value Claude doesn't already know. | 2 / 3 |
Actionability | Excellent executable code examples throughout - complete patterns for main.py, repositories, services, endpoints, security, and testing. All code is copy-paste ready with proper imports and realistic implementations. | 3 / 3 |
Workflow Clarity | While the patterns are well-organized, there's no clear workflow for setting up a new project step-by-step. Missing validation checkpoints (e.g., 'verify database connection before proceeding', 'run tests after each layer implementation'). The content presents patterns but not a sequenced process. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections progressing from project structure to implementation patterns to testing. References to external files (references/fastapi-architecture.md, assets/project-template/) are well-signaled and one level deep. | 3 / 3 |
Total | 10 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (568 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
Table of Contents
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.