python-fastapi-patterns
FastAPI web framework patterns. Triggers on: fastapi, api endpoint, dependency injection, pydantic model, openapi, swagger, starlette, async api, rest api, uvicorn.
81
75%
Does it follow best practices?
Impact
92%
1.53xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xdarkmatter/claude-mods/python-fastapi-patterns/SKILL.mdQuality
Discovery
62%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger term coverage and distinctiveness with a comprehensive list of FastAPI-specific keywords, but critically lacks specificity about what the skill actually does. 'FastAPI web framework patterns' is too vague — it should enumerate concrete actions like creating endpoints, defining Pydantic models, setting up dependency injection, or configuring middleware.
Suggestions
Replace 'FastAPI web framework patterns' with specific actions like 'Creates FastAPI endpoints, defines Pydantic request/response models, configures dependency injection, sets up middleware and authentication.'
Add a 'Use when...' clause that bridges the what and when, e.g., 'Use when building or modifying REST APIs with FastAPI, defining data validation models, or configuring async API servers.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'FastAPI web framework patterns' which is vague and abstract. It does not list any concrete actions like 'create endpoints', 'define routes', 'configure middleware', or 'validate request bodies'. No specific capabilities are described. | 1 / 3 |
Completeness | The 'when' is addressed via the 'Triggers on:' clause with explicit trigger terms, but the 'what' is extremely weak — 'FastAPI web framework patterns' doesn't explain what the skill actually does. It lacks a proper 'Use when...' clause but the triggers partially compensate. Capped at 2 due to the weak 'what'. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'fastapi', 'api endpoint', 'dependency injection', 'pydantic model', 'openapi', 'swagger', 'starlette', 'async api', 'rest api', 'uvicorn'. These are terms users would naturally use when working with FastAPI. | 3 / 3 |
Distinctiveness Conflict Risk | The trigger terms are highly specific to the FastAPI ecosystem (fastapi, starlette, uvicorn, pydantic model) making it clearly distinguishable from generic API or web framework skills. Unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong reference-style skill that provides clean, executable FastAPI patterns with excellent progressive disclosure and token efficiency. The main weakness is the lack of an explicit workflow or sequencing guidance for building an API from scratch, though for a pattern-reference skill this is a minor gap. The quick reference table and well-organized sections make it highly usable.
Suggestions
Consider adding a brief 2-3 step workflow at the top (e.g., '1. Scaffold with script, 2. Define models, 3. Add routes, 4. Test with `uvicorn app:app --reload`') to provide sequencing guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It jumps straight into executable code patterns without explaining what FastAPI is, what REST APIs are, or other concepts Claude already knows. Every section delivers concrete patterns with minimal prose. | 3 / 3 |
Actionability | All code examples are fully executable Python with proper imports, type annotations, and realistic patterns. The examples cover the core FastAPI patterns (models, DI, routing, exceptions) with copy-paste ready code and a useful quick reference table. | 3 / 3 |
Workflow Clarity | The skill presents individual patterns clearly but lacks an explicit workflow for building an API end-to-end. There's no sequencing guidance (e.g., 'start with models, then routes, then DI') and no validation checkpoints for testing or verifying the API works. The scaffold script is mentioned but not integrated into a workflow. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview of core patterns inline, then clear one-level-deep references to advanced topics (DI patterns, middleware, validation, background tasks). The See Also section with prerequisites and related skills provides good navigation context. | 3 / 3 |
Total | 11 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- NeverSight/skills_feed
- Commit
c50d4b5
- 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.