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," or "why isn't this page working." 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.
82
Quality
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/skills/page-cro/SKILL.mdQuality
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 terms and distinctiveness, with excellent cross-references to related skills that prevent conflicts. However, it focuses heavily on 'when' to use the skill while neglecting 'what' the skill actually does - it never describes the concrete actions or analysis methods involved in optimizing marketing pages.
Suggestions
Add specific actions the skill performs, e.g., 'Analyzes page structure, copy, CTAs, and visual hierarchy to identify conversion blockers and recommend improvements'
Include concrete deliverables or outputs, e.g., 'Provides prioritized recommendations, A/B test suggestions, and copy rewrites'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (marketing pages, CRO) and lists page types (homepage, landing pages, pricing pages, feature pages, blog posts), but doesn't describe concrete actions like 'analyze copy', 'restructure CTAs', or 'improve headlines'. | 2 / 3 |
Completeness | Strong 'when' clause with explicit triggers and helpful cross-references to related skills, but the 'what' is weak - it says 'optimize, improve, or increase conversions' without explaining what actions or analysis the skill actually performs. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'CRO', 'conversion rate optimization', 'this page isn't converting', 'improve conversions', 'why isn't this page working', plus specific page types like 'landing pages', 'pricing pages'. | 3 / 3 |
Distinctiveness Conflict Risk | Excellent distinctiveness with clear scope boundaries and explicit cross-references to related skills (signup-flow-cro, onboarding-cro, form-cro, popup-cro), making it very clear when to use this skill vs others. | 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 frameworks are specific and immediately usable with concrete examples. Minor verbosity in explaining concepts Claude already understands (basic marketing terminology) prevents a perfect conciseness score, but overall this is a high-quality skill.
Suggestions
Trim explanatory text for concepts Claude knows (e.g., remove 'Feature-focused instead of benefit-focused' explanation, just list it as an issue to check)
Consider moving the 'Common issues' and 'Types to look for' lists to a reference file to reduce main skill length
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation that Claude would already know (e.g., explaining what 'feature-focused vs benefit-focused' means, basic CTA concepts). Some sections could be tightened without losing clarity. | 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. | 3 / 3 |
Workflow Clarity | Clear sequential analysis framework (7 dimensions in order of impact), explicit output structure (Quick Wins → High-Impact → Test Ideas → Copy Alternatives), and logical flow from assessment to recommendations. For a non-destructive analysis task, validation checkpoints aren't critical. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of one-level-deep reference to experiments.md for detailed content, and clear navigation to related skills. Content is appropriately split between overview and detailed frameworks. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
355d067
- 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.