CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fastapi-development

Modern Python API development with FastAPI covering async patterns, Pydantic validation, dependency injection, and production deployment

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 ./plugins/luxor-backend-toolkit/skills/fastapi-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

40%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 a thorough, mostly-executable FastAPI reference, but it is monolithic and tutorial-verbose, re-explaining concepts Claude already knows and inlining material that belongs in separate reference files. It lacks sequenced workflows with validation checkpoints for its destructive/database/deploy operations.

Suggestions

Trim concept explanations Claude already knows (FastAPI philosophy/features, async-vs-def rationale, basic CRUD/Docker walkthroughs) and keep only non-obvious guidance and reusable code.

Split large reference blocks (auth flows, full SQLAlchemy CRUD, deployment recipes) into one-level-deep reference files under references/ and link to them from a concise overview in SKILL.md.

Add explicit validation/verification checkpoints (e.g., run tests, verify the container starts, check DB migrations applied) into the deployment and CRUD sections, since these are destructive/batch operations.

DimensionReasoningScore

Conciseness

The ~980-line body re-explains concepts Claude already knows (FastAPI's philosophy/feature list, what async/await is for, CRUD boilerplate, basic Docker/Gunicorn usage) and inlines large tutorial-scale reference blocks; this is noticeably verbose with several padded sections. It is above 1 because the code is generally accurate rather than entirely filler.

2 / 5

Actionability

It provides mostly executable, copy-paste-ready code across Pydantic models, routing, dependency injection, auth, SQLAlchemy CRUD, tests, and Docker, with only minor gaps (e.g., undefined helpers like get_user_from_db and hash_password). It is not a 5 because some examples reference undefined helpers and skip wiring needed to actually run.

4 / 5

Workflow Clarity

Topics are presented as a reference catalog rather than a sequenced workflow, and destructive/batch operations (DB CRUD, deployment) lack explicit validation checkpoints or feedback loops; the rubric caps such skills at 3 and this sits below that due to rough, gap-filled sequencing. It is above 1 because a rough topic ordering exists.

2 / 5

Progressive Disclosure

Everything is inlined into one monolithic SKILL.md with no bundle files in references/scripts/assets and no one-level-deep pointers, so large blocks that clearly belong in separate reference files are inlined. It is above 1 because the body uses section headers that provide some navigability.

2 / 5

Total

10

/

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 third-person, naming several concrete FastAPI capabilities with good trigger keywords, but it omits any explicit "Use when..." trigger guidance, which caps its completeness. Adding a concrete trigger clause would lift it toward the top anchors.

Suggestions

Append a 'Use when...' clause naming concrete trigger scenarios (e.g., building REST APIs, OAuth2/JWT auth, async database integration, migrating from Flask/Django).

Broaden trigger-term coverage with synonyms and ecosystem cues users actually say (REST API, Swagger/OpenAPI, WebSocket, SQLAlchemy, uvicorn).

Consider including a file/extension or version cue to sharpen distinctiveness against generic Python backend skills.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ("async patterns", "Pydantic validation", "dependency injection", "production deployment"), which is several specific actions with only minor coverage gaps; it is not a 5 because coverage is not comprehensive (e.g., routing, auth, testing are absent).

4 / 5

Completeness

The description clearly states what the skill does but has no "Use when..." clause or equivalent explicit trigger guidance, which the rubric caps at 3; it is above 2 because the "what" is concrete rather than vague.

3 / 5

Trigger Term Quality

Includes strong natural keywords users would say ("FastAPI", "async patterns", "Pydantic", "dependency injection", "production deployment") but lacks a few common variations (e.g., "REST API", "OAuth2", "Swagger/OpenAPI", file/extension cues); below 5 because synonym coverage is incomplete.

4 / 5

Distinctiveness Conflict Risk

"FastAPI" plus named sub-capabilities carve a mostly distinct niche with only minor overlap risk against a generic Python-backend or Django/Flask skill; it is not a 5 because the trigger phrasing is not sharp enough to fully eliminate overlap with adjacent web-framework skills.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (989 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

manutej/luxor-claude-marketplace

Path

plugins/luxor-backend-toolkit/skills/fastapi-development/SKILL.md

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.