CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fastapi-best-practices

FastAPI best practices e convenções baseadas em produção real. Aplicar em todos os projetos FastAPI.

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

Quality

Content

57%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 dense, well-sectioned conventions reference with strong, mostly executable code examples and a genuinely valuable migration-safety rule with validation. Its weaknesses are the absence of any progressive disclosure (everything inline, plus references to 'cursor-multiagent-system' template paths that don't exist in this bundle), repetitive padding in the migration section, and no ordered end-to-end workflow tying the conventions together.

Suggestions

Split heavyweight sections (SQL-first patterns, cache system, dependency recipes) into reference files (e.g., references/database.md, references/cache.md) linked from a lean overview in SKILL.md

Remove or fix the dangling 'cursor-multiagent-system' template references (core/templates/…) — either bundle those snippets as skill assets or drop the paths, since they are unresolvable from this skill

Condense the migration prohibition to the rule plus reason plus correct process once, and add an ordered scaffold workflow for a new domain (models → schemas → router → service → migration → test) with explicit validation checkpoints

DimensionReasoningScore

Conciseness

Mostly lean rules plus code with no pedagogical padding, but noticeably tightened-target sections remain: the migration prohibition repeats the same rule roughly six ways ('NUNCA alterar… NUNCA editar… NUNCA deletar' followed by 'Razão' and a 'Processo correto' that restate it), and metadata like 'Última Atualização: 2026-01-20' and 'Fonte' adds tokens without guidance value. Matches anchor 3 ('Mostly efficient but includes some unnecessary explanation or could be tightened'); not 4 because the migration repetition exceeds minor trimming, not 2 because most sections are dense and useful.

3 / 5

Actionability

Abundant executable guidance: the domain-structure tree, async route examples with correct/incorrect pairs, Pydantic v2 ConfigDict, dependency chains, a full SQLAlchemy query, the alembic file_template ini snippet, an async test client, and a final checklist. Minor gaps: 'from core.templates.cache.redis_cache_snippet import CacheSystem' and the 'cursor-multiagent-system' template references point to files not present in this skill's bundle, and '@model_serializer' is used without its import. Matches anchor 4 ('Mostly executable guidance with minor gaps'); not 5 because the dangling template references are not copy-paste runnable.

4 / 5

Workflow Clarity

Per-topic rules are numbered and the migration section includes validation ('SEMPRE testar migrations em ambiente de desenvolvimento primeiro') plus a correct numbered process, and the checklist provides end-of-work verification. However, there is no coherent end-to-end sequence (e.g., scaffolding a new domain: schemas → router → service → migration → tests) — sections read as independent convention lists. Matches anchor 3 ('sequence present but checkpoints missing or implicit' across the skill overall); not 4 because validation checkpoints exist only for migrations.

3 / 5

Progressive Disclosure

445 lines with clear section headers make the body navigable, but everything is inlined in a single file — full SQL examples, cache patterns, and dependency recipes that belong in reference files — and the 'core/templates/…' references point outside the skill where they cannot be resolved. Matches anchor 3 ('Some structure but could be better organized; content that should be separate is inline'); not 2 because headers keep it far more navigable than a headerless wall of text, not 4 because no content split exists at all.

3 / 5

Total

13

/

20

Passed

Description

48%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 identifies a specific niche (FastAPI best practices) and includes an explicit application clause, but it is thin: it enumerates no concrete capabilities, relies on generic 'best practices' language, and over-claims by applying to 'all FastAPI projects'. Trigger coverage inside the description itself is limited to 'FastAPI' and 'best practices', with the richer terms relegated to a separate triggers field.

Suggestions

Enumerate concrete capabilities in the description, e.g. 'Structure FastAPI projects by domain, write async routes, define Pydantic v2 schemas, chain dependencies, manage Alembic migrations safely, and test with async clients'

Replace the over-broad 'Aplicar em todos os projetos FastAPI' with specific 'use when' triggers such as 'Use when creating or refactoring FastAPI projects, implementing endpoints, or configuring Pydantic/dependencies/migrations'

Fold key natural trigger terms (endpoint, router, pydantic, async, alembic, migration) into the description text itself so discovery does not depend solely on the separate triggers field

DimensionReasoningScore

Specificity

The description names the domain ("FastAPI best practices e convenções baseadas em produção real") but lists no concrete actions or capabilities such as project structuring, async routing, Pydantic schemas, or migration rules. This matches anchor 2 ('Names the domain but actions are minimal or generic'); it is not 3 because no specific actions are enumerated, and not 1 because the domain itself is concrete rather than abstract.

2 / 5

Completeness

"Aplicar em todos os projetos FastAPI" provides an explicit 'when' clause, but the 'what' ("best practices e convenções") names no concrete capabilities, and "todos os projetos" is an over-claim rather than a specific trigger. Sits between anchor 3 and anchor 4: the vague 'what' and over-broad 'when' pull it down to 3.

3 / 5

Trigger Term Quality

Relevant natural keywords like "FastAPI" and "best practices" are present, but the description itself omits common variations users would say ("endpoint", "router", "pydantic", "async", "api") — those appear only in the separate frontmatter triggers field, not the description. Fits anchor 3 ('Some relevant keywords but missing common variations or synonyms'); not 4 because coverage within the description text is thin.

3 / 5

Distinctiveness Conflict Risk

"FastAPI" carves out a clear, specific niche unlikely to trigger the wrong skill; overlap risk is limited to other FastAPI-specific skills. Matches anchor 4 ('Mostly distinct; minor overlap risk with closely related skills'); not 5 because "Aplicar em todos os projetos FastAPI" claims the entire FastAPI space.

4 / 5

Total

12

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/backend/fastapi/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.