python-fastapi-patterns

FastAPI web framework patterns. Triggers on: fastapi, api endpoint, dependency injection, pydantic model, openapi, swagger, starlette, async api, rest api, uvicorn.

1.53x

Quality

—

Does it follow best practices?

Impact

92%

1.53x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, code-first body with strong executable examples, but it is held back by absent validation checkpoints in its workflow and — most seriously — by references, scripts, and assets that are advertised but do not exist, breaking progressive disclosure.

Suggestions

Create the referenced bundle files (./references/dependency-injection.md, ./scripts/scaffold-api.sh, ./assets/fastapi-template.py, etc.) or remove the dangling "Additional Resources", "Scripts", and "Assets" sections so navigation is honest.

Add a brief ordered build/verify workflow with an explicit checkpoint, e.g. scaffold -> define models -> wire router -> `uvicorn main:app --reload` -> hit `/docs` to confirm routes, to lift workflow clarity above 2.

Move the more advanced inline patterns (custom exception handlers, router organization, advanced DI/scopes) into the existing reference files to tighten the core body toward a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, executable code, but it stays above the 50-line simple-skill threshold and includes a degree of inline coverage (models, params, DI, exceptions, routers) that could partly live in references; minor tightening is possible but it avoids explaining concepts Claude already knows.	2 / 3
Actionability	Every section provides complete, executable, copy-paste-ready FastAPI code with real imports and annotations (e.g. the Annotated dependency injection and lifespan examples), matching the fully-executable anchor.	3 / 3
Workflow Clarity	Sections are logically ordered, but there is no multi-step workflow with validation checkpoints; for an API-building skill, steps like scaffold -> define models -> wire routes -> run/validate uvicorn are present only implicitly, so it sits at the "steps listed but checkpoints missing" anchor.	2 / 3
Progressive Disclosure	The body lists ./references/*.md, ./scripts/scaffold-api.sh, and ./assets/fastapi-template.py, but none of these bundle files or directories exist in the skill bundle — the references are dangling, so the structure is effectively a monolithic inline body with no valid one-level-deep navigation.	1 / 3
	Total	8 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-triggered description with strong concrete actions and a clear FastAPI niche. Its main weakness is the "Triggers on:" phrasing instead of an explicit "Use when..." directive, which caps the completeness dimension.

Suggestions

Replace the "Triggers on:" clause with an explicit "Use when..." sentence (e.g., "Use when building async APIs with FastAPI, designing endpoints, or working with Pydantic models/OpenAPI.").

Lead with the actionable verb phrase rather than a noun ("Build async web APIs with FastAPI..." instead of "FastAPI web framework patterns.") to state the capability as a concrete action.

Dimension	Reasoning	Score
Specificity	The description names multiple concrete actions grounded in FastAPI's capabilities — "dependency injection", "pydantic model", "openapi", "swagger", and "async api" — matching the anchor that lists several specific concrete actions.	3 / 3
Completeness	It answers "what" (FastAPI web framework patterns) and lists triggers, but uses a "Triggers on:" clause rather than an explicit "Use when..." instruction; per the guidelines a missing explicit "Use when..." clause caps completeness at 2.	2 / 3
Trigger Term Quality	It surfaces natural terms a user would say ("fastapi", "api endpoint", "openapi", "swagger", "uvicorn", "rest api"), giving good coverage of the vocabulary users actually type.	3 / 3
Distinctiveness Conflict Risk	The FastAPI-specific trigger terms (fastapi, pydantic model, starlette, uvicorn, openapi) carve a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: NeverSight/skills_feed
Commit: 26d37ce

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.