Content
75%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.
The body is a well-structured, actionable Methods-writing guide with real reference files backing its progressive disclosure. Its main weakness is conciseness: several generic boilerplate sections pad the skill without adding skill-specific value.
Suggestions
Remove or collapse the generic boilerplate sections (Required Inputs, Output Contract, Validation and Safety Rules, Failure Handling, Input Validation, Quick Validation) into a few skill-specific lines; the "No local script validation step is required" block in particular adds nothing.
Convert reference mentions into proper markdown links (e.g. [imrad_structure.md](references/imrad_structure.md)) and drop the repeated "if available" hedges now that the files exist, to make navigation crisper.
Tighten the validation guidance in the Recommended Workflow into a concrete verify step tied to the reporting checklist (e.g. 're-check each CONSORT item is explicitly reported') rather than a generic 'final validation pass'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The core (Key Features, the 10-step algorithm, the worked example) is efficient, but generic scaffolding sections — Required Inputs, Output Contract, Validation and Safety Rules, Failure Handling, and a "Quick Validation" block stating "No local script validation step is required" — are padded boilerplate Claude does not need. | 3 / 5 |
Actionability | For an instruction-only skill the guidance is highly actionable: a concrete 10-step Methods algorithm naming specific checks (Shapiro-Wilk, Cohen's d/η²/OR/RR, Holm/Bonferroni/FDR, IQR/Grubbs outliers) plus a near-copy-paste worked example covering the common RCT case. | 5 / 5 |
Workflow Clarity | The IMRAD-aligned algorithm is a clearly ordered 10-step sequence with an explicit validation pass and user-checkpoint guidance; the checkpoints are somewhat generic rather than concrete verify-then-proceed loops, leaving a minor gap below the explicit-feedback-loop anchor. | 4 / 5 |
Progressive Disclosure | Structure is sound: the body holds the overview/algorithm/example while deeper material (imrad_structure.md, reporting_guidelines.md, writing_principles.md — all present in ./references/) is one level deep and signaled inline; references are backtick paths hedged with "if available" rather than clean markdown links, a minor organization gap. | 4 / 5 |
Total | 16 / 20 Passed |