page-cro

When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," "why isn't this page working," "my landing page sucks," "nobody's converting," "low conversion rate," "bounce rate is too high," "people leave without signing up," or "this page needs work." Use this even if the user just shares a URL and asks for feedback — they probably want conversion help. For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.

1.28x

Quality

78%

Does it follow best practices?

Impact

94%

1.28x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/page-cro/SKILL.md

Quality

Discovery

72%

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

This description excels at trigger term coverage and distinctiveness through explicit skill boundaries, making it easy for Claude to know when to select it. However, it's weak on specificity - it tells Claude when to use the skill but not what concrete actions or analysis the skill actually performs. Adding specific capabilities would make this a strong description.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Analyzes page structure, headlines, CTAs, social proof placement, and value proposition clarity to identify conversion blockers and recommend improvements.'

Restructure to lead with capabilities before the extensive trigger list, following the pattern: '[What it does]. Use when [triggers].'

Dimension	Reasoning	Score
Specificity	Names the domain (marketing pages, CRO) and mentions page types (homepage, landing pages, pricing pages), but doesn't list specific concrete actions like 'analyze headlines', 'improve CTAs', or 'restructure value propositions'. The description focuses more on when to use it than what it actually does.	2 / 3
Completeness	The 'when' is exceptionally well-covered with explicit triggers and user phrases, but the 'what' is weak - it says 'optimize, improve, or increase conversions' without explaining what specific actions or analysis the skill performs. The description tells Claude when to select it but not what capabilities it provides.	2 / 3
Trigger Term Quality	Excellent coverage of natural user phrases including 'CRO', 'conversion rate optimization', 'this page isn't converting', 'my landing page sucks', 'nobody's converting', 'low conversion rate', 'bounce rate is too high', and 'people leave without signing up'. These are realistic phrases users would actually say.	3 / 3
Distinctiveness Conflict Risk	Clearly distinguishes itself from related skills by explicitly listing boundaries (signup-flow-cro, onboarding-cro, form-cro, popup-cro) and specifying its scope as marketing pages. This cross-referencing significantly reduces conflict risk.	3 / 3
	Total	10 / 12 Passed

Implementation

85%

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

This is a well-structured CRO skill with strong actionability and clear workflow. The main weakness is some verbosity in explaining concepts Claude already understands (basic CRO principles, what makes good headlines). The frameworks and output structure are immediately usable and appropriately reference related skills.

Suggestions

Trim explanatory content in sections like 'Strong headline patterns' and 'Common objections' - Claude knows these concepts; focus on project-specific patterns or unique frameworks instead

Consider condensing the 'CRO Analysis Framework' section by removing obvious items (e.g., 'Is there enough white space?') and keeping only non-obvious or project-specific guidance

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some explanatory text that Claude would already know (e.g., explaining what makes headlines strong, basic CRO concepts). Some sections like 'Common objections to address' list obvious items that don't add unique value.	2 / 3
Actionability	Provides concrete, specific guidance throughout with clear patterns (headline formulas, CTA examples with weak vs. strong comparisons), specific checklists, and actionable output format. The frameworks are immediately usable without additional interpretation.	3 / 3
Workflow Clarity	Clear sequential analysis framework ('in order of impact'), well-structured output format with prioritized recommendations (Quick Wins → High-Impact → Test Ideas), and logical flow from initial assessment through page-specific frameworks. The process is unambiguous.	3 / 3
Progressive Disclosure	Well-organized with clear sections, appropriate use of external reference (experiments.md), and related skills clearly signaled at the end. Content is appropriately structured for the skill's scope without being monolithic or requiring deep nesting.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: coreyhaines31/marketingskills
Commit: 9d4d29a

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.