CtrlK
BlogDocsLog inGet started
Tessl Logo

fastapi-patterns

FastAPI patterns for async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness.

62

Quality

74%

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

Quality

Content

82%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 body is a high-quality, executable pattern reference: complete copy-paste code across the FastAPI lifecycle, lean prose, and clear sectioning. It lacks explicit validation feedback loops and has no bundled reference files, which keep workflow_clarity and progressive_disclosure just below perfect.

DimensionReasoningScore

Conciseness

The body is lean: it assumes Claude knows FastAPI and pairs one-line directives with complete code, with only minor intro sentences (e.g. 'Use a factory so tests and workers can build the app with controlled settings.') that could be trimmed, fitting the 'efficient, minor over-explanation' anchor rather than the pristine 5.

4 / 5

Actionability

Every section provides fully executable, copy-paste-ready code covering the common cases (factory, schema split, DI, async endpoints, exception handlers, OpenAPI override, test fixture), matching the 'fully executable, copy-paste ready, common cases covered' anchor.

5 / 5

Workflow Clarity

'How It Works' and 'Project Layout' give a clear structural sequence and the Security/Performance sections act as checklists, but there are no explicit validate->fix->retry feedback loops; this is a patterns skill rather than a destructive workflow, so the 3-cap does not apply and 4 is the best fit.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent) and the skill is a single well-sectioned file with a See Also pointer to sibling skills; structure is good and navigation is easy, though all content is inlined with no one-level-deep references that would justify a 5.

4 / 5

Total

17

/

20

Passed

Description

66%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 well-keyworded for FastAPI, but lacks an explicit 'when to use' trigger clause, which caps its completeness. Adding a 'Use when ...' sentence would lift it into the top tier.

Suggestions

Append an explicit trigger clause, e.g. 'Use when building or reviewing FastAPI apps, async APIs, or Pydantic schemas.'

Lead with action verbs ('Build', 'Review', 'Structure') instead of 'patterns for ...' to convert topic nouns into concrete capabilities.

Add a couple of natural synonyms users might say (e.g. 'REST API', 'uvicorn', 'SQLAlchemy') to widen trigger coverage.

DimensionReasoningScore

Specificity

Lists several specific concrete areas ('async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness'), but they are framed as topic nouns rather than action verbs, leaving it just short of the comprehensive action-verb anchor at 5.

4 / 5

Completeness

The 'what' is clear ('FastAPI patterns for ...'), but there is no explicit 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Strong natural keywords a user would say ('FastAPI', 'async APIs', 'dependency injection', 'Pydantic', 'OpenAPI docs'), but a few common synonyms are missing (e.g. 'REST API', 'uvicorn', 'SQLAlchemy'), fitting the 'good coverage, a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The 'FastAPI patterns' framing carves a clear niche with distinct triggers and minimal conflict risk, though it shares some overlap with related 'api-design'/'python-patterns' skills noted in See Also.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.