popup-cro
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," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
82
77%
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 ./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 completeness. The explicit cross-references to related skills (form-cro, page-cro) are particularly valuable for disambiguation. The main weakness is that the 'what' portion could be more specific about concrete actions beyond 'create or optimize'.
Suggestions
Add 2-3 specific concrete actions to improve specificity, such as 'design popup layouts, configure trigger conditions, optimize copy and CTAs for conversion'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (popups, modals, overlays) and mentions 'create or optimize' as actions, but lacks specific concrete actions like 'design A/B test variants', 'implement exit-intent triggers', or 'analyze popup conversion rates'. | 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 extensive trigger term list). Also includes helpful cross-references to related skills. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'exit intent', 'popup conversions', 'lead capture popup', 'email popup', 'exit popup', 'scroll trigger', 'sticky bar', 'notification bar', 'collect emails with a popup'. These are highly natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche (overlay/interrupt-style conversion elements) and explicit boundary-setting with cross-references to form-cro and page-cro, reducing conflict risk with related skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%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 skill with strong actionability - specific benchmarks, copy formulas, and concrete experiment ideas make it immediately useful. However, it's verbose for a skill file, explaining concepts Claude already understands and including content that could be split into reference files. The workflow could benefit from explicit validation checkpoints for implementation.
Suggestions
Move the detailed 'Experiment Ideas' section to a separate POPUP-EXPERIMENTS.md file and reference it from the main skill
Add an explicit implementation workflow with validation steps: design → implement → test on staging → measure baseline → iterate
Remove explanatory content Claude already knows (e.g., 'Timing Is Everything' principles, basic definitions of popup types) to reduce token usage by ~25%
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanation that Claude would already know (e.g., explaining what exit intent is, basic popup concepts). Some sections like 'Core Principles' state obvious UX truths. Could be tightened by 20-30%. | 2 / 3 |
Actionability | Provides highly concrete guidance with specific copy formulas, exact timing recommendations (30-60 seconds), benchmark percentages (2-5% conversion), and clear output format templates. The experiment ideas section gives specific, testable variations. | 3 / 3 |
Workflow Clarity | The skill provides good structure for assessment and output format, but lacks explicit validation checkpoints. For popup implementation, there's no clear sequence like 'implement → test → measure → iterate' with specific verification steps between stages. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~400 lines) and could benefit from splitting detailed sections (like Experiment Ideas, Common Popup Strategies) into separate reference files. Related skills are mentioned but inline content is heavy. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%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
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.