Content
65%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 comprehensive, executable code for searching, downloading, and analyzing GEO data, undermined by verbosity and a monolithic structure that duplicates material already in the reference file. Batch workflows lack validation checkpoints, capping workflow clarity at 3. Moving detail into the existing reference and adding explicit verification steps would raise most dimensions.
Suggestions
Trim concept-explaining sections (Key Concepts, GEO2R, Common Use Cases) and time-sensitive counts, or move them to references/geo_reference.md.
Push the detailed E-utilities parameter-level and FTP material into the reference, keeping SKILL.md as a quick-start overview with one example per capability.
Add explicit validation checkpoints to the batch workflows (e.g., verify downloaded file size/format, retry on failure, confirm sample counts match metadata) so batch operations satisfy the workflow-clarity feedback-loop requirement.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bulk is domain-specific, executable code, but padded sections remain: "Key Concepts" defines SOFT/MINiML/MIAME, "Common Use Cases" and "GEO2R Web Tool" are generic prose, and time-sensitive counts ("264,928+ series", "2024[Publication Date]") are not isolated in a deprecated section. Mostly efficient with clear trim candidates, so above anchor 2 but below anchor 4. | 3 / 5 |
Actionability | Every section gives copy-paste-ready, complete functions: Entrez esearch/esummary/efetch workflows, GEOparse get_GEO/pivot_samples/download_supplementary_files, FTP and wget download commands, and a full t-test with Benjamini-Hochberg correction pipeline. These cover the common cases end to end, matching the top anchor. | 5 / 5 |
Workflow Clarity | Sections imply a search → retrieve → analyze progression but no explicit sequence is stated, and the batch operations (batch_download_geo, batch_fetch_geo_metadata) only print errors rather than validate or retry. Per the rubric guideline, batch operations lacking validation/verification steps cap workflow clarity at 3. | 3 / 5 |
Progressive Disclosure | references/geo_reference.md exists, is one level deep, and is clearly signaled in the "## Resources" section — better than anchor 2. However, the ~820-line body inlines E-utilities and FTP detail that the reference also documents, so it is a full manual rather than the overview the rubric rationale calls for — not anchor 4's "most content appropriately placed". | 3 / 5 |
Total | 14 / 20 Passed |