CtrlK
BlogDocsLog inGet started
Tessl Logo

fastapi-code-review

Review checklist for correctness, regressions, and missing tests in the vault-memory FastAPI/async codebase — async pitfalls, FastAPI/DI/auth checks, and test-quality signals.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 tight, highly actionable review checklist that assumes Claude's competence and names exact APIs and patterns. It is well-organized and sequenced, with only minor workflow-feedback-loop gaps that are largely inapplicable to a review skill.

DimensionReasoningScore

Conciseness

The body is lean and packed with specific checks; it never explains concepts Claude already knows (no 'what is FastAPI/async' padding) and every bullet earns its place, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Guidance is concrete and directly executable — e.g. 'compare task.get_loop() against asyncio.get_running_loop()', 'mock via app.dependency_overrides[get_dependencies]', 'monkeypatch-delete the key', 'go through _safe_vault_path' — naming exact functions, env vars, and patterns; per scoring_notes, absence of code blocks in an instruction-only skill is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

A clearly sequenced 'Review order' (1. Correctness → 2. Regressions → 3. Missing tests) provides an explicit checklist sequence with most checkpoints present; not a 5 because there is no explicit validate→fix→retry feedback loop, though such loops are largely inapplicable to a review skill.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and four well-organized section headers, so per the simple-skill guideline progressive disclosure scores 5 on well-organized sections alone; no bundle files exist to verify.

5 / 5

Total

19

/

20

Passed

Description

70%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 highly distinct, naming concrete review dimensions and a clear niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reviewing changes to the vault-memory FastAPI/async codebase or when the user asks to review FastAPI route/async code.'

Broaden trigger terms with natural synonyms users say ('code review', 'lint', 'pull request review') to lift trigger-term coverage.

State the 'when' explicitly rather than leaving it implied by the codebase reference.

DimensionReasoningScore

Specificity

Lists several specific actions — 'correctness, regressions, and missing tests' plus 'async pitfalls, FastAPI/DI/auth checks, and test-quality signals' — matching the 'lists several specific actions; minor gaps' anchor; not a 5 because all actions are review-for-X variants scoped to one codebase rather than comprehensive distinct operations.

4 / 5

Completeness

The 'what' is clear ('Review checklist for...') but there is no explicit 'Use when...' trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 3, matching the 'clear what, when missing or only weakly implied' anchor.

3 / 5

Trigger Term Quality

Good natural keyword coverage — 'review', 'regressions', 'missing tests', 'FastAPI', 'async', 'auth' — terms users would actually say; a few natural synonyms (e.g. 'code review', 'lint') are missing, so it sits at the 'good coverage, a few terms missing' anchor rather than 5.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to 'the vault-memory FastAPI/async codebase' with distinct triggers, giving a clear niche with minimal conflict risk, matching the top anchor.

5 / 5

Total

16

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
pvnkmnk/vault-memory
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.