cro-optimization

Run conversion rate optimization through hypothesis-driven testing including audit, hypothesis generation, test design, statistical analysis, and rollout decisions. Use this skill whenever the user wants to optimize conversion, run A/B tests, audit a funnel, generate test hypotheses, design experiments, or analyze test results. Triggers on conversion optimization, CRO, A/B test, split test, multivariate test, hypothesis, conversion funnel, funnel audit, experiment design, statistical significance, lift, optimization. Also triggers when the user has a conversion problem and isn't sure where to start, or when test results are ambiguous and need interpretation.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, highly actionable CRO playbook with clear workflow sequencing and copy-paste templates. Its main weaknesses are some concept explanation Claude already knows and a monolithic body that under-uses the reference-file pattern it already sets up.

Suggestions

Trim or move the 'Statistical foundations' section (the 95%-significance definition and multiple-testing primer) into a reference file, keeping only the operational sample-size table inline — these explain concepts Claude already knows.

Split the output template and the sample-size quick-reference table into reference files (e.g. references/test-plan-template.md and references/sample-size-reference.md) and link to them, reducing the inline body to an overview.

Tighten the 'Common test setup mistakes' and 'Failure patterns' lists by collapsing overlapping items (e.g. peeking/early-stopping appears in both) to recover token budget.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and operational, but spends tokens explaining concepts Claude already knows ('A 95% significance level means...') and the multiple-testing/Bonferroni primer, so it is not fully lean.	2 / 3
Actionability	Provides concrete, copy-paste-ready guidance: a filled hypothesis template with example, sample-size calculator inputs, a decision-framework table, and a full markdown output template — fully actionable for an instruction-only skill.	3 / 3
Workflow Clarity	Clear sequencing via the 4-phase framework and 10-step workflow, with pre-defined decision criteria ('when to ship, when to kill, when to extend') acting as checkpoints and feedback loops ('iterate hypothesis', 'compound lessons').	3 / 3
Progressive Disclosure	One clearly-signaled one-level reference exists (references/hypothesis-library.md, verified present), but the ~270-line body keeps statistical foundations, the sample-size reference table, and the output template inline where separate files would aid navigation.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: third-person voice, concrete actions, explicit trigger guidance covering natural phrasings, and a clear niche that avoids conflict with neighboring skills. Both the 'what' and 'when' are answered explicitly.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'audit, hypothesis generation, test design, statistical analysis, and rollout decisions' — rather than vague language, matching the top anchor.	3 / 3
Completeness	Explicitly answers both what ('Run conversion rate optimization through hypothesis-driven testing including...') and when ('Use this skill whenever the user wants to...'), with an explicit 'Triggers on' clause.	3 / 3
Trigger Term Quality	Broad natural-term coverage ('A/B test, split test, multivariate test, conversion funnel, funnel audit, experiment design, statistical significance, lift, optimization') plus user-phrased triggers ('when the user wants to optimize conversion, run A/B tests').	3 / 3
Distinctiveness Conflict Risk	Occupies a clear CRO niche with distinct triggers and the body further distinguishes it from adjacent skills (landing-page-copy, analytics-strategy), making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: rampstackco/claude-skills
Commit: f1bc195

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.