maria/fastapi
FastAPI framework with Pydantic v2 patterns, PII sanitisation, and practical workflows
93
Quality
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
run-check-server
skills/run-check-server/SKILL.md
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 well-crafted skill description that clearly articulates specific capabilities and includes explicit 'Use when' guidance. The description effectively targets FastAPI-specific workflows. Minor improvement could be made by expanding trigger terms to include related vocabulary users might naturally use.
Suggestions
Consider adding common related terms users might say: 'uvicorn', 'swagger', 'API server', 'REST endpoints', or 'OpenAPI docs'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Start a FastAPI dev server, verify docs and OpenAPI schema, test endpoints, and run pytest' - these are all distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Start a FastAPI dev server, verify docs and OpenAPI schema, test endpoints, and run pytest') and when ('Use when running, checking, or debugging a FastAPI application') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes good terms like 'FastAPI', 'dev server', 'pytest', 'endpoints', but missing common variations users might say like 'API server', 'uvicorn', 'swagger', 'REST API', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on FastAPI applications with distinct triggers; unlikely to conflict with general Python, Django, or Flask skills due to explicit FastAPI mentions throughout. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates strong technical writing. It provides a complete, actionable workflow for running and verifying a FastAPI server with executable commands, expected outputs, and a practical troubleshooting guide. The content is lean, well-structured, and respects Claude's intelligence.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose with no unnecessary explanation of what FastAPI is or how curl works. The troubleshooting table is dense and informative without padding. | 3 / 3 |
Actionability | All commands are copy-paste ready with concrete examples including GET/POST requests, expected outputs (http_code 200), and specific flags. No pseudocode or vague instructions. | 3 / 3 |
Workflow Clarity | Clear numbered sequence from starting server through testing. Includes implicit validation checkpoints (verify docs load, check schema, test endpoints) and a comprehensive troubleshooting table for error recovery. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with a single focused task, the content is well-organized with clear sections (Steps, Troubleshooting). No external references needed for this scope. | 3 / 3 |
Total | 12 / 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 |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |