Content
65%Reviews 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 executable code and a well-signaled reference file, but it is verbose and monolithic rather than an overview pointing to detail, and it lacks validation checkpoints for its batch/bulk operations.
Suggestions
Trim repeated boilerplate (e.g. the repeated GEOparse.get_GEO setup) and remove concept explanations Claude already knows to reduce token cost.
Move the long analysis/processing examples into references/geo_reference.md so SKILL.md is a concise overview pointing to detail.
Add explicit validation/verification checkpoints to batch-download and differential-expression workflows (e.g. verify file integrity, check sample counts, confirm QC before proceeding).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~800-line body repeats boilerplate (GEOparse.get_GEO called ~8 times) and explains concepts Claude already knows (what GEO is, basic library purpose); mostly accurate and useful but padded and could be tightened. | 2 / 3 |
Actionability | Provides fully executable Python throughout — GEOparse, Bio.Entrez, ftplib, scipy/statsmodels differential expression — with concrete, copy-paste-ready examples. | 3 / 3 |
Workflow Clarity | Sections are task-organized but lack explicit sequenced workflows with validation checkpoints; batch and bulk-download operations have no verify/validate step, which caps workflow clarity at 2. | 2 / 3 |
Progressive Disclosure | A real one-level reference (references/geo_reference.md) is clearly signaled, but the SKILL.md body itself is a monolithic wall with content that should live in the reference kept inline. | 2 / 3 |
Total | 9 / 12 Passed |