Content
92%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 tight, well-structured body for a single-script skill: exact input/output contracts, one executable example, and verified reference to the real script. The only improvement is showing runnable examples for the non-search actions.
Suggestions
Add one-liner examples for the identifier lookups (e.g. echo '{"action":"vcv","vcv":"VCV000013080"}' | python scripts/clinvar_variation.py) so all five actions are copy-paste ready.
State the default max_items value (5 per the script) so users know what they get when they omit it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with zero padding: it never explains what ClinVar is or how HTTP works, and every line is operative guidance (rules, field specs, one example). Not 4: there is no over-explanation left to trim. | 5 / 5 |
Actionability | Gives a copy-paste executable example, exact required/optional input fields, precise output shapes, and the failure envelope ("ok=false with error.code and error.message"). Not 5: only the search action gets a runnable example — vcv/rcv/scv/refsnp invocations must be inferred from the field table rather than shown. | 4 / 5 |
Workflow Clarity | This is a simple, single-action skill and the invocation is unambiguous: construct the action-specific JSON, pipe it to scripts/clinvar_variation.py, then summarize or save_raw, with failures self-reporting via ok=false. No batch or destructive operations exist that would require a validation cap. | 5 / 5 |
Progressive Disclosure | Under 50 lines, cleanly sectioned (Operating rules, Execution behavior, Input, Output, Execution, References), with a References section that explicitly confirms no additional runtime files; the one referenced path, scripts/clinvar_variation.py, exists and matches the documented action/field set. | 5 / 5 |
Total | 19 / 20 Passed |