Content
75%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.
A highly actionable, well-structured CLI skill body with executable examples and good error-recovery guidance. Its main weaknesses are redundant repetition of the same cautions across multiple sections and two orphaned reference bundle files that are never linked from the body.
Suggestions
De-duplicate repeated guidance: state the search-region-vs-resolve-variant caution, the X/Y→23/24 chromosome tip, and the credentials/NCBI_API_KEY instructions once in their primary location and reference back from elsewhere instead of restating.
Link the orphaned bundle files from the body (e.g. add a note pointing to references/api-notes.md for extended API behavior and references/citation.bib for citation info) so the progressive-disclosure structure is fully navigable.
Add an explicit validation/checkpoint between workflow steps (e.g. 'confirm the output rsids list is non-empty before invoking get-variant') to lift workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body avoids explaining concepts Claude already knows (no 'what is a SNP' padding) and is mostly operational, but several guidance blocks are repeated verbatim or near-verbatim: the search-region-vs-resolve-variant caution appears in Core Rules, the Command Selection Guide CAUTION, and Common Mistakes; the '23 for X / 24 for Y' tip appears three times; and the credentials/NCBI_API_KEY instructions appear in both Prerequisites and the Rate Limiting section. This is more than minor trimming, landing at anchor-3 rather than 4. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready commands for every subcommand with real arguments and output paths (e.g. 'uv run scripts/dbsnp_cli.py get-variant rs7412 --output /tmp/rs7412.json'), documented arguments, and concrete JSON output examples covering the common cases. | 5 / 5 |
Workflow Clarity | Three clearly sequenced multi-step workflows (coordinates→rsID→details, region survey→per-variant detail, HGVS→rsID→coordinates) are present, and the Troubleshooting section provides explicit error-recovery feedback loops (HTTP 500 → switch assembly, 'DO NOT RETRY'). It stops at 4 because validation between workflow steps is implicit rather than stated (e.g. no explicit 'confirm rsIDs were found before running get-variant'). | 4 / 5 |
Progressive Disclosure | The body is well-structured (Prerequisites, Core Rules, When to Use, Command Selection Guide, Quick Start, Commands, Workflows, Troubleshooting) and its one in-body reference, scripts/dbsnp_cli.py, is a real, clearly signaled one-level-deep file. The gap keeping it from 5 is that the bundle files references/api-notes.md and references/citation.bib exist but are never linked or signaled from the body, leaving them orphaned. | 4 / 5 |
Total | 16 / 20 Passed |