popup-cro

Overview of popup-cro skill

What popup-cro is for

The popup-cro skill helps you create or optimize popups, modals, slide-ins, sticky bars, and other interrupt-style conversion elements. Its focus is not just writing popup copy, but improving the full conversion setup: purpose, trigger timing, offer clarity, form friction, mobile experience, frequency rules, and brand-safe UX.

Who should use this popup-cro skill

Best fit readers are marketers, founders, growth teams, CRO practitioners, and AI-agent users who need a structured way to design a popup for Conversion without defaulting to generic “write me a popup” prompts. It is especially useful when the job is lead capture, discount offers, exit-intent saves, announcements, feature promotion, or survey/feedback collection.

The real job-to-be-done

Most users do not need “a popup.” They need a popup that appears on the right page, at the right moment, with the right offer and low enough friction to convert without hurting trust. popup-cro is built for that practical decision-making, not just headline generation.

What makes popup-cro different

The strongest differentiator is that popup-cro starts from conversion context. It explicitly checks for product marketing context first, then asks about popup purpose, current performance, trigger setup, complaints, traffic source, visitor type, and page context. That makes it more useful than ordinary prompting when you need recommendations that fit the business rather than generic overlay patterns.

When popup-cro is a good fit

Use popup-cro when the request involves:

• Exit-intent popups
• Email capture modals
• Discount or promo overlays
• Announcement bars
• Slide-ins and sticky bars
• Scroll or time-triggered popups
• Lead magnet delivery inside a popup

If you need optimization for an embedded form rather than a popup, the repository points users toward form-cro. For broader page-level conversion work, page-cro is the closer fit.

What matters before you install

This skill is content-first and workflow-first. It has a substantial SKILL.md and an evals/evals.json, but no helper scripts or reference folders. That means adoption is easy if you want prompt guidance, heuristics, and examples. It is less compelling if you are expecting automation, code integrations, or implementation templates for a specific popup platform.

How to Use popup-cro skill

popup-cro install and setup

Install the popup-cro skill from the repository with:

npx skills add https://github.com/coreyhaines31/marketingskills --skill popup-cro

After install, read:

1. SKILL.md
2. evals/evals.json

SKILL.md contains the operating guidance. evals/evals.json shows what good outputs are expected to include, which is often the fastest way to understand how to invoke the skill well.

Read this file path first

Start with skills/popup-cro/SKILL.md if you are browsing the repo directly:
https://github.com/coreyhaines31/marketingskills/tree/main/skills/popup-cro

This is the core source of truth for the popup-cro guide. The evals file is useful second because it reveals practical expectations such as trigger guidance, copy structure, frequency rules, and rough benchmarks.

What input popup-cro needs

To get strong output from popup-cro, provide:

• Popup goal: email capture, discount, exit save, announcement, survey, feature push
• Audience: new visitors, returning visitors, trial users, shoppers, blog readers
• Page type: homepage, product page, pricing page, blog post, cart
• Trigger: exit intent, scroll depth, time delay, inactivity, click
• Offer: discount, lead magnet, demo, newsletter, update
• Current pain: low conversion, high dismissal, mobile complaints, poor lead quality
• Constraints: brand tone, legal limits, mobile UX, form fields, tool/platform

Without these, the skill can still help, but it will be forced to guess the most important conversion variables.

Check product context before prompting

One concrete workflow from the repository matters: popup-cro tells the agent to check for .agents/product-marketing-context.md first, or .claude/product-marketing-context.md in older setups. If that file exists, use it before asking new questions.

This is a practical differentiator. It helps the popup-cro skill align popup messaging to product positioning, objections, audience language, and offers already defined elsewhere.

Turn a rough request into a usable prompt

Weak prompt:
“Write a popup for my SaaS.”

Stronger popup-cro usage prompt:
“Use popup-cro to design an exit-intent email capture popup for our SaaS landing page. Audience is first-time visitors from paid search. Product is a social media scheduling tool for small agencies. Goal is to collect email leads from visitors who do not start a trial. Offer can be a checklist or extended trial, but not a discount. We want mobile-safe UX, minimal fields, and frequency rules that avoid annoying repeat visitors.”

That stronger input lets the skill make decisions on offer type, trigger timing, copy angle, form length, and suppression logic.

What popup-cro will usually help you decide

In practice, the skill is most useful for decisions like:

• Which popup type fits the goal
• When the popup should trigger
• What incentive is strong enough
• How many form fields to ask for
• What copy structure reduces resistance
• How often to reshow or suppress the popup
• How mobile should differ from desktop

These decisions matter more than clever wording alone.

Suggested workflow for real projects

A practical popup-cro usage workflow:

1. Gather product and audience context.
2. Define one primary conversion action.
3. State current popup or page problem.
4. Ask the skill for recommended popup type and trigger.
5. Ask for headline, body, CTA, and close treatment.
6. Ask for frequency and exclusion rules.
7. Revise for traffic source and device differences.
8. Compare output against your popup tool’s implementation limits.

This sequence produces better outputs than asking for final copy first.

What the evals reveal about expected output

The repository’s evals show that good popup-cro output should often include:

• Recognition of popup type
• Trigger logic such as exit intent
• A compelling, value-led headline
• Minimal form friction
• Frequency rules after dismissal
• Copy formulas instead of random phrasing
• Performance framing, including rough benchmarks where appropriate

That is useful for install decisions: this skill is not just a copywriter; it pushes toward a more complete CRO recommendation.

Practical tips that improve output quality

Ask for recommendations in the language of tradeoffs:

• “Maximize lead volume”
• “Protect brand trust”
• “Keep mobile experience clean”
• “Prioritize qualified leads over raw submissions”

Those priorities materially change what popup-cro should suggest. For example, a lead-quality goal may justify a more specific offer or slightly more friction, while a volume goal often pushes toward email-only capture and clearer immediate value.

Where popup-cro can be too generic

If you provide no offer, no audience, and no traffic context, the output will likely become broadly correct but less decision-useful. The skill is strongest when the popup is attached to a real funnel stage and a real user segment.

Best-fit use cases for popup-cro for Conversion

popup-cro for Conversion is strongest when popup performance depends on intent and timing, such as:

• Saving abandoning visitors with an exit offer
• Converting blog readers into newsletter subscribers
• Offering first-visit discounts on ecommerce pages
• Promoting a feature or trial at a high-intent moment
• Capturing leads from paid traffic with a tailored promise

It is less valuable when the request is purely visual design or front-end implementation code.

popup-cro skill FAQ

Is popup-cro better than a normal prompt?

Usually yes, if you need more than copy. A normal prompt may produce a headline and CTA. The popup-cro skill is more likely to structure the problem around trigger timing, value proposition, field count, dismissal handling, and visitor context.

Is popup-cro beginner-friendly?

Yes. The skill itself is readable and scenario-driven. Beginners can use it effectively if they provide basic context: goal, audience, page, offer, and trigger idea. You do not need deep CRO expertise to get useful output.

Does popup-cro include implementation code?

No clear evidence suggests code helpers or platform-specific scripts. This is a strategy-and-prompting skill, not a plugin or popup builder integration. You may still use its output inside tools like your CMS, tag manager, or popup platform.

When should I not use popup-cro?

Skip popup-cro if your task is:

• An embedded form rather than a popup
• Whole-page messaging optimization
• Pure front-end engineering
• Analytics instrumentation setup only

In those cases, the repository itself suggests adjacent skills may fit better.

Can popup-cro help with mobile popup decisions?

Yes. The source explicitly calls out mobile experience during initial assessment. That matters because many popup ideas that look fine on desktop become intrusive, hard to close, or low-converting on mobile.

Does popup-cro cover only exit-intent popups?

No. Exit-intent is a major use case, but the skill also covers lead capture, discounts, announcements, feature promotion, surveys, overlays, slide-ins, and sticky bars.

Is popup-cro useful without current performance data?

Yes, but it is better with it. If you know current conversion rate, dismissal rate, complaint patterns, or traffic source splits, the recommendations become far more specific and credible.

How to Improve popup-cro skill

Give popup-cro sharper business context

The biggest quality jump comes from better inputs, not longer prompts. Include:

• Business model
• Core offer
• Visitor intent
• Funnel stage
• Traffic source
• Success metric

That lets popup-cro recommend a popup strategy that fits the economics of your funnel instead of generic best practices.

State the downside you want to avoid

Good popup decisions are about balance. Tell the skill what failure matters most:

• “Do not hurt brand perception”
• “Avoid low-quality discount seekers”
• “Do not interrupt mobile checkout”
• “Minimize repeat annoyance”

This changes trigger timing, copy aggressiveness, and reshow policy.

Provide the existing popup if you have one

If you already run a popup, paste the current:

• Headline
• Body copy
• CTA
• Trigger rules
• Frequency settings
• Form fields
• Target pages

Then ask popup-cro to diagnose likely friction points. This is usually more valuable than asking for a fresh concept from zero.

Ask for one recommendation layer at a time

For stronger output, split requests into stages:

1. Strategy
2. Trigger and targeting
3. Offer and copy
4. Frequency and suppression
5. Test variations

This avoids shallow “all-in-one” answers and makes the popup-cro guide more actionable.

Use concrete audience language in the prompt

Weak:
“Visitors to our site”

Better:
“First-time visitors from non-brand Google Ads who viewed pricing but did not start checkout”

Specific audience language improves the skill’s recommendations on urgency, copy tone, incentive strength, and whether the popup should appear at all.

Common failure modes with popup-cro usage

Typical weak results come from:

• No clear conversion goal
• No page context
• Asking for copy before strategy
• Ignoring mobile constraints
• Using the same popup for every traffic source
• Overloading the form with fields

Most of these are fixed by giving the skill more funnel detail.

Iterate after the first output

Do not stop at version one. Ask:

• “Make this less aggressive”
• “Adapt for returning visitors”
• “Create a lower-friction mobile version”
• “Rewrite for higher lead quality”
• “Suggest an A/B test against the current popup”

That iterative use is where popup-cro becomes materially better than a one-shot generic prompt.

Use evals to refine your own prompt standard

The evals/evals.json file is not just for testing. It shows what the repository considers a complete answer. Use those expectations as a checklist for your own prompts so every popup-cro install in a team workflow produces more consistent outputs.

Improve popup-cro outputs with constraints

Useful constraints make recommendations more realistic:

• “No discounting allowed”
• “Email only”
• “Must work above legal consent text”
• “Desktop only”
• “Cannot show on checkout”
• “Need an easy close option”

Constraints force better conversion tradeoffs and reduce unusable answers.

How to know popup-cro is working well

The output is strong when it gives you:

• A clear popup type choice
• A reasoned trigger recommendation
• Copy tied to visitor intent
• Friction-aware form guidance
• Frequency rules
• Mobile considerations
• At least one sensible test direction

If you only get a catchy headline, you are not yet using the popup-cro skill to its full value.