Content
73%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 dense, expert-level skill body with an exemplary phased workflow and explicit validation checkpoints. Its weaknesses are redundancy between the metadata comment, Principles, Core Contract, and Never sections, and heavy dependence on reference files that are missing from the evaluated bundle.
Suggestions
Remove the CAPABILITIES_SUMMARY HTML comment and consolidate the repeated peeking/HARKing/pre-registration rules so each appears in exactly one section, cutting the Never list's long explanatory clauses.
Ship the referenced reference/*.md and _common/*.md files in the bundle (or inline the minimal templates and sample-size formula) so the recipe dispatch and Reference Map point at files that actually exist.
Add a brief inline fallback for each recipe (one-line method summary or formula) so the core flow remains executable even when reference files are unavailable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient, expert-level rules with real numbers, but the ~35-line CAPABILITIES_SUMMARY HTML comment duplicates body content, and the peeking/HARKing/pre-registration rules are restated across Principles, Core Contract, and Never with long explanatory clauses. | 3 / 5 |
Actionability | Highly concrete instruction-only guidance with specific thresholds (p < 0.001 SRM, >=80% power, 7-14 day duration, 1/5/25/50/100% ramp) and named methods (mSPRT, Benjamini-Hochberg, delta-method), but the executable artifacts (templates, sample-size calculator) are delegated to reference files absent from this bundle. | 4 / 5 |
Workflow Clarity | The HYPOTHESIZE -> DESIGN -> EXECUTE -> ANALYZE table gives per-phase required actions, key rules, and read paths, with ANALYZE explicitly sequencing 'SRM check -> statistical analysis -> confidence intervals -> recommendations', a halt-and-investigate feedback loop, and freeze/kill-switch checkpoints. | 5 / 5 |
Progressive Disclosure | The Reference Map provides well-signaled, one-level-deep, condition-based pointers across 14 files with recipe-to-reference dispatch, but none of the referenced reference/ or _common/ files exist in the bundle, so the clearly signaled navigation cannot actually be followed. | 4 / 5 |
Total | 16 / 20 Passed |