CtrlK
BlogDocsLog inGet started
Tessl Logo

fastapi-python

Expert in FastAPI Python development with best practices for APIs and async operations

55

Quality

61%

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

Quality

Content

68%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 content is exceptionally concise and well-structured as a standards reference, but it is purely instructional with no executable code examples, no sequenced workflow, and no validation checkpoints, which limits actionability and workflow clarity.

Suggestions

Add a short executable Quick-Start example (a minimal FastAPI app with a Pydantic model, an async endpoint, and dependency injection) to lift actionability toward copy-paste ready.

For any multi-step or batch guidance (e.g., refactoring routes, migrating to async), provide a numbered sequence with an explicit validation/verification checkpoint.

Add concrete code snippets for the highest-value directives (e.g., a lifespan context manager and an HTTPException response pattern) so the guidance is executable rather than only descriptive.

DimensionReasoningScore

Conciseness

The body is a lean, well-organized list of directives with no padding or explanations of concepts Claude already knows; every line is a concrete standard, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

It gives concrete, specific directives (e.g., 'Use async def for asynchronous operations', 'Prefer lifespan context managers', 'Use HTTPException for expected errors') but includes no executable code examples or commands, leaving the guidance instructional rather than copy-paste ready.

3 / 5

Workflow Clarity

The guidance is grouped into clear topical sections rather than a sequenced multi-step process; there are no validation checkpoints or feedback loops, and for a standards/conventions skill this lands at the 'steps listed but validation gaps' / unsequenced midpoint.

3 / 5

Progressive Disclosure

The body is short and well-organized into clearly labeled sections with no nested references and no bundle files to navigate; it is appropriately self-contained with minor organization gaps, fitting the 'good structure; most content appropriately placed' anchor.

4 / 5

Total

15

/

20

Passed

Description

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

The description is clear and domain-specific but generic in its actions and lacks any explicit 'Use when' trigger guidance, capping completeness. Adding concrete capability verbs and a usage trigger clause would lift it substantially.

Suggestions

Add a 'Use when...' clause naming concrete triggers (e.g., 'Use when building FastAPI services, defining async endpoints, or working with Pydantic models').

Replace generic phrasing with specific concrete actions (e.g., 'Designs async endpoints, models request/response schemas with Pydantic v2, wires dependency injection, optimizes blocking I/O').

Include natural user phrasings and synonyms ('REST endpoints', 'OpenAPI docs', 'backend APIs') to broaden trigger coverage.

DimensionReasoningScore

Specificity

It names the domain ('FastAPI Python development', 'APIs and async operations') but offers only generic actions rather than concrete, enumerated capabilities, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor.

3 / 5

Completeness

It clearly states what the skill does (expert FastAPI development with best practices) but provides no 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

It surfaces 'FastAPI', 'Python', 'APIs', and 'async operations', but lacks the common natural phrasings or synonyms a user would say when needing this skill (e.g., 'endpoints', 'OpenAPI', 'backend service', 'web framework'), fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The FastAPI-specific framing carves a fairly clear niche distinct from general Python or other web-framework skills, with only minor overlap risk against generic Python-backend skills.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
debpalash/VoiceStudio
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.