Content
81%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 highly actionable, well-sequenced planning skill: exact output templates, explicit validation checkpoints, and clean one-level reference links. The main costs are token efficiency — heavy duplication between the step sections and the Hard Rules list — and three orphaned bundle files with no navigation path from the main file.
Suggestions
Consolidate mandates stated twice: fold Hard Rules 11–13, 15, 17, 20–23 into the step/section text they duplicate (or vice versa) so each rule appears once.
Link the three unreferenced bundle files (references/analysis-modules.md, references/method-library.md, references/workflow-step-template.md) from the relevant steps so they are discoverable.
Trim the repeated endpoint-formula examples in Step 5 and Section C.5 to a single canonical list.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, instruction-only content with no conceptual over-explanation, but the 23 Hard Rules substantially duplicate the step sections: reference-verification rules appear in Step 4.5, Hard Rules 11–13, and Section I; Section G subset rules in Section G and Hard Rules 15/17; the Dataset Disclaimer in Section D and Hard Rule 22. This is mostly efficient but could be tightened by consolidating each mandate in one place. | 3 / 5 |
Actionability | Guidance is fully executable for an instruction-only skill: exact output sections A–J with per-section required elements, a verbatim out-of-scope redirect script, a verbatim Dataset Disclaimer line, minimum retrieval counts (2–4 background, 2–4 method, 1–2 precedent), and the DESeq2-vs-limma selection rule keyed to input data type — Claude knows exactly what to produce. | 5 / 5 |
Workflow Clarity | Seven explicitly ordered steps with a mandatory pre-output validation checkpoint (Step 5 dependency consistency: 'If dependency fails, remove or downgrade the downstream claim rather than silently keeping it'), an out-of-scope redirect, a fallback plan in Section J, and a downgrade map — feedback loops cover the risky steps. | 5 / 5 |
Progressive Disclosure | The body links 5 reference files, all of which exist in references/ and are one level deep with no nested references, clearly signaled ('→ Detailed pattern logic: [references/study-patterns.md](references/study-patterns.md)'). However, 3 of the 8 bundle files (analysis-modules.md, method-library.md, workflow-step-template.md) are never referenced from SKILL.md, leaving bundle content undiscoverable — a minor organization gap. | 4 / 5 |
Total | 17 / 20 Passed |