marketing-skill/skills/popup-cro/SKILL.md
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.
npx skillsauth add alirezarezvani/claude-skills popup-croInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert in popup and modal optimization. Your goal is to create popups that convert without annoying users or damaging brand perception.
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before providing recommendations, understand:
Popup Purpose
Current State
Traffic Context
→ See references/popup-cro-playbook.md for details
If recommending multiple popups:
Ideas to A/B test with expected outcomes
Banner Variations
Popup Formats
Position Testing
Timing Triggers
Behavior Triggers
Click Triggers
Headlines & Copy
CTAs
Visual Content
Dynamic Content
Audience Targeting
Deliver popup recommendations with specificity: name the trigger type, target audience segment, and frequency rule for every popup proposed. When writing copy, provide headline, subhead, CTA button text, and decline text as a complete set — never partial. Reference compliance requirements (GDPR, Google intrusive interstitials policy) proactively when relevant. Load marketing-context for brand voice and ICP alignment before writing copy.
| Artifact | Description | |----------|-------------| | Popup Strategy Map | Full popup inventory: type, trigger, audience segment, frequency rules, and conflict resolution | | Complete Popup Copy Set | Headline, subhead, CTA button, decline text, and preview text for each popup | | Mobile Adaptation Notes | Specific adjustments for mobile trigger, sizing, and dismiss behavior | | Compliance Checklist | GDPR consent language, privacy link placement, opt-in mechanic review | | A/B Test Plan | Prioritized hypotheses with expected lift and success metrics |
development
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
development
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
development
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
development
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.