Content
92%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 strong, well-structured body: fully executable code for both the closed-form and simulation paths, a sequenced workflow with genuine validation loops (Type I error check, fresh-seed verification of candidate n), and clean one-level-deep progressive disclosure verified against the actual bundle. The only weakness is minor verbosity — a short textbook recap of what power analysis is and a long administrative citation-fetching procedure that could be tightened or trimmed.
Suggestions
Trim the Overview's background sentences ("Power analysis plans the probability of rejecting..." and "Four quantities are locked together for any given test...") to a one-line framing; Claude already knows the definition, and the skill-specific guidance (inferential-goal caveat) is what adds value.
Condense or move the harness API-behavior detail in the simulation section (TypeError on raw p-values, invalid-count rejection, etc.) into references/simulation_based_power.md, keeping only the usage pattern and the verify-with-fresh-seed loop inline.
Shorten the 'Citing Scientific Agent Skills' fetch-and-verify instructions to the essential citation line plus one sentence on fetching the current record; the detailed arXiv API fallback steps are administrative overhead in the main file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with non-obvious procedural knowledge ("n_enroll = ceil(n_analyzed / (1 − dropout_rate))", "The harness's alpha argument does not threshold returned p-values", "DEFF = 1 + (m − 1)·ICC is a planning approximation"), and it assumes domain competence rather than teaching basics. But minor over-explanation could be trimmed: the Overview's textbook statements ("Power analysis plans the probability of rejecting a specified null under an assumed alternative", "Four quantities are locked together for any given test") restate what Claude already knows, and the citation section's version-fetching instructions (~15 lines) are administrative rather than procedural. This fits anchor 4 ('efficient; minor instances of over-explanation that could be trimmed') better than 5 ('every token earns its place'). Not 3: there is no padded section and no tutorial-style hand-holding. | 4 / 5 |
Actionability | Quotes: "from power import sample_size, power, mde, power_curve" with seven complete runnable calls; "est = simulate_power(gen_and_test, n=64, n_sims=2000, alpha=0.05, seed=0)"; the uv pip install commands with exact pins; and a copy-paste reporting template. Code is executable as written (the run-directory caveat is stated: "Run from skills/statistical-power/scripts/ or add that directory to sys.path"), and the common cases (two-group t, 3:1 allocation, ANOVA, proportions, correlation, power curve) are all covered. This matches anchor 5 ('fully executable; copy-paste ready code or commands; specific examples cover the common cases'). Not 4: no gaps remain — even edge conventions (signed effects for one-sided tests, integer-ratio recheck) are specified. | 5 / 5 |
Workflow Clarity | Quotes: the 7-step workflow ("State the design... Choose the effect size... Set α and target power... Compute... Sensitivity analysis... Apply adjustments... Report") with explicit checkpoints and error-recovery loops: "First check Type I error under the null", "A noisy bisection search yields a candidate n: verify nearby sizes with more replicates and a fresh seed", "Recheck power using the realized integer ratio". The reporting template doubles as a completeness checklist. This matches anchor 5 ('clear sequence with explicit validation steps; feedback loops for error recovery'). Not 4: validation is not just mentioned but built into the loop (verify candidate n with fresh seeds). Not a destructive/batch skill, so no cap applies. | 5 / 5 |
Progressive Disclosure | SKILL.md is an overview with quick recipes inline, and the bulk detail is split into three real one-level-deep files, each verified to exist and clearly signaled with purpose statements: "references/closed_form_recipes.md — per-test argument conventions and tested statsmodels/Pingouin calls", "references/simulation_based_power.md — full simulation patterns...", "references/effect_sizes.md — choosing effect sizes (SESOI)... ". The reference files do not chain further (only peer-level cross-references), and the Resources section lists every script and reference with a one-line description. This matches anchor 5 ('clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'). Not 4: there is no misplaced bulk content — full argument tables, conversion tables, and simulation patterns are all in the reference files rather than inlined. | 5 / 5 |
Total | 19 / 20 Passed |