Content
38%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-organized but shallow checklist of standard CRO principles. Its main structural claims fail against the real bundle — the referenced knowledge module is missing and the bundled script is orphaned — and the execution protocol lacks the concrete steps, templates, and feedback loops needed to be genuinely actionable.
Suggestions
Fix the bundle mismatch: either create sub-skills/psychological_triggers.md or remove the 'Knowledge Modules' section, and add a reference to the actually-bundled scripts/conversion_calc.js (e.g. '## ROI calculator: node scripts/conversion_calc.js <spend> <conv%> <revenue-per-sale>') so the script is discoverable.
Make the Execution Protocol executable: add a worked example hypothesis, a concrete A/B test setup template (variants, primary metric, sample size/MDE, duration), and a feedback loop step for iterating on failed tests.
Add at least one concrete before/after example per section (e.g. actual micro-copy rewrites, a real decoy-priced tier table) so the principles translate into specific output rather than high-level hints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is compact one-line bullets rather than padded prose, but much of it restates CRO concepts Claude already knows (social proof, decoy effect, multi-step forms, micro-copy, empty states), and taglines like '*Turning visitors into leads.*' and 'Celebrate small wins to build dopamine and habit loops' are unnecessary padding. It could be tightened by cutting the known-concept restatements to focus on the kit's own frameworks and protocol. | 3 / 5 |
Actionability | The guidance is instruction-only but stays at the level of high-level hints — 'Use the Decoy Effect (Anchor pricing)', 'Remove non-essential fields', 'Display SSL certificates' — with no concrete examples of application, no worked hypothesis, no sample test plan, and the only executable artifact (scripts/conversion_calc.js) is never referenced. This matches 'Minimal concrete guidance; high-level hints but missing the specific steps to execute' rather than score 3, which would require at least incomplete-but-present concrete steps or templates. | 2 / 5 |
Workflow Clarity | The Execution Protocol gives a clear 4-phase sequence (Diagnosis, Hypothesis, Design, Validation) and Phase 4 does mention 'an A/B test setup with clear success criteria', so a sequence exists. But the phases are one-line abstractions with no checkpoints during execution and no feedback loop — nothing says what to do with failed test results or how to iterate, leaving it at 'sequence present but checkpoints missing or implicit'. | 3 / 5 |
Progressive Disclosure | Scored against the actual bundle: the body's only reference, './sub-skills/psychological_triggers.md', points to a file that does not exist (there is no sub-skills/ directory), while the one real bundle file, scripts/conversion_calc.js, is never mentioned anywhere in SKILL.md. So the on-paper structure (menu + sectioned bullets) is undermined by a broken link that strands the sole 'Knowledge Module' and leaves the actual bundled script undiscoverable — minimal effective structure for navigating the real bundle. | 2 / 5 |
Total | 10 / 20 Passed |