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.
The body is highly actionable — all five subcommands are documented with verified, executable examples matching the actual CLI — with clear sequencing of prerequisites and workflows. Its weaknesses are redundancy (the capability-to-command mapping appears three times) and a couple of missed validation steps and an unreferenced bundle file (citation.bib).
Suggestions
Merge "When to Use" and "Command Selection Guide" into one mapping of user intent to subcommand, and drop the duplicated Quick Start example from the Commands section.
Reference references/citation.bib from the body (e.g. a short "Citation" section) so the bundled file is discoverable and GTEx attribution is surfaced.
Add a validation step to the workflow: check that Step 1's output contains a valid GENCODE ID (and what to do on failure or multiple matches) before running Step 2.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient with no padding about concepts Claude already knows, but it is noticeably redundant: the "When to Use" bullet list, the "Command Selection Guide", and each "Commands" subsection restate the same capability-to-command mapping three times; the intro paragraph repeats the frontmatter description; and the Quick Start `resolve-gencode-id TNF` example reappears verbatim in Commands. This matches 'Mostly efficient but... could be tightened' — not 4 because the triplicated mapping is more than a minor trim. | 3 / 5 |
Actionability | Every command is fully executable copy-paste-ready `uv run scripts/gtex_cli.py ...` lines with real argument values (e.g. `get-eqtls-in-region chr17 7000000 7100000 "Esophagus - Muscularis"`), and the documented subcommands, positional args, flags, and defaults were verified to match the actual CLI in scripts/gtex_cli.py. The common cases (resolve ID, get expression, top tissues, gene/region eQTLs) are each covered by a concrete example. | 5 / 5 |
Workflow Clarity | Multi-step processes are clearly sequenced: numbered Prerequisites (uv setup, license notification gate) and a Typical Workflow showing the symbol-to-GENCODE-ID-to-query dependency chain with Step 1/Step 2. Not 5 because there are no validation or error-recovery checkpoints (e.g. what to do if symbol resolution fails or returns an empty result before proceeding to Step 2); not 3 because the operations are read-only API queries, the sequence is explicit, and the licensing checkpoint does gate execution. | 4 / 5 |
Progressive Disclosure | Good structure with well-organized sections (Prerequisites, When to Use, Commands, Workflows) and the bundled script scripts/gtex_cli.py is consistently and correctly referenced by every command. Minor gaps keep it from 5: the bundled references/citation.bib is never mentioned or linked anywhere in the body (an orphaned bundle file), and the triplicated command mapping is inline content that could be consolidated; not 3 because navigation is easy, references that exist are clearly signaled, and nothing is nested or buried. | 4 / 5 |
Total | 16 / 20 Passed |