When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
78
Quality
73%
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/popup-cro/SKILL.mdQuality
Discovery
89%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 is a strong skill description with excellent trigger term coverage and clear scope boundaries. The main weakness is that it focuses more on 'when to use' than 'what it does' - the specific capabilities and actions are somewhat vague beyond 'create or optimize'. The cross-references to related skills are a notable strength for disambiguation.
Suggestions
Add 2-3 specific concrete actions to clarify capabilities, e.g., 'Designs popup layouts, writes conversion copy, configures display triggers and targeting rules, optimizes for mobile responsiveness.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (popups, modals, overlays, slide-ins, banners) and mentions 'create or optimize' as actions, but lacks specific concrete actions like 'design A/B tests', 'write copy', or 'configure triggers'. | 2 / 3 |
Completeness | Clearly answers both what (create/optimize popups, modals, overlays, slide-ins, banners for conversion) and when (explicit 'Use when' equivalent at the start, plus specific trigger terms). Also helpfully distinguishes from related skills (form-cro, page-cro). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'exit intent', 'popup conversions', 'modal optimization', 'lead capture popup', 'email popup', 'announcement banner', 'overlay' - these are all terms users naturally use when discussing this topic. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche (popup/modal conversion optimization) and explicitly differentiates from related skills (form-cro for forms outside popups, page-cro for general page optimization), reducing conflict risk. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive popup CRO reference guide with excellent organization and progressive disclosure. However, it leans toward being a knowledge base rather than an actionable skill - it explains concepts well but lacks concrete implementation examples (code, specific tool configurations) and clear validation workflows for testing popup effectiveness.
Suggestions
Add executable code examples for common popup implementations (e.g., JavaScript for exit intent detection, HTML/CSS for modal structure)
Include a concrete validation workflow: implement → test on staging → measure baseline → deploy → verify metrics
Trim the 'Core Principles' section which states UX concepts Claude already understands, and condense the experiment ideas into a more scannable format
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity, particularly in the 'Core Principles' section which states obvious UX concepts Claude already knows. The experiment ideas section is extensive but could be more condensed. | 2 / 3 |
Actionability | Provides good conceptual guidance and copy formulas, but lacks executable code examples for implementation. The output format section describes what to include but doesn't show concrete examples of actual popup code or configuration. | 2 / 3 |
Workflow Clarity | The 'Initial Assessment' section provides a clear starting workflow, but the overall document reads more as a reference guide than a step-by-step process. No validation checkpoints for testing popup implementations or measuring success before deployment. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections and headers. References to related skills (form-cro, page-cro, etc.) are clearly signaled at the end. Content is appropriately structured for scanning and navigation. | 3 / 3 |
Total | 9 / 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 | |
355d067
Table of Contents
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.