fastapi-expert
tessl i github:jeffallan/claude-skills --skill fastapi-expertUse when building high-performance async Python APIs with FastAPI and Pydantic V2. Invoke for async SQLAlchemy, JWT authentication, WebSockets, OpenAPI documentation.
Review Score
67%
Validation Score
12/16
Implementation Score
42%
Activation Score
90%
Generated
Validation
Total
12/16Score
Passed| Criteria | Score |
|---|---|
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata |
body_examples | No examples detected (no code fences and no 'Example' wording) |
Implementation
Suggestions 3
Score
42%Overall Assessment
The skill has excellent organization and progressive disclosure with a well-structured reference table, but critically lacks any executable code examples despite being a technical API development skill. The content describes what to do rather than showing how to do it, making it more of a checklist than actionable guidance.
Suggestions
- Add a Quick Start section with a minimal executable FastAPI endpoint example showing Pydantic V2 schema, async endpoint, and dependency injection
- Include at least one concrete code example for the MUST DO items (e.g., show the Annotated pattern for dependency injection, show field_validator syntax)
- Add validation checkpoints to the Core Workflow (e.g., 'Run schema tests before implementing endpoints', 'Verify OpenAPI docs render correctly')
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The skill includes some unnecessary framing ('Senior FastAPI specialist with 10+ years experience') and the 'Role Definition' section explains what Claude should already understand. The MUST DO/MUST NOT lists are useful but could be tighter. |
Actionability | 1/3 | No executable code examples anywhere. The skill describes what to do ('Use Pydantic V2 syntax', 'Use async/await') but provides zero concrete code snippets, commands, or copy-paste ready examples. |
Workflow Clarity | 2/3 | The 5-step core workflow provides a clear sequence but lacks validation checkpoints. No feedback loops for error recovery, no explicit verification steps between stages like 'test your schema before implementing endpoints'. |
Progressive Disclosure | 3/3 | Excellent structure with a clear reference table pointing to specific files for detailed topics. References are one level deep, well-organized by topic, and clearly signal when to load each reference. |
Activation
Suggestions 1
Score
90%Overall Assessment
This is a strong skill description with excellent trigger terms and clear 'when to use' guidance. The main weakness is that it lists technologies rather than concrete actions - it tells you what tools are involved but not what specific tasks it helps accomplish (e.g., 'create REST endpoints', 'define request/response models', 'implement auth middleware').
Suggestions
- Add concrete actions before the technology list, e.g., 'Create REST endpoints, define request/response schemas, implement authentication middleware' to improve specificity
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | Names the domain (async Python APIs) and mentions specific technologies (FastAPI, Pydantic V2, SQLAlchemy, JWT, WebSockets, OpenAPI), but doesn't list concrete actions like 'create endpoints', 'define schemas', or 'implement authentication flows'. |
Completeness | 3/3 | Clearly answers both what (building async Python APIs with specific technologies) and when ('Use when building...', 'Invoke for...'). Has explicit trigger guidance with 'Use when' and 'Invoke for' clauses. |
Trigger Term Quality | 3/3 | Excellent coverage of natural terms users would say: 'FastAPI', 'Pydantic', 'async', 'SQLAlchemy', 'JWT authentication', 'WebSockets', 'OpenAPI', 'API'. These are all terms developers naturally use when working in this domain. |
Distinctiveness Conflict Risk | 3/3 | Very distinct niche combining FastAPI + Pydantic V2 + async patterns. The specific technology stack (FastAPI, not Flask/Django; Pydantic V2 specifically) creates clear boundaries unlikely to conflict with general Python or other web framework skills. |