Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Popup Cro

ASecurity

Create and optimize popups, modals, overlays, slide-ins, and banners to increase conversions without harming user experience or brand trust.

429 stars
0 votes
0 copies
0 views
Added 9/22/2026
ai-agentsrustgoperformance

Works with

cursorcli

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 9/22/2026

$npx -y skills add aiskillstore/marketplace --skill popup-cro --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Popup Cro?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Popup Cro
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aiskillstore-popup-cro-marketplace/badge)](https://www.skillsdirectory.com/skills/aiskillstore-popup-cro-marketplace)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: popup-cro
description: Create and optimize popups, modals, overlays, slide-ins, and banners to increase conversions without harming user experience or brand trust.
---
# 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

Attribution

aiskillstoreaiskillstore
View sourceSee grades on GitHubMore from aiskillstore →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →