Content
72%Weight 40%Scale 1-3Reviews 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 with copy-paste executable commands and well-organized, properly progressive structure that points to real bundle scripts. It loses points for some redundant concept/motivation explanation and for lacking explicit output-validation feedback loops in its workflows.
Suggestions
Trim the conceptual explanations of phastCons/phyloP and the pathogenicity motivation in the opening paragraphs; assume Claude's domain knowledge and keep only the non-obvious track/collection reference tables.
Add an explicit validation checkpoint for script output (e.g., check the JSON for an error/empty field and retry with list_tracks.py if a track name fails), giving a clear validate-fix-retry loop.
Reference references/citation.bib from the body (e.g., a 'Citation' note) so the bundled reference file is discoverable and not orphaned.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Quotes 'It retrieves scores from the PHAST package — specifically phastCons ... and phyloP ... calculated from multiple alignments' and 'a strong signal for pathogenicity' explain concepts and motivations Claude largely already knows, though the collection/track tables are genuinely non-obvious reference data, fitting the 'mostly efficient but could be tightened' anchor. | 2 / 3 |
Actionability | Quotes fully executable commands such as 'uv run scripts/get_conservation.py --coordinates ... --output /tmp/cons_output.json' plus '--collection mammal', '--analyze', and '--tf-filter TP53' with real flags and concrete arguments, making examples copy-paste ready. | 3 / 3 |
Workflow Clarity | Quotes 'ALWAYS execute the provided helper scripts' and 'Always pass --output' show a present sequence, but there are no explicit validate-then-fix-then-retry checkpoints; validation of parsed output is left implicit, fitting the 'steps listed but validation gaps' anchor. | 2 / 3 |
Progressive Disclosure | The body is organized into clear sections (Prerequisites, Core Rules, Utility Scripts, per-use-case subsections, Anti-Patterns) with one-level-deep, clearly signaled references to the real scripts/ files (get_conservation.py, get_tfbs.py, list_tracks.py), matching the well-signaled reference anchor. | 3 / 3 |
Total | 10 / 12 Passed |