Content
82%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.
Highly actionable content with executable commands for every subcommand, clear core rules, and useful anti-patterns. Weaknesses are minor: a slightly redundant intro, no explicit validation/feedback loops in the query workflow, and an unreferenced bundled citation file.
Suggestions
Trim the opening background paragraph ('JASPAR is the definitive open-access database...') to a single line or fold it into the usage statement to save tokens.
Add an explicit validation step to the workflow, e.g., verify the resolved Matrix ID exists (and retry with a different tax_id or name variant on failure) before calling get_tf_motif.
Reference the bundled references/citation.bib in the body (e.g., a 'Citation' section) so the reference file is discoverable and its purpose is clear.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean and operational, but the opening background sentence 'JASPAR is the definitive open-access database for Transcription Factor (TF) binding profiles' plus the following framing paragraph restate context Claude largely already knows and could be trimmed. | 4 / 5 |
Actionability | All six subcommands are given as copy-paste-ready 'uv run scripts/jaspar_api.py ...' invocations with concrete example arguments, and supported output formats and constraints (100kb window, tax_id 9606) are explicitly enumerated. | 5 / 5 |
Workflow Clarity | The critical resolve-then-fetch sequence is explicit ('If a user provides a gene symbol ... you must resolve it first using resolve_tf_id') and prerequisites are a numbered two-step process, but there are no explicit output-validation or error-recovery checkpoints beyond the TFFM 500-error aside. | 4 / 5 |
Progressive Disclosure | The body is well-sectioned and the bundled script (scripts/jaspar_api.py) is real and consistently referenced, but the bundle's references/citation.bib is never mentioned or linked anywhere in the body, leaving a navigation gap for an existing reference file. | 4 / 5 |
Total | 17 / 20 Passed |