CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

46

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

The canonical home for this skill is fastapi-templates in rmyndharis/antigravity-skills

SKILL.md
Quality
Evals
Security

Quality

Content

18%Scale 1-5

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

This skill is essentially a stub—it has a title and metadata but lacks any substantive content for building FastAPI projects. There are no code examples, no project structure templates, no concrete commands, and no real workflow. The entire skill delegates to a resource file that doesn't exist in the bundle, leaving Claude with nothing actionable to work with.

Suggestions

Add a concrete project structure template (directory tree) and at least one executable FastAPI app example with async endpoint, dependency injection, and error handling patterns.

Replace the generic instruction bullets ('Apply relevant best practices') with a specific step-by-step workflow for scaffolding a FastAPI project, including validation steps like running tests or starting the dev server.

Either include the referenced `resources/implementation-playbook.md` in the bundle or inline the essential patterns (middleware setup, database connection, Pydantic models) directly in the SKILL.md.

Remove the generic 'Do not use this skill when' section and the boilerplate instructions to make room for actual FastAPI-specific guidance.

DimensionReasoningScore

Conciseness

The 'Use this skill when' and 'Do not use this skill when' sections add moderate padding without much value—Claude doesn't need to be told when not to use a skill in such generic terms. The instructions section is generic boilerplate ('Clarify goals, constraints, and required inputs') rather than FastAPI-specific content. However, it's not excessively verbose overall.

3 / 5

Actionability

There is zero concrete, executable guidance—no code examples, no project structure templates, no specific commands, no FastAPI patterns. The instructions are entirely abstract ('Apply relevant best practices and validate outcomes') and delegate everything to a referenced file that doesn't exist in the bundle.

1 / 5

Workflow Clarity

There is no workflow, no sequenced steps, and no validation checkpoints. The four bullet points in Instructions are generic platitudes with no specific process for creating a FastAPI project. For a skill about creating production-ready projects, the absence of any concrete workflow is a critical gap.

1 / 5

Progressive Disclosure

The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable disclosure strategy, but no bundle files are provided, meaning the reference leads nowhere. The SKILL.md itself contains almost no substantive content to serve as an effective overview or entry point, making the progressive disclosure structure hollow.

2 / 5

Total

7

/

20

Passed

Description

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

This is a solid description that clearly communicates both purpose and trigger conditions. Its main weakness is that the 'what' portion leans on architectural buzzwords (async patterns, dependency injection) rather than listing concrete actions the skill performs. Adding more specific deliverables and a few additional trigger synonyms would strengthen it.

Suggestions

Replace or supplement architectural pattern terms with concrete actions like 'generate route handlers, configure middleware, set up Pydantic models, create project scaffolding'.

Add common synonyms and related terms such as 'REST API', 'Python API', 'web server', 'ASGI', or 'endpoints' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (FastAPI projects) and mentions a few concrete aspects (async patterns, dependency injection, error handling), but these are more architectural patterns than specific actions. It doesn't list concrete actions like 'generate route handlers', 'configure middleware', 'set up database models', etc.

3 / 5

Completeness

Clearly answers both 'what' (create production-ready FastAPI projects with async patterns, dependency injection, and error handling) and 'when' (when building new FastAPI applications or setting up backend API projects) with explicit trigger phrases.

5 / 5

Trigger Term Quality

Includes good natural keywords like 'FastAPI', 'backend API', 'async', and 'dependency injection' that users would naturally mention. Missing some common variations like 'REST API', 'Python API', 'web server', 'endpoints', or 'ASGI'.

4 / 5

Distinctiveness Conflict Risk

Fairly distinct due to the specific mention of FastAPI, which narrows the scope well. Minor overlap risk with general Python web framework skills (Flask, Django) or generic API scaffolding skills, but the FastAPI-specific terms help differentiate.

4 / 5

Total

16

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.