Content
71%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.
A well-organized, highly actionable body with concrete tool calls and a clear three-step workflow, weakened mainly by lack of progressive disclosure (no reference files) for a complex skill and some implicit validation checkpoints.
Suggestions
Add at least one complete runnable Python example under 'COMPUTE, DON'T DESCRIBE' (e.g. calling gwas_get_variants_for_trait and summarizing hits with pandas) to lift actionability from concrete commands to copy-paste code.
Move the detailed tool catalog and Key Parameter Gotchas into a references/ file (e.g. TOOL_REFERENCE.md) and link to it from SKILL.md, keeping the body as an overview to improve progressive disclosure.
Insert explicit validation checkpoints in the Three-Step Workflow (e.g. after enrichment, verify FDR/convergence before proceeding to druggability) to add the missing feedback loops.
Trim the genetics-101 explanations in Core Reasoning Principles to the reasoning chain only, dropping restatements of what non-coding variants or eQTLs are.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean and terse with imperative style and dense gotchas, but a few genetics-101 explanations ('Non-coding GWAS variants rarely affect the nearest gene', the TCF7L2/Wnt walkthrough) restate concepts Claude already knows and could be trimmed. | 4 / 5 |
Actionability | Concrete tool calls with exact parameters and format gotchas (e.g. 'identifiers is space-separated STRING, not array') cover common cases, but there is no full runnable Python code block despite the 'COMPUTE, DON'T DESCRIBE' directive. | 4 / 5 |
Workflow Clarity | A clearly sequenced Three-Step Workflow with evidence tiers and ranking formulas, but validation/feedback checkpoints are implicit rather than explicit (no validate→fix→retry loops), leaving minor gaps. | 4 / 5 |
Progressive Disclosure | Internally well-sectioned with clear headers, but for a complex multi-phase skill the detailed tool catalog and gotchas are fully inlined with no reference files (references/scripts/assets are absent), so content that could be split out stays inline. | 3 / 5 |
Total | 15 / 20 Passed |