CtrlK
BlogDocsLog inGet started
Tessl Logo

fastapi-router-py

Create FastAPI routers following established patterns with proper authentication, response models, and HTTP status codes.

52

Quality

59%

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-router-py/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%Scale 1-5

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

A reasonably concise and actionable skill that provides useful code snippets for FastAPI router creation. Its main weaknesses are the lack of validation/verification steps in the integration workflow and the missing bundle file (assets/template.py) that the skill depends on. The 'When to Use' section adds no value.

Suggestions

Add a validation step to the Integration Steps, such as 'Run the test suite or hit the endpoint to verify the router is correctly mounted and responding'.

Include the assets/template.py file in the bundle or inline a minimal version so the skill is self-contained.

Remove the 'When to Use' section — it's a tautology that adds no information.

Consider adding a brief error-handling pattern (e.g., raising HTTPException with proper status codes) since this is a common need when creating routers.

DimensionReasoningScore

Conciseness

Generally efficient and assumes Claude's competence. The 'When to Use' section is a meaningless tautology that wastes tokens, and the description line at the top repeats the title. Otherwise lean.

4 / 5

Actionability

Provides concrete, executable Python code snippets for authentication, response models, and status codes. References a template file with clear placeholder instructions. Minor gap: the template file (assets/template.py) is not provided in the bundle, so the core workflow depends on an unverifiable external asset.

4 / 5

Workflow Clarity

The Integration Steps provide a clear sequence but lack any validation checkpoints. There's no verification step (e.g., run tests, hit the endpoint, check imports). For a multi-step process involving creating routers, models, and mounting them, missing validation caps this at 3.

3 / 5

Progressive Disclosure

References assets/template.py which is good progressive disclosure in principle, but no bundle files are provided so we can't verify it exists. The skill inlines a reasonable amount of content but the Integration Steps could benefit from linking to more detailed guidance. No other references are provided for models or service layer patterns.

3 / 5

Total

14

/

20

Passed

Description

53%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 identifies a clear domain (FastAPI router creation) and mentions several relevant technical aspects, but lacks a 'Use when...' clause that would help Claude select it appropriately. The trigger terms are somewhat technical and miss common synonyms users might use. It reads more like a capability statement than a selection guide.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks to create API endpoints, add routes, build a FastAPI backend, or scaffold REST API handlers.'

Include natural synonyms and variations such as 'API endpoint', 'route', 'REST API', '.py', 'web service', 'backend' to improve trigger term coverage.

List more specific concrete actions such as 'generate CRUD endpoints', 'add route handlers', 'configure dependency injection' to better distinguish from generic API skills.

DimensionReasoningScore

Specificity

Names the domain (FastAPI routers) and mentions a few concrete aspects (authentication, response models, HTTP status codes), but doesn't list specific actions like 'generate CRUD endpoints', 'add middleware', or 'create route handlers'. The actions are more like qualities than concrete operations.

3 / 5

Completeness

Has a clear 'what' (create FastAPI routers with proper patterns), but completely lacks a 'when' clause. There is no 'Use when...' guidance to help Claude know when to select this skill over others.

3 / 5

Trigger Term Quality

Includes 'FastAPI', 'routers', 'authentication', 'response models', and 'HTTP status codes' which are relevant but somewhat technical. Missing natural user phrases like 'API endpoint', 'route', 'REST API', 'backend', or 'web service' that users might actually say.

3 / 5

Distinctiveness Conflict Risk

Fairly distinct by specifying 'FastAPI routers' specifically, which narrows the scope well. However, could overlap with general API development skills or Python web framework skills. The mention of 'established patterns' adds some distinctiveness.

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.