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," or "overlay." For forms outside of popups, see form-cro. For general page conversion optimization, see page-cro.
Install with Tessl CLI
npx tessl i github:coreyhaines31/marketingskills --skill popup-croOverall
score
67%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 94%
↑ 1.12xAgent success when using this skill
Validation for skill structure
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 reduce confusion. However, it inverts the typical structure by focusing heavily on 'when to use' while neglecting 'what it does' - the actual capabilities and actions are vague beyond 'create or optimize'. Adding specific actions would significantly improve this description.
Suggestions
Add specific concrete actions at the beginning, e.g., 'Designs popup layouts, configures exit-intent triggers, optimizes timing and targeting rules, A/B tests modal variations, and improves lead capture conversion rates.'
Restructure to lead with capabilities before the 'Use when...' clause to follow the standard pattern and clarify what the skill actually does.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (popups, modals, overlays, slide-ins, banners) and mentions 'conversion purposes' but doesn't list specific concrete actions like 'design exit-intent triggers' or 'optimize timing and targeting rules'. The description focuses more on when to use rather than what it does. | 2 / 3 |
Completeness | The 'when' is very well covered with explicit triggers and cross-references to related skills. However, the 'what' is weak - it says 'create or optimize' but doesn't explain what specific capabilities or actions the skill provides for popup/modal work. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'popups', 'modals', 'overlays', 'slide-ins', 'banners', 'exit intent', 'popup conversions', 'modal optimization', 'lead capture popup', 'email popup', 'announcement banner'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly distinguishes itself with specific popup/modal terminology and explicitly differentiates from related skills (form-cro for forms, page-cro for general page optimization). The cross-references reduce conflict risk significantly. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive coverage of popup CRO concepts, copy formulas, and strategic considerations, making it a solid reference document. However, it lacks executable code examples for implementation, reads more like a knowledge base than actionable instructions, and could be more concise by removing obvious UX principles Claude already understands.
Suggestions
Add executable code snippets for common popup implementations (HTML/CSS/JS for modal, exit intent detection, scroll triggers, localStorage for frequency capping)
Create a clear numbered workflow: 1) Assess context → 2) Choose popup type → 3) Write copy → 4) Implement → 5) Test → 6) Measure, with validation checkpoints
Move the extensive 'Experiment Ideas' section to a separate POPUP-EXPERIMENTS.md file and reference it from the main skill
Remove the 'Core Principles' section or condense to a single line - these are basic UX concepts Claude already knows
| 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. No concrete HTML/CSS/JS snippets for popup creation, trigger implementation, or tracking setup despite being a technical skill. | 2 / 3 |
Workflow Clarity | The 'Output Format' section provides structure for deliverables, but there's no clear step-by-step workflow for creating a popup from start to finish. Missing validation checkpoints for testing popup behavior before deployment. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but it's a monolithic document that could benefit from splitting detailed experiment ideas and compliance sections into separate reference files. The 'Related Skills' section shows good cross-referencing. | 2 / 3 |
Total | 8 / 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.
- 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.