BeginnerCorey Haines

Popup CRO

Popup CRO is an ecommerce AI skill for Corey Haines, built for teams working with Codex, Claude Code, OpenClaw. Use it to improve a product page, shopping journey, or…

Views
0
Installs
0
Favorites
0
Supported Platforms
Codex · Claude Code · OpenClaw
01

What this Skill does

You are preparing to improve a product page, shopping journey, or checkout experience. The first decision to test is whether Creating a new email capture popup for a website and Optimizing existing popup conversion rates through A/B testing hold up together before validating… Start with a small test around “Creating a new email capture popup for a website”, then check whether “Optimizing existing popup conversion rates through A/B testing” fits the way your team actually works.

02

What makes it different

01

Includes a retention step after resolution

It ends the workflow with a recovery offer, such as a discount code, after the return outcome has been explained.

02

Turns customer feedback into structured output

The source asks the model to group, classify, answer, or prioritize review feedback rather than treating every comment as an isolated case.

03

Before you use it

Actual return-logistics information

Provide the approved label process, carrier or drop-off details, and the real refund timing. The source text can format these instructions but cannot look them up.

04

No installation needed

Copy and paste into a model chat
  1. Expand and copy the complete original Skill.md below.
  2. Open a new conversation in a compatible AI model, then paste it into the chat box.
  3. Add verified task details, run one low-risk example, and review the result before using it in store operations.
05

Original Skill.md

The complete source is shown below. Copy it from the top right to use it.

You are an expert in popup and modal optimization. Create popups that convert without annoying users or damaging brand perception. Understand purpose (email capture/lead magnet/discount/exit intent), current state, and traffic context. Apply principles: timing matters, value must be obvious, respect the user (easy dismiss, remember preferences). Recommend trigger strategy (time/scroll/exit-intent/click/behavior) with rationale. Design with visual hierarchy: headline → value prop → form/CTA → close option. Provide copy formulas and A/B testing plan across placement, triggers, messaging, and frequency capping. For mobile, prefer bottom slide-ups over full-screen overlays.
06

Get started

Starter prompts for the main use cases—copy and use them directly.

01

Start with one real task

Do not begin with a store-wide rollout. Pick one reversible task where Popup CRO can help you plan campaigns, produce channel-ready material, and control advertising work. Use this when the input boundary, owner, and one primary measure from conversion rate, cost per acquisition, contribution margin, and unsubscribe rate are written down.

Show prompt and variablesHide prompt and variables
Use the Skill above to help me with this task: Start with one real task.

Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]

Do not begin with a store-wide rollout. Pick one reversible task where Popup CRO can help you plan campaigns, produce channel-ready material, and control advertising work.

Return a practical result and clearly flag anything that needs human review.

Replace these variables

[TASK_DETAILS]
The facts, context, or source material for this task.
[CONSTRAINTS]
Replace this placeholder with your verified store-specific information.
02

Prepare the input and guardrails

Collect only the the offer, audience, approved claims, brand voice, channel limits, and budget needed for this test. Remove unrelated personal data and state which actions must never run automatically. Use this when every input has a known source, sensitive fields are minimized, and the approver knows what the trial can read or change.

Show prompt and variablesHide prompt and variables
Use the Skill above to help me with this task: Prepare the input and guardrails.

Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]

Collect only the the offer, audience, approved claims, brand voice, channel limits, and budget needed for this test. Remove unrelated personal data and state which actions must never run automatically.

Return a practical result and clearly flag anything that needs human review.

Replace these variables

[TASK_DETAILS]
The facts, context, or source material for this task.
[CONSTRAINTS]
Replace this placeholder with your verified store-specific information.
03

Inspect the source Skill, then run it

Read the source, installation method, and permission notes before adding Popup CRO to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a campaign brief or marketing asset that a responsible operator can inspect, and it stayed inside the approved boundary.

Show prompt and variablesHide prompt and variables
Use the Skill above to help me with this task: Inspect the source Skill, then run it.

Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]

Read the source, installation method, and permission notes before adding Popup CRO to a separate test project. Keep commands and Skill text exactly as published.

Return a practical result and clearly flag anything that needs human review.

Replace these variables

[TASK_DETAILS]
The facts, context, or source material for this task.
[CONSTRAINTS]
Replace this placeholder with your verified store-specific information.
04

Review it against a baseline

Do not judge the result by fluency. Compare it with source data, the current SOP, and the pre-test baseline; record factual errors, omissions, and editing time. Use this when conversion rate, cost per acquisition, contribution margin, and unsubscribe rate has a pre-test baseline, and errors and exceptions are logged separately.

Show prompt and variablesHide prompt and variables
Use the Skill above to help me with this task: Review it against a baseline.

Task details: [TASK_DETAILS]
Constraints or policies to follow: [CONSTRAINTS]

Do not judge the result by fluency. Compare it with source data, the current SOP, and the pre-test baseline; record factual errors, omissions, and editing time.

Return a practical result and clearly flag anything that needs human review.

Replace these variables

[TASK_DETAILS]
The facts, context, or source material for this task.
[CONSTRAINTS]
Replace this placeholder with your verified store-specific information.
07

Risks and operating notes

Do not invent labels, links, locations, or timelines

This text can draft return instructions, but it does not verify a carrier label, local drop-off point, parcel status, or refund-processing time. Use only details supplied by your actual return system.

Only offer approved recovery incentives

The instruction may suggest an exchange, store credit, or discount code. Confirm the offer amount, eligibility, stacking rules, and margin impact before it is sent to a customer.

Use the minimum customer data needed

The workflow may need an order reference or case facts. Do not paste payment details, full addresses, or unrelated order history into a model conversation; redact them unless they are essential to the decision.

Keep claims tied to verified product facts

When this instruction drafts marketing or product content, review specifications, comparisons, performance claims, and testimonials against approved evidence before publishing.

Community rating results

Task effectiveness
Setup and ease of use
Reliability and guardrails
Documentation clarity
Time to first useful result

No reviews yet.

Leave a review

Rate every dimension, then share your real experience.

Task effectiveness
Setup and ease of use
Reliability and guardrails
Documentation clarity
Time to first useful result
Author / maintainer

Corey Haines

Creator of Marketing Skills, an open-source collection of reusable agent skills for content, SEO, conversion, launch, and growth work.

Risk, permissions, and limitations

Review third-party permission scopes before providing store data. Never paste payment credentials, customer passwords, or unnecessary personal data into a model. Outputs must be checked by the operator responsible for the workflow.

Content checked: