Content
78%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 skill body: every command has executable examples and deep material is properly delegated to real reference files. The main weaknesses are a verbatim-duplicated parsing warning and the absence of any result-validation step after queries.
Suggestions
State the 'do not use cat / use jq' rule once — the 'Parsing Output (CRITICAL)' section repeats the Core Rules bullet almost word-for-word; keep the fuller version and trim the bullet to a pointer.
Fix the typo 'eachmcommand' in the Parsing Output section ('returned by eachmcommand').
Add a brief validation step after queries, e.g., check the output JSON is non-empty or inspect the error field before parsing, so failed lookups are caught early.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient, but the 'Do NOT use cat / use jq' warning appears nearly verbatim twice (Core Rules bullet and the 'Parsing Output (CRITICAL)' section), and the intro re-explains domain background ('functional non-coding DNA elements (like Promoters, Enhancers, and insulators)') that could be trimmed. Not anchor 2 because there is no pervasive padding and the command reference itself is tight. | 3 / 5 |
Actionability | Every command comes with a copy-paste-ready invocation with real arguments and output paths (e.g., 'uv run scripts/screen_api.py search --chromosome chr11 --start 5205263 --end 5207263 --output /tmp/search.json'), plus a worked jq filtering example. Not below 5 — the examples cover the common cases for both scripts. | 5 / 5 |
Workflow Clarity | Prerequisites are sequenced first (uv setup, license notification), then usage rules, quick start, and per-command examples, with a documented fallback (jq unavailable → Python; grch38 → mm10). Not anchor 5 because there is no explicit validation step for query results (e.g., checking the output file is non-empty or handling failed lookups) — though as a read-only query skill this is a minor gap rather than a destructive-operation risk. | 4 / 5 |
Progressive Disclosure | The body is a well-organized overview of commands, with bulk detail correctly split into one-level-deep, clearly signaled references ('read references/json_output_structure.md', 'read references/graphql_schema.md'), and both referenced files plus the scripts exist in the bundle. Not below 5 — the inline command docs are the appropriate getting-started content, not misplaced bulk material. | 5 / 5 |
Total | 17 / 20 Passed |