fastapi
REST API and WebSocket development with FastAPI emphasizing security, performance, and async patterns
68
58%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/fastapi/SKILL.mdQuality
Discovery
32%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 identifies the technology stack (FastAPI) and general concerns (security, performance, async) but lacks concrete actions and explicit trigger guidance. It reads more like a tagline than a functional skill description that would help Claude choose it from a large skill library.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when building APIs with FastAPI, creating REST endpoints, implementing WebSocket connections, or when the user mentions FastAPI, Pydantic, or async Python web development'.
List specific concrete actions such as 'Create REST endpoints, implement authentication/authorization, handle WebSocket connections, define Pydantic models, configure middleware'.
Include common user terms and file extensions like 'Python backend', 'API routes', 'real-time communication', '.py files with FastAPI imports'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (FastAPI, REST API, WebSocket) and mentions some qualities (security, performance, async patterns), but doesn't list concrete actions like 'create endpoints', 'implement authentication', or 'handle websocket connections'. | 2 / 3 |
Completeness | Describes what domain it covers but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. The rubric caps completeness at 2 for missing this, and the 'what' is also weak. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'REST API', 'WebSocket', 'FastAPI', and 'async' that users might mention, but misses common variations like 'API endpoints', 'backend', 'Python web framework', or 'real-time'. | 2 / 3 |
Distinctiveness Conflict Risk | FastAPI is specific enough to distinguish from general Python or other web frameworks, but 'REST API' and 'WebSocket development' could overlap with skills for other frameworks like Flask, Django, or Express. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%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, comprehensive FastAPI skill with excellent actionability - nearly all patterns include complete, executable code examples with clear BAD/GOOD comparisons. The TDD workflow and pre-deployment checklist provide good validation checkpoints. Minor issues include some redundancy (duplicate section 6, repeated security reminders) and the skill could be slightly more concise by removing overlapping content.
Suggestions
Remove duplicate section 6 (Testing & Validation appears twice with different content) and consolidate testing examples
Trim the summary section which largely repeats the security reminders already covered in detail throughout the document
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., summary section repeats earlier points, section 6 appears twice with different content, version tables and dependency lists overlap). Some explanatory text could be trimmed, though most content is actionable. | 2 / 3 |
Actionability | Excellent executable code examples throughout - JWT authentication, rate limiting, file upload validation, connection pooling, and testing patterns are all copy-paste ready with complete implementations. Anti-patterns show clear BAD/GOOD comparisons. | 3 / 3 |
Workflow Clarity | Clear TDD workflow with explicit steps (write test → implement → refactor → verify). The verification step includes specific commands (pytest, mypy, bandit) with explicit 'all must pass before committing' checkpoint. Pre-deployment checklist provides validation gates. | 3 / 3 |
Progressive Disclosure | Well-organized with clear file structure at the top pointing to reference files (security-examples.md, advanced-patterns.md, threat-model.md). Content is appropriately split with the main file covering core patterns and references for deeper dives. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
68%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 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (684 lines); consider splitting into references/ and linking | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 11 / 16 Passed | |
- Repository
- martinholovsky/claude-skills-generator
- Commit
1086ef2
- 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.