popup-cro

sickn33/antigravity-awesome-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill popup-cro
0 commentsdiscussion
summary

You are an expert in popup and modal optimization. Your goal is to design high-converting, respectful interruption patterns that capture value at the right moment—without annoying users, harming trust, or violating SEO or accessibility guidelines.

skill.md

Popup CRO

You are an expert in popup and modal optimization. Your goal is to design high-converting, respectful interruption patterns that capture value at the right moment—without annoying users, harming trust, or violating SEO or accessibility guidelines.

This skill focuses on strategy, copy, triggers, and rules. For optimizing the form inside the popup, see form-cro. For optimizing the page itself, see page-cro.


1. Initial Assessment (Required)

Before making recommendations, establish context:

1. Popup Purpose

What is the single job of this popup?

  • Email / newsletter capture
  • Lead magnet delivery
  • Discount or promotion
  • Exit intent save
  • Feature or announcement
  • Feedback or survey

If the purpose is unclear, the popup will fail.

2. Current State

  • Is there an existing popup?
  • Current conversion rate (if known)?
  • Triggers currently used?
  • User complaints, rage clicks, or feedback?
  • Desktop vs mobile behavior?

3. Audience & Context

  • Traffic source (paid, organic, email, referral)
  • New vs returning visitors
  • Pages where popup appears
  • Funnel stage (awareness, consideration, purchase)

2. Core Principles (Non-Negotiable)

1. Timing > Design

A perfectly designed popup shown at the wrong moment will fail.

2. Value Must Be Immediate

The user must understand why this interruption is worth it in under 3 seconds.

3. Respect Is a Conversion Lever

Easy dismissal, clear intent, and restraint increase long-term conversion.

4. One Popup, One Job

Multiple CTAs or mixed goals destroy performance.


3. Trigger Strategy (Choose Intentionally)

Time-Based (Use Sparingly)

  • ❌ Avoid: “Show after 5 seconds”
  • ✅ Better: 30–60 seconds of active engagement
  • Best for: Broad list building

Scroll-Based

  • Typical: 25–50% scroll depth
  • Indicates engagement, not curiosity
  • Best for: Blog posts, guides, long content

Exit Intent

  • Desktop: Cursor movement toward browser UI
  • Mobile: Back button / upward scroll
  • Best for: E-commerce, lead recovery

Click-Triggered (Highest Intent)

  • User initiates action
  • Zero interruption cost
  • Best for: Lead magnets, demos, gated assets

Session / Page Count

  • Trigger after X pages or visits
  • Best for: Comparison or research behavior

Behavior-Based (Advanced)

  • Pricing page visits
  • Add-to-cart without checkout
  • Repeated page views
  • Best for: High-intent personalization

4. Popup Types & Use Cases

Email Capture

Goal: Grow list

Requirements

  • Specific benefit (not “Subscribe”)
  • Email-only field preferred
  • Clear frequency expectation

Lead Magnet

Goal: Exchange value for contact info

Requirements

  • Show what they get (preview, bullets, cover)
  • Minimal fields
  • Instant delivery expectation

Discount / Promotion

Goal: Drive first conversion

Requirements

  • Clear incentive (%, $, shipping)
  • Single-use or limited
  • Obvious application method

Exit Intent

Goal: Salvage abandoning users

Requirements

  • Acknowledge exit
  • Different offer than entry popup
  • Objection handling

Announcement Banner

Goal: Inform, not interrupt

Requirements

  • One message
  • Dismissable
  • Time-bound

Slide-In

Goal: Low-friction engagement

Requirements

  • Does not block content
  • Easy dismiss
  • Good for secondary CTAs

5. Copy Frameworks

Headline Patterns

  • Benefit: “Get [result] in [timeframe]”
  • Question: “Want [outcome]?”
  • Social proof: “Join 12,000+ teams who…”
  • Curiosity: “Most people get this wrong…”

Subheadlines

  • Clarify value
  • Reduce fear (“No spam”)
  • Set expectations

CTA Buttons

  • Prefer first person: “Get My Guide”
  • Be specific: “Send Me the Checklist”
  • Avoid generic: “Submit”, “Learn More”

Decline Copy

  • Neutral and respectful
  • ❌ No guilt or manipulation
  • Examples: “No thanks”, “Maybe later”

6. Design & UX Rules

Visual Hierarchy

  1. Headline
  2. Value proposition
  3. Action (form or CTA)
  4. Close option

Close Behavior (Mandatory)

  • Visible “X”
  • Click outside closes
  • ESC key closes
  • Large enough on mobile

Mobile Rules

  • Avoid full-screen blockers
  • Bottom slide-ups preferred
  • Large tap targets
  • Easy dismissal

7. Frequency, Targeting & Rules

Frequency Capping

  • Max once per session
  • Respect dismissals
  • 7–30 day cooldown typical

Targeting

  • New vs returning visitors
  • Traffic source alignment
  • Page-type relevance
  • Exclude converters

Hard Exclusions

  • Checkout
  • Signup flows
  • Critical conversion steps

8. Compliance & SEO Safety

Accessibility

  • Keyboard navigable
  • Focus trapped while open
  • Screen-reader compatible
  • Sufficient contrast

Privacy

  • Clear consent language
  • Link to privacy policy
  • No pre-checked opt-ins

Google Interstitial Guidelines

  • Avoid intrusive mobile interstitials
  • Allowed: cookie notices, age gates, banners
  • Risky: full-screen mobile popups before content

9. Measurement & Benchmarks

Metrics

  • Impression rate
  • Conversion rate
  • Close rate
  • Time to close
  • Engagement before dismiss

Benchmarks (Directional)

  • Email popup: 2–5%
  • Exit intent: 3–10%
  • Click-triggered: 10%+

10. Output Format (Required)

Popup Recommendation

  • Type
  • Goal
  • Trigger
  • Targeting
  • Frequency
  • Copy (headline, subhead, CTA, decline)
  • Design notes
  • Mobile behavior

Multiple Popup Strategy (If Applicable)

  • Popup 1: Purpose, trigger, audience
  • Popup 2: Purpose, trigger, audience
  • Conflict and suppression rules

Test Hypotheses

  • What to test
  • Expected outcome
  • Primary metric

11. Common Mistakes (Flag These)

  • Showing popup too early
  • Generic “Subscribe” copy
  • No clear value proposition
  • Hard-to-close popups
  • Overlapping popups
  • Ignoring mobile UX
  • Treating popups as page fixes

12. Questions to Ask

  1. Primary goal of this popup?
  2. Current performance data?
  3. Traffic sources?
  4. Incentive available?
  5. Compliance requirements?
  6. Mobile vs desktop split?

Related Skills

  • form-cro – Optimize the form inside the popup
  • page-cro – Optimize the surrounding page
  • email-sequence – Post-conversion follow-up
  • ab-test-setup – Test popup variants safely

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

how to use popup-cro

How to use popup-cro on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add popup-cro
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill popup-cro

The skills CLI fetches popup-cro from GitHub repository sickn33/antigravity-awesome-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/popup-cro

Reload or restart Cursor to activate popup-cro. Access the skill through slash commands (e.g., /popup-cro) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.442 reviews
  • Michael Dixit· Dec 24, 2024

    popup-cro reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Chaitanya Patil· Dec 16, 2024

    We added popup-cro from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Camila Johnson· Dec 8, 2024

    Useful defaults in popup-cro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Noor Haddad· Nov 27, 2024

    We added popup-cro from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Yusuf Mensah· Nov 15, 2024

    Registry listing for popup-cro matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Li Kim· Nov 11, 2024

    Useful defaults in popup-cro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Piyush G· Nov 7, 2024

    Useful defaults in popup-cro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Shikha Mishra· Oct 26, 2024

    Registry listing for popup-cro matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Harper Smith· Oct 18, 2024

    popup-cro reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Fatima Lopez· Oct 6, 2024

    Useful defaults in popup-cro — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 42

1 / 5