CtrlK
BlogDocsLog inGet started
Tessl Logo

python-fastapi-patterns

FastAPI web framework patterns. Triggers on: fastapi, api endpoint, dependency injection, pydantic model, openapi, swagger, starlette, async api, rest api, uvicorn.

81

1.53x
Quality

75%

Does it follow best practices?

Impact

92%

1.53x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xdarkmatter/claude-mods/python-fastapi-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, code-rich FastAPI reference that is highly token-efficient and largely actionable, organized into clear topical sections with a quick-reference table. Its main weakness is progressive disclosure: the advertised references/, scripts/, and assets/ files do not exist, leaving dangling links, and several code helpers are placeholders.

Suggestions

Create the referenced bundle files (references/dependency-injection.md, middleware-patterns.md, validation-serialization.md, background-tasks.md, scripts/scaffold-api.sh, assets/fastapi-template.py) or remove the broken pointers.

Define or stub the placeholder helpers (create_db_pool, fetch_user, authenticate_token, oauth2_scheme, async_session) so snippets run end-to-end, or mark them explicitly as app-supplied.

Add a brief 'Build an endpoint' mini-workflow (define model -> add route -> wire dependency -> run with uvicorn) with a verification step to lift workflow clarity.

DimensionReasoningScore

Conciseness

The body is code-forward with minimal prose ('Modern async API development with FastAPI.' then executable blocks) and only brief, load-bearing comments like '# Annotated types for reuse'. It assumes Claude's competence and never explains what FastAPI or Pydantic is. It is not below 5 because there is no padded or redundant explanation.

5 / 5

Actionability

Examples are real, structurally complete FastAPI code (imports, decorators, Annotated params, exception handlers) covering the common cases, plus a Quick Reference table. It is below 5 because several helpers (create_db_pool, create_user_in_db, fetch_user, authenticate_token, oauth2_scheme, async_session) are undefined placeholders, so snippets are not standalone copy-paste runnable.

4 / 5

Workflow Clarity

Sections follow a sensible build-up order (app -> models -> params -> DI -> exceptions -> routers) and the skill is a patterns reference with no destructive or batch operations, so the missing-validation cap does not apply. It is below 5 because there is no explicit end-to-end build sequence or checkpoints, and above 3 because the organization is clear and unambiguous for a reference skill.

4 / 5

Progressive Disclosure

The body is well-sectioned and signals one-level-deep references with one-line descriptions ('./references/dependency-injection.md - Advanced DI patterns...'), but the references/, scripts/, and assets/ directories do not exist, so every pointer is a broken link. It is above 2 because signaling and structure are clear, and below 4 because navigation to the deeper material fails.

3 / 5

Total

16

/

20

Passed

Description

72%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 has strong trigger-term coverage and explicit invocation guidance, but the 'what' is reduced to the generic word 'patterns' with no concrete capabilities listed. Voice is correctly third person with no first/second-person phrasing.

Suggestions

Replace 'FastAPI web framework patterns' with concrete actions, e.g. 'Build async REST endpoints, define Pydantic request/response models, and wire dependency injection with FastAPI.'

Trim the most generic triggers ('api endpoint', 'rest api') or qualify them to reduce overlap with other API skills.

Consider adding a file-extension or tool trigger (e.g. 'main.py', 'uvicorn run') to broaden natural-term coverage.

DimensionReasoningScore

Specificity

The phrase 'FastAPI web framework patterns' names the domain but lists no concrete actions (e.g. build endpoints, define models, inject dependencies), matching the anchor 'Names the domain but actions are minimal or generic'. It is below 3 because no specific capability is enumerated, and above 1 because the domain is clearly identified.

2 / 5

Completeness

It states both a 'what' ('FastAPI web framework patterns') and an explicit 'when' ('Triggers on: ...' with concrete trigger phrases), satisfying the 'Use when...' equivalent so it is not capped at 3. It is below 5 because the 'what' is generic ('patterns') rather than a concrete capability list, and above 3 because the 'when' is explicit.

4 / 5

Trigger Term Quality

'Triggers on: fastapi, api endpoint, dependency injection, pydantic model, openapi, swagger, starlette, async api, rest api, uvicorn' provides comprehensive natural-language terms users would actually say, including synonyms (openapi/swagger, async api/rest api). It is not below 5 because coverage is broad and includes framework-specific vocabulary.

5 / 5

Distinctiveness Conflict Risk

Framework-specific triggers (fastapi, starlette, uvicorn, pydantic model) carve a clear niche with minimal conflict risk. It is below 5 because generic terms like 'api endpoint' and 'rest api' could overlap with other web-API skills, and above 3 because the fastapi-specific vocabulary dominates.

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
NeverSight/skills_feed
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.