Content
36%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a thin shell: well-sectioned and brief, but almost entirely generic filler with zero FastAPI-specific instruction, and its sole depth resource is missing from the bundle. It fails the core purpose of a SKILL.md body — telling Claude concretely what to do.
Suggestions
Replace the generic Instructions ('Apply relevant best practices and validate outcomes') with concrete guidance: a minimal project skeleton (app/main.py, routers/, deps.py), an async route example with dependency injection and error handling, and a run command like `uvicorn app.main:app --reload`.
Add an explicit workflow with validation checkpoints, e.g.: scaffold project → implement routes → run `pytest` → verify the app starts and `/docs` responds.
Fix the broken progressive disclosure: ship the referenced `resources/implementation-playbook.md` in the bundle or remove the reference, and delete the tautological 'Do not use this skill when' bullets and the intro line that duplicates the frontmatter description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Quotes: 'The task is unrelated to fastapi project templates' / 'You need a different domain or tool outside this scope' are tautological filler, and 'Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes' is generic boilerplate. Not 4 because several sections add no skill-specific value (the Do-not-use list and generic instruction bullets are pure padding, and the intro repeats the description); not 2 because the body is short with no concept explanations. | 3 / 5 |
Actionability | Quotes: 'Apply relevant best practices and validate outcomes. Provide actionable steps and verification.' — no code, commands, project layout, or FastAPI-specific steps anywhere; the only concrete pointer, 'open resources/implementation-playbook.md', targets a file that does not exist in the bundle. Not 1 because the Use-when list and resource pointer constitute minimal concrete guidance; not 3 because there is no executable or near-executable guidance at all. | 2 / 5 |
Workflow Clarity | Quotes: 'Clarify goals... Apply relevant best practices and validate outcomes' — only a rough implicit sequence (clarify → apply → validate) with no defined steps, no commands, and no validation checkpoints (e.g., run the server, hit /docs, run pytest). Not 1 because a rough ordering and clear scope structure exist; not 3 because the steps are poorly defined and validation is absent, matching the anchor-2 example pattern. | 2 / 5 |
Progressive Disclosure | Sections are well organized and the reference is clearly signaled and one level deep ('If detailed examples are required, open resources/implementation-playbook.md'), but the actual bundle contains no such file — the single referenced path is broken, so the disclosure promise is unfulfilled. Not 4/5 because a dangling reference is a real navigation failure; not 2 because structure itself is good and nothing is improperly inlined. | 3 / 5 |
Total | 10 / 20 Passed |