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
Multi-popup strategy with conflict rules
Structured popup format
75%
83%
Conflict rules present
92%
100%
A/B test hypotheses
25%
100%
Time-based trigger duration
30%
100%
Mobile sizing guidance
50%
100%
Desktop sizing guidance
83%
100%
Exit intent mobile alternative
100%
100%
First-person CTA copy
100%
100%
Non-manipulative decline text
100%
63%
Frequency capping
75%
75%
Exclude checkout pages
0%
100%
Exit intent differentiation
100%
50%
Without context: $0.2845 · 1m 56s · 11 turns · 60 in / 5,089 out tokens
With context: $0.4551 · 3m 18s · 13 turns · 13 in / 7,901 out tokens
Email capture popup design and compliance
Structured popup format
100%
100%
Single email field
100%
100%
Scroll or time trigger threshold
100%
100%
First-person or specific CTA
100%
100%
Non-manipulative decline text
50%
100%
GDPR compliance
100%
100%
Accessibility requirements
100%
100%
Mobile sizing — no full-screen
100%
100%
Desktop width range
100%
100%
Frequency capping
100%
100%
Non-generic value proposition
100%
100%
Without context: $0.3341 · 2m 21s · 13 turns · 13 in / 5,622 out tokens
With context: $0.3296 · 2m 19s · 9 turns · 9 in / 5,717 out tokens
Audience targeting and page exclusion rules
Exclude converted users
100%
100%
Exclude recently dismissed
100%
100%
Exclude conversion flow pages
100%
83%
Frequency: once per session
100%
100%
Re-show delay 7+ days
100%
100%
New vs. returning targeting
50%
40%
Traffic source targeting
20%
100%
Cookie/localStorage mechanism
100%
100%
Rationale provided
100%
100%
Implementation-ready spec
100%
100%
Without context: $0.2065 · 1m 26s · 8 turns · 9 in / 3,507 out tokens
With context: $0.3080 · 2m 3s · 12 turns · 59 in / 4,573 out tokens
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.