fastapi-templates

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

Quality

63%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/fastapi-templates/SKILL.md

Quality

Content

43%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.

The body is compact and well-sectioned but offers almost no FastAPI-specific, executable guidance — it relies on generic process bullets and a referenced playbook that is missing from the bundle. Adding concrete code and an actual sequenced, validated workflow would substantially raise the score.

Suggestions

Replace the abstract 'Instructions' bullets with at least one copy-paste-ready FastAPI example (project layout, app factory, async route, dependency injection) so the body is actionable on its own.

Define a concrete sequenced workflow with explicit validation checkpoints (e.g. scaffold → add routes/DI → run `pytest`/`uvicorn` → verify), rather than generic advice.

Either create resources/implementation-playbook.md so the referenced path resolves, or remove the reference until the file exists, to fix the broken progressive-disclosure navigation.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept over-explanation, but the generic 'Instructions' bullets ('Clarify goals...', 'Apply relevant best practices...') are boilerplate that adds little FastAPI-specific value, so it sits just below the leanest anchor.	4 / 5
Actionability	There is no concrete code, command, or executable example in the body — guidance like 'Apply relevant best practices and validate outcomes' is high-level and deflects detailed examples to a referenced file, matching the 'minimal concrete guidance, missing specific steps' anchor.	2 / 5
Workflow Clarity	The four 'Instructions' bullets are generic advice rather than a sequenced process, and there are no validation checkpoints or a defined step order, fitting the 'rough sequence present but many gaps, validation absent' anchor.	2 / 5
Progressive Disclosure	Sections are well organized and the body points to a single one-level-deep reference (resources/implementation-playbook.md), but that referenced file does not exist in the bundle, so navigation is only partially functional.	3 / 5
	Total	11 / 20 Passed

Description

82%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, third-person description that clearly answers both what the skill does and when to use it, anchored on a distinct FastAPI niche. The only mild gap is that it lists one main action plus feature tags rather than several discrete capabilities.

Dimension	Reasoning	Score
Specificity	It names the FastAPI domain and the concrete action "Create production-ready FastAPI projects" with listed features (async patterns, dependency injection, error handling), but offers only one primary action verb rather than multiple distinct actions, matching the '1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	It clearly states what it does ("Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling") and gives an explicit 'Use when building new FastAPI applications or setting up backend API projects' trigger, mirroring the top anchor example.	5 / 5
Trigger Term Quality	Natural user terms like "FastAPI projects", "FastAPI applications", and "backend API projects" are present and would be said by a user, though a few common synonyms (e.g. REST APIs, .py) are missing.	4 / 5
Distinctiveness Conflict Risk	"FastAPI" is a clear, specific niche with distinct triggers and minimal overlap with other skills; the description is unlikely to fire for the wrong skill.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/fastapi-templates/SKILL.md
Commit: 3eff4af

Reviewed: 23 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.