fastapi-patterns

FastAPI best practices covering project structure, Pydantic v2 schemas, dependency injection, async handlers, authentication, authorization, transactional service layers, and testing with httpx and pytest. Use when building or reviewing FastAPI apps — Pydantic schemas, dependencies, async handlers, auth, or tests.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%Weight 40%Scale 1-5

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

An excellent, lean code-pattern reference: executable end-to-end FastAPI examples with anti-patterns and best practices, well sectioned. The only soft spot is the absence of explicit validation/checkpoint guidance for the destructive DB operations the patterns rely on.

Dimension	Reasoning	Score
Conciseness	The body is lean: it jumps straight into organized code with brief section intros and avoids explaining what FastAPI/Pydantic/SQLAlchemy are, so every token earns its place.	5 / 5
Actionability	Fully executable, copy-paste-ready code across project structure, config, schemas, DI, router, service, and tests covering the common cases, with a Best Practices and Anti-Patterns section giving concrete do/don't examples.	5 / 5
Workflow Clarity	The skill is a pattern reference rather than a destructive multi-step process, and sections are logically sequenced with an Anti-Patterns feedback-style section; however there are no explicit validate/retry checkpoints for the database-mutation and batch operations the patterns involve, leaving minor validation gaps.	4 / 5
Progressive Disclosure	No bundle files exist and none are needed; the body is a well-organized single-file overview with clear section headers, so the simple-skill exception applies and structure is appropriate.	5 / 5
	Total	19 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 strong, specific description that concretely enumerates capabilities and gives an explicit 'Use when' trigger clause. Minor gains are possible by adding full synonyms ('authentication'/'authorization' instead of 'auth') and sharpening the niche against adjacent web-framework skills.

Suggestions

Expand the abbreviated 'auth' to 'authentication and authorization' in the trigger clause so users say those exact words.

Add 'REST API' or 'endpoint' as natural trigger terms to widen the keyword surface users actually say.

Tighten the trigger to a more distinct niche (e.g., 'Use when building or reviewing production FastAPI services') to reduce overlap with generic web-framework skills.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions across the domain — 'project structure, Pydantic v2 schemas, dependency injection, async handlers, authentication, authorization, transactional service layers, and testing with httpx and pytest' — comprehensive coverage rather than vague language.	5 / 5
Completeness	Both 'what' (the enumerated best-practice areas) and 'when' ('Use when building or reviewing FastAPI apps — ...') are explicitly and concretely answered with trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ('building or reviewing FastAPI apps', 'Pydantic schemas, dependencies, async handlers, auth, or tests'), but 'auth' is an abbreviation and common synonyms like 'API' or 'endpoints' are only implied, so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	The FastAPI niche is clear with distinct triggers and minimal conflict risk, but the breadth of covered areas (auth, testing, DI) creates minor overlap with general web-framework or testing skills rather than a fully isolated niche.	4 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (515 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/fastapi-patterns/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.