CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

A well-structured, actionable CRO framework that gives Claude concrete templates, scoring rubrics, and a copy-paste output format. Main weaknesses are minor verbosity in the statistical foundations section and a heavier-than-overview SKILL.md with limited use of reference files.

Suggestions

Move the statistical foundations section (significance explanation, sample-size quick-reference table, multiple-testing note) into a references file, keeping only the decision-relevant rules inline to improve progressive disclosure.

Add an explicit pre-launch validation gate to the workflow (e.g., "QA variant renders and event tracking before starting the clock") to strengthen feedback loops.

Tighten the significance explanation to the CRO-specific misconception note rather than re-deriving what a p-value is.

DimensionReasoningScore

Conciseness

Mostly lean for the depth covered — hypothesis template, ICE/PIE scoring, sample-size table, decision matrix, and output template all earn their tokens — with minor over-explanation of significance and Bonferroni that Claude already knows. Not a 5 because the statistical foundations section could be trimmed; not a 3 because padding is minor.

4 / 5

Actionability

Provides copy-paste-ready, specific guidance for an instruction skill: a hypothesis structure with a worked example, 1-10 ICE/PIE scoring, a sample-size quick-reference table, a decision matrix, and a complete output-format markdown template. Not a 4 because the common cases are covered with no real gaps.

5 / 5

Workflow Clarity

Clear 10-step workflow and 4-phase sequence (Audit → Hypothesis → Test design → Decide) with a pre-launch parameters checklist and a ship/kill/extend decision matrix. Not a 5 because the workflow reads as a sequence rather than explicit validate→fix→retry feedback loops; not a 3 because checkpoints are mostly present.

4 / 5

Progressive Disclosure

Well-organized sections with one clearly-signaled, one-level-deep reference (references/hypothesis-library.md) verified to exist. Not a 5 because SKILL.md is heavier than an "overview" — the statistical foundations and sample-size table could be split out — and only one reference file exists; not a 3 because structure and signaling are good.

4 / 5

Total

17

/

20

Passed

Description

96%Weight 40%Scale 1-5

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

A strong, third-person description that explicitly covers what the skill does, when to use it, and a comprehensive set of trigger terms including synonyms. The only weakness is a couple of broad trigger terms ("optimization", "lift") that carry minor overlap risk with non-CRO optimization skills.

Suggestions

Qualify the broad trigger "optimization" (e.g., "conversion optimization") so it cannot fire for unrelated optimization tasks such as code or performance optimization.

Consider narrowing "lift" to "conversion lift" to reduce overlap with general performance contexts.

DimensionReasoningScore

Specificity

Lists multiple concrete CRO actions — "audit, hypothesis generation, test design, statistical analysis, and rollout decisions" — giving comprehensive coverage rather than vague abstractions. Not a 4 because coverage is complete, not "minor gaps."

5 / 5

Completeness

Explicitly answers both what ("Run conversion rate optimization through hypothesis-driven testing including...") and when ("Use this skill whenever...", "Triggers on...", "Also triggers when...") with concrete trigger phrases. Not a 4 because both what and when are explicit, not "could be more specific."

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms and abbreviations: "conversion optimization, CRO, A/B test, split test, multivariate test, hypothesis, conversion funnel, funnel audit, experiment design, statistical significance, lift, optimization." Not a 4 because common variations are present rather than "a few missing."

5 / 5

Distinctiveness Conflict Risk

Clear CRO niche with distinct triggers (A/B test, split test, conversion funnel, funnel audit), but standalone terms "optimization" and "lift" are generic and could overlap with unrelated optimization skills. Not a 5 because of this minor overlap risk; not a 3 because the bulk of triggers are CRO-specific.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-skills
Reviewed

Table of Contents

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.