CtrlK
BlogDocsLog inGet started
Tessl Logo

python-fastapi-development

Python FastAPI backend development with async patterns, SQLAlchemy, Pydantic, authentication, and production API patterns.

39

Quality

38%

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/python-fastapi-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

23%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 reads as a high-level project management outline rather than actionable technical guidance. It lists 8 phases with vague action items and delegates all real work to other skills via copy-paste prompts, but provides zero executable code, concrete commands, or specific implementation patterns for FastAPI development. The content is verbose relative to its information density—it uses ~200 lines to convey what could be a simple checklist.

Suggestions

Add concrete, executable code examples for core patterns: a minimal FastAPI app with async SQLAlchemy, a Pydantic model, a JWT auth dependency, and a pytest fixture with TestClient.

Replace vague action items like 'Configure migrations (Alembic)' with specific commands (e.g., `alembic init migrations`, `alembic revision --autogenerate -m 'initial'`, `alembic upgrade head`).

Add validation checkpoints between phases—e.g., 'Verify DB connection with `python -c "from app.db import engine; ..."` before proceeding to API routes'.

Either verify that all referenced skills (@fastapi-templates, @prisma-expert, etc.) exist and link to them properly, or remove the references and inline the essential guidance directly.

DimensionReasoningScore

Conciseness

The skill is heavily padded with generic phase descriptions, numbered action lists that state the obvious (e.g., 'Design database schema', 'Set up pytest'), and copy-paste prompts that just say 'Use @skill-name to do X'. Much of this is information Claude already knows or could infer. The technology stack table and quality gates add little unique value.

2 / 5

Actionability

There is no executable code, no concrete commands, no specific configuration examples, and no actual implementation guidance. Every 'action' is a vague directive like 'Configure migrations (Alembic)' or 'Add password hashing'. The copy-paste prompts just delegate to other skills without providing any concrete steps themselves.

1 / 5

Workflow Clarity

The 8 phases are clearly sequenced and logically ordered, and there is a quality gates checklist at the end. However, there are no validation checkpoints between phases, no feedback loops for error recovery, and no guidance on what to do if a phase fails. The workflow reads more like a table of contents than an actionable process.

3 / 5

Progressive Disclosure

The skill references many other skills/bundles by name but provides no file paths, links, or indication of whether these references actually exist. All 8 phases are inlined at the same level of detail (or lack thereof), creating a long document with no actual content depth. No bundle files are provided to support the numerous references.

2 / 5

Total

8

/

20

Passed

Description

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

The description effectively identifies the technology stack (FastAPI, SQLAlchemy, Pydantic) which provides reasonable trigger terms and distinctiveness. However, it reads more like a topic label than a skill description—it lacks concrete actions (what it does) and completely omits 'when to use' guidance, which are critical for Claude to select the right skill from a large pool.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when building REST APIs with FastAPI, creating async endpoints, setting up SQLAlchemy models, or implementing API authentication.'

Replace the topic-label style with concrete actions, e.g., 'Creates FastAPI endpoints, defines Pydantic request/response models, configures SQLAlchemy database connections, implements JWT/OAuth authentication.'

Include additional natural trigger terms and synonyms such as 'REST API', 'endpoints', 'routes', 'JWT', 'OAuth', 'CRUD', 'web server' to improve discoverability.

DimensionReasoningScore

Specificity

Names the domain (FastAPI backend development) and lists several technologies (SQLAlchemy, Pydantic, authentication, async patterns), but these are more technology keywords than concrete actions. It doesn't describe what the skill actually does (e.g., 'creates API endpoints', 'generates CRUD routes', 'sets up database models').

3 / 5

Completeness

Provides a partial 'what' (Python FastAPI backend development) but has no 'when' clause at all. There is no 'Use when...' guidance or equivalent trigger phrasing, which per the rubric should cap completeness at 3, and the 'what' itself is more of a topic label than a clear explanation.

2 / 5

Trigger Term Quality

Includes several natural keywords a developer would use: 'FastAPI', 'SQLAlchemy', 'Pydantic', 'authentication', 'async', 'API', 'backend'. Missing some common variations like 'REST API', 'endpoints', 'routes', 'middleware', 'OAuth', 'JWT', or 'Python web framework'.

4 / 5

Distinctiveness Conflict Risk

FastAPI is a specific framework, which helps distinguish this from generic Python or Django skills. However, broad terms like 'backend development', 'authentication', and 'production API patterns' could overlap with other backend or API-related skills.

4 / 5

Total

13

/

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.