popup-generator
The popup-generator skill guides the design and optimization of popups and modals for lead capture, newsletter signups, and offer promotion. Use it when creating or improving popups, modals, lightboxes, or exit-intent overlays, focusing on conversion-friendly timing (scroll percentage, time delay, exit intent), mobile-safe design that avoids Google penalties for intrusive interstitials, and best practices like value-first messaging, friction-free exits, and personalization for returning visitors or cart abandoners.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/popup-generator && cp -r /tmp/popup-generator/skills/components/conversion/popup ~/.claude/skills/popup-generatorSKILL.md
# Components: Popup / Modal Guides popup and modal design for conversion. Well-designed popups can achieve up to 25% conversion; poorly timed or intrusive ones hurt UX and SEO. Google penalizes intrusive mobile popups. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for offers and audience. Identify: 1. **Goal**: Newsletter, discount, lead magnet, demo 2. **Trigger**: Time delay, scroll %, exit intent, click 3. **Mobile**: Critical; smaller screens = easier to interrupt ## Best Practices ### Timing and Context - **Avoid**: Popup on page load; users hate it - **Prefer**: After engagement (scroll 25-50%, time on page, exit intent) - **Personalize**: Returning visitors, cart abandoners, discount users - **Value-first**: Offer genuine value; act as "helpful teammate" not spam ### Design - **Short copy**: Clear headline, one benefit, single CTA - **Visual hierarchy**: Guide attention to CTA; don't distract - **Easy exit**: Clear X, visible "No Thanks"; friction-free exit increases trust and conversion - **Brand consistency**: Build instant comfort ### Mobile - **Size**: Fit screen; thumb-friendly close - **Lightweight**: Avoid heavy assets; affects LCP - **SEO**: Google penalizes intrusive interstitials; avoid full-page takeover on mobile ### Avoid - Dark patterns (fake close, hidden options) - Too early or too frequent - Multiple popups in one session - Blocking content without clear value ## Triggers | Trigger | Use | |---------|-----| | **Time delay** | 5-15s typical; after some engagement | | **Scroll %** | 25-50% read; user invested | | **Exit intent** | Mouse leaving viewport; last chance | | **Click** | User-initiated; least intrusive | ## Output Format - **Offer** and copy - **Trigger** (timing, scroll, exit intent) - **Design** (size, CTA, exit) - **Mobile** checklist ## Related Skills - **signup-login-page-generator**: Full account signup → dedicated page preferred; popup for lightweight capture - **landing-page-generator**: Lead capture popups on landing pages; popup as alternative to full-page form - **newsletter-signup-generator**: Popup often contains signup form - **cta-generator**: Popup CTA design - **top-banner-generator**: Alternative to popup; less intrusive for announcements - **sidebar-generator**: Alternative for CTAs; in-content often converts better - **brand-visual-generator**: Popup styling
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.