Drafts the logistics part of a return
The source includes return-label or instruction guidance, nearby drop-off information, and the expected refund sequence.
IntermediateClaude Projects
A/B Test Hypothesis Generator
A/B Test Hypothesis Generator is an ecommerce AI skill for Claude Projects, built for teams working with Shopify, WooCommerce, Magento. Use it to improve a product…
- Views
- 0
- Installs
- 0
- Favorites
- 0
System Prompt Original link: no public source found
What this Skill does
You are preparing to improve a product page, shopping journey, or checkout experience. The first decision to test is whether Monthly CRO sprint planning and Post-launch conversion audits hold up together before validating whether one page, guidance, or checkout change works. Start with a small test around “Monthly CRO sprint planning”, then check whether “Post-launch conversion audits” fits the way your team actually works.
What makes it different
Structures the analysis before making a recommendation
The source asks for analysis, classification, ranking, or scoring before it reaches a conclusion or next action.
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.
No installation needed
Copy and paste into a model chat
- Expand and copy the complete original Skill.md below.
- Open a new conversation in a compatible AI model, then paste it into the chat box.
- Add verified task details, run one low-risk example, and review the result before using it in store operations.
Original Skill.md
The complete source is shown below. Copy it from the top right to use it.
You are a CRO (Conversion Rate Optimization) strategist for ecommerce stores. When given store analytics data, you will:
1. IDENTIFY bottlenecks:
- Pages with highest exit rates
- Steps with largest funnel drop-offs
- Segments with lowest conversion rates
- Devices with poor performance
2. GENERATE hypotheses (format: If [change], then [expected result], because [reason]):
- Quick wins (implement in <1 day)
- Medium effort (1-3 days)
- Major tests (1-2 weeks)
3. For each hypothesis, provide:
- Current metric baseline
- Expected improvement range
- Confidence level (Low/Medium/High)
- Sample size needed for statistical significance
- Test duration recommendation
- Revenue impact estimate
4. PRIORITIZE by: Expected Revenue Impact × Implementation Ease
5. SUGGEST test variants:
- Control (current version)
- Variant A (minimal change)
- Variant B (bold change)
- Variant C (radical change — optional)
Your recommendations should be specific, data-backed, and actionable. Never suggest changes without estimated impact.Get started
Starter prompts for the main use cases—copy and use them directly.
01Start with one real task
Do not begin with a store-wide rollout. Pick one reversible task where A/B Test Hypothesis Generator can help you improve product discovery, merchandising, and onsite conversion. Use this when the input boundary, owner, and one primary measure from conversion rate, revenue per visitor, add-to-cart rate, and guardrail metrics are written down.
Show prompt and variablesHide prompt and variables
Start with one real task
Do not begin with a store-wide rollout. Pick one reversible task where A/B Test Hypothesis Generator can help you improve product discovery, merchandising, and onsite conversion. Use this when the input boundary, owner, and one primary measure from conversion rate, revenue per visitor, add-to-cart rate, and guardrail metrics are written down.
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 A/B Test Hypothesis Generator can help you improve product discovery, merchandising, and onsite conversion.
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.
02Prepare the input and guardrails
Collect only the traffic and funnel data, the current page or theme, product rules, and a measurable hypothesis 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
Prepare the input and guardrails
Collect only the traffic and funnel data, the current page or theme, product rules, and a measurable hypothesis 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.
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 traffic and funnel data, the current page or theme, product rules, and a measurable hypothesis 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.
03Inspect the source Skill, then run it
Read the source, installation method, and permission notes before adding A/B Test Hypothesis Generator to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a conversion experiment or merchandising change that a responsible operator can inspect, and it stayed inside the approved boundary.
Show prompt and variablesHide prompt and variables
Inspect the source Skill, then run it
Read the source, installation method, and permission notes before adding A/B Test Hypothesis Generator to a separate test project. Keep commands and Skill text exactly as published. Use this when you have a conversion experiment or merchandising change that a responsible operator can inspect, and it stayed inside the approved boundary.
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 A/B Test Hypothesis Generator 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.
04Review 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, revenue per visitor, add-to-cart rate, and guardrail metrics has a pre-test baseline, and errors and exceptions are logged separately.
Show prompt and variablesHide prompt and variables
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, revenue per visitor, add-to-cart rate, and guardrail metrics has a pre-test baseline, and errors and exceptions are logged separately.
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.
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.
Network-collected; original author unavailable.
The complete available Skill content is cataloged and reviewed; public web material does not currently name the original author. Attribution does not affect its directory visibility or content-based recommendation eligibility.
Network-collected; no author source is listed. This label describes attribution only, not capability, visibility, or recommendation eligibility.
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:
No reviews yet.