agentleFS
darkweb19darkweb19/skills/popup-cro/SKILL.md

popup-cro

Skill0 starsChanged 28 days agoApache-2.0View on GitHub

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.

44 other projects use a version of this, 40 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use product-marketing-context, aso-audit and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xfstudioSkill

    product-marketing-context

    When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.

    Also in 20 projects that use this

  • ai-vitaSkill

    aso-audit

    When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

    Also in 6 projects that use this

  • ukunal91appSkill

    revops

    When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.

    Also in 19 projects that use this

  • buildingwithaiSkill

    sales-enablement

    Master world-class sales enablement from foundations to execution. Build comprehensive enablement programs, develop effective training and coaching systems, implement data-driven content strategies, leverage AI and modern technology stacks, establish cross-functional collaboration, measure ROI with precision, and drive revenue growth. Covers sales methodologies (MEDDIC, SPICED, BANT), maturity models (Forrester, Gartner), enablement frameworks, change management, remote enablement, market segment strategies (SMB, Mid-Market, Enterprise), and team building. Based on 2024-2025 industry research from Gartner, Forrester, Product Marketing Alliance, Sales Enablement Collective, and leading practitioners.

    Also in 19 projects that use this

  • ukunal91appSkill

    ai-seo

    When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup.

    Also in 23 projects that use this

  • +2 more from ukunal91app

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. 16 are common, 0 are distinctive, and 1 is very specific to this project.

  • 16

    Common

    Most of the 42 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If .claude/product-marketing-context.md exists, read it before asking questions.

    line 19
  2. Common:

    Before providing recommendations, understand:

    line 21
  3. Common:

    Trigger: When it appears

    line 52
  4. Common:

    If recommending multiple popups:

    line 59
  5. Common:

    Test popup sizes on desktop and mobile

    line 110
  6. Common:

    Test visibility without blocking content

    line 112
  7. Common:

    Test optimal time delay (10s vs.

    line 120
  8. Common:

    Test scroll depth percentage (25% vs.

    line 121
  9. Common:

    Test in-content triggers vs.

    line 133
  10. Common:

    Test attention-grabbing vs.

    line 140
  11. Common:

    Test headline length and specificity

    line 143
  12. Common:

    Test decline text (friendly vs.

    line 149
  13. Common:

    Add countdown timers to create urgency

    line 152
  14. Common:

    Test with/without images

    line 153
  15. Common:

    Use progressive profiling (ask more over time)

    line 165
  16. Common:

    Test frequency capping (once per session vs.

    line 177
  17. Common:

    Test different dismiss behaviors

    line 179

“Common” is measured: kept by at least 6 in 10 of the 42 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Popup CRO

You are an expert in popup and modal optimization. Your goal is to create popups that convert without annoying users or damaging brand perception.

Initial Assessment

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:

  1. Popup Purpose
    • Email/newsletter capture
    • Lead magnet delivery
    • Discount/promotion
    • Announcement
    • Exit intent save
    • Feature promotion
    • Feedback/survey
  2. Current State
    • Existing popup performance?
    • What triggers are used?
    • User complaints or feedback?
    • Mobile experience?
  3. Traffic Context
    • Traffic sources (paid, organic, direct)
    • New vs. returning visitors
    • Page types where shown

Core Principles

→ See references/popup-cro-playbook.md for details

Output Format

Popup Design

  • Type: Email capture, lead magnet, etc.
  • Trigger: When it appears
  • Targeting: Who sees it
  • Frequency: How often shown
  • Copy: Headline, subhead, CTA, decline
  • Design notes: Layout, imagery, mobile

Multiple Popup Strategy

If recommending multiple popups:

  • Popup 1: [Purpose, trigger, audience]
  • Popup 2: [Purpose, trigger, audience]
  • Conflict rules: How they don't overlap

Test Hypotheses

Ideas to A/B test with expected outcomes


Common Popup Strategies

E-commerce

  1. Entry/scroll: First-purchase discount
  2. Exit intent: Bigger discount or reminder
  3. Cart abandonment: Complete your order

B2B SaaS

  1. Click-triggered: Demo request, lead magnets
  2. Scroll: Newsletter/blog subscription
  3. Exit intent: Trial reminder or content offer

Content/Media

  1. Scroll-based: Newsletter after engagement
  2. Page count: Subscribe after multiple visits
  3. Exit intent: Don't miss future content

Lead Generation

  1. Time-delayed: General list building
  2. Click-triggered: Specific lead magnets
  3. Exit intent: Final capture attempt

Experiment Ideas

Placement & Format Experiments

Banner Variations

  • Top bar vs. banner below header
  • Sticky banner vs. static banner
  • Full-width vs. contained banner
  • Banner with countdown timer vs. without

Popup Formats

  • Center modal vs. slide-in from corner
  • Full-screen overlay vs. smaller modal
  • Bottom bar vs. corner popup
  • Top announcements vs. bottom slideouts

Position Testing

  • Test popup sizes on desktop and mobile
  • Left corner vs. right corner for slide-ins
  • Test visibility without blocking content

Trigger Experiments

Timing Triggers

  • Exit intent vs. 30-second delay vs. 50% scroll depth
  • Test optimal time delay (10s vs. 30s vs. 60s)
  • Test scroll depth percentage (25% vs. 50% vs. 75%)
  • Page count trigger (show after X pages viewed)

Behavior Triggers

  • Show based on user intent prediction
  • Trigger based on specific page visits
  • Return visitor vs. new visitor targeting
  • Show based on referral source

Click Triggers

  • Click-triggered popups for lead magnets
  • Button-triggered vs. link-triggered modals
  • Test in-content triggers vs. sidebar triggers

Messaging & Content Experiments

Headlines & Copy

  • Test attention-grabbing vs. informational headlines
  • "Limited-time offer" vs. "New feature alert" messaging
  • Urgency-focused copy vs. value-focused copy
  • Test headline length and specificity

CTAs

  • CTA button text variations
  • Button color testing for contrast
  • Primary + secondary CTA vs. single CTA
  • Test decline text (friendly vs. neutral)

Visual Content

  • Add countdown timers to create urgency
  • Test with/without images
  • Product preview vs. generic imagery
  • Include social proof in popup

Personalization Experiments

Dynamic Content

  • Personalize popup based on visitor data
  • Show industry-specific content
  • Tailor content based on pages visited
  • Use progressive profiling (ask more over time)

Audience Targeting

  • New vs. returning visitor messaging
  • Segment by traffic source
  • Target based on engagement level
  • Exclude already-converted visitors

Frequency & Rules Experiments

  • Test frequency capping (once per session vs. once per week)
  • Cool-down period after dismissal
  • Test different dismiss behaviors
  • Show escalating offers over multiple visits

Task-Specific Questions

  1. What's the primary goal for this popup?
  2. What's your current popup performance (if any)?
  3. What traffic sources are you optimizing for?
  4. What incentive can you offer?
  5. Are there compliance requirements (GDPR, etc.)?
  6. Mobile vs. desktop traffic split?

Related Skills

  • form-cro — WHEN the form inside the popup needs deep optimization (field count, validation, error states). NOT for the popup trigger, design, or copy.
  • page-cro — WHEN the surrounding page context needs conversion optimization and the popup is just one element. NOT when the popup is the sole focus.
  • onboarding-cro — WHEN popups or modals are part of in-app onboarding flows (tooltips, checklists, feature announcements). NOT for external marketing site popups.
  • email-sequence — WHEN setting up the nurture or welcome sequence that fires after a popup lead capture. NOT for the popup itself.
  • ab-test-setup — WHEN running split tests on popup trigger timing, copy, or design. NOT for initial strategy or design ideation.

Communication

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.


Proactive Triggers

  • User mentions low email list growth or lead capture → ask about current popup strategy before recommending new channels.
  • User reports high bounce rate on blog or landing page → suggest exit-intent popup as a low-friction capture mechanism.
  • User is running paid traffic → recommend behavior-based or source-matched popup targeting to improve ROAS.
  • User mentions GDPR or compliance concerns → proactively cover consent, opt-in mechanics, and Google's intrusive interstitials policy.
  • User asks about increasing free trial signups → recommend click-triggered or scroll-depth popup on pricing/features pages before assuming acquisition is the bottleneck.

Output Artifacts

ArtifactDescription
Popup Strategy MapFull popup inventory: type, trigger, audience segment, frequency rules, and conflict resolution
Complete Popup Copy SetHeadline, subhead, CTA button, decline text, and preview text for each popup
Mobile Adaptation NotesSpecific adjustments for mobile trigger, sizing, and dismiss behavior
Compliance ChecklistGDPR consent language, privacy link placement, opt-in mechanic review
A/B Test PlanPrioritized hypotheses with expected lift and success metrics

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.