CtrlK
BlogDocsLog inGet started
Tessl Logo

fastapi-router-py

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

55

Quality

63%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/fastapi-router-py/SKILL.md

The canonical home for this skill is fastapi-router-py in administrakt0r/AI-Agents-Safe-Coding-Skills

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 lean, well-structured, and actionable with executable code for auth, response models, and status codes plus a concrete integration sequence. Its main weaknesses are the missing assets/template.py file the Quick Start depends on, the absence of any validation/verification checkpoint in the workflow, and a vague filler "When to Use" line.

Suggestions

Provide the referenced assets/template.py (or inline the template) so the Quick Start's primary instruction is executable.

Add a verification step to Integration Steps, e.g. "Run the app and confirm the new router responds with the expected status codes before proceeding."

Replace the generic "When to Use" line with a concrete, specific applicability statement tied to FastAPI router creation.

DimensionReasoningScore

Conciseness

The body is lean with executable code snippets and no padding about what FastAPI is, fitting the score-4 anchor of efficient with minor over-explanation; the only drag is the vague templated "When to Use" filler line ("This skill is applicable to execute the workflow or actions described in the overview.").

4 / 5

Actionability

It provides concrete placeholder substitution, executable auth/response-model/status-code snippets, and specific file paths in the integration steps, matching the score-4 anchor of mostly executable guidance with minor gaps — the main gap being the Quick Start depends on assets/template.py which is not present in the bundle.

4 / 5

Workflow Clarity

The Integration Steps are a clear numbered sequence (create router → mount → models → service → frontend) but there are no validation or verification checkpoints, fitting the score-3 anchor of steps listed with sequence present but checkpoints missing; this is not a destructive/batch operation so the score-3 cap does not bind, but the absence of any verification still lands it at 3 rather than 4.

3 / 5

Progressive Disclosure

The body is well-organized into clearly labeled sections with a single one-level-deep, clearly signaled reference ("Copy the template from assets/template.py"), matching the score-4 anchor of good structure with mostly clear references and minor gaps; the gap is that the referenced assets/template.py file does not actually exist in the bundle.

4 / 5

Total

15

/

20

Passed

Description

58%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 specific and third-person with a clear statement of what the skill does, but it lacks an explicit "Use when..." trigger clause and natural-language synonyms, which caps completeness and trigger-term quality. It is distinct and low-conflict but reads more as a feature list than a trigger-optimized description.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating or scaffolding FastAPI routers, endpoints, or API routes."

Include natural synonyms users say ("endpoints", "API routes", "REST handlers") alongside "routers".

Lead with the concrete action verb phrase and keep the feature list as supporting detail rather than the whole description.

DimensionReasoningScore

Specificity

Names the domain ("Create FastAPI routers") and several concrete elements — "proper authentication, response models, and HTTP status codes" — giving specific coverage with only minor gaps, matching the score-4 anchor rather than 5 because the actions are listed as features rather than a comprehensive set of distinct operations.

4 / 5

Completeness

It clearly states what the skill does ("Create FastAPI routers following established patterns...") but provides no "Use when..." trigger clause, so per the judging guideline a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant technical keywords ("FastAPI routers", "authentication", "response models", "HTTP status codes") are present but common natural variations a user might say ("endpoint", "API route", "REST") are missing, fitting the score-3 anchor of some relevant keywords without synonyms.

3 / 5

Distinctiveness Conflict Risk

"Create FastAPI routers" is a clear, fairly narrow niche unlikely to trigger for unrelated skills, matching the score-4 anchor of mostly distinct with minor overlap risk against closely related web-framework skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

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.