IntermediateClaude Code

Launch Strategy

Launch Strategy is an ecommerce AI skill for Claude Code, built for teams working with Codex, Claude Code, OpenClaw. Use it to you are preparing a formal launch for a…

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

What this Skill does

You are preparing a formal launch for a product, feature, or campaign. Do not change every step at once: test Design a phased product Launch Strategy for a new SaaS tool alongside Plan a Product Hunt launch with pre-launch checklist and timeline, then consider keeping… Start with a small test around “Design a phased product Launch Strategy for a new SaaS tool”, then check whether “Plan a Product Hunt launch with pre-launch checklist and timeline” fits the way your team actually works.

02

What makes it different

01

Breaks down a competitor page by operating dimension

The instruction separates positioning, pricing, conversion tactics, user experience, and search content instead of returning one undifferentiated summary.

02

Creates listing and search-content fields together

The source covers product or listing copy alongside SEO-related fields such as keywords, metadata, or image text when those fields are requested.

03

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.
04

Original Skill.md

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

You are a SaaS launch strategist. Gather: what's launching, audience size, owned channels, timeline, past launches, Product Hunt readiness. Use the ORB channel framework: Owned (email, blog, in-product), Rented (social media, communities), Borrowed (partners, PR, influencers). For Product Hunt: start prep 4+ weeks before, build community relationships, craft listing copy, plan engagement. Differentiate by launch type: new product (full GTM), major feature (announcement campaign), minor update (quick ship), pricing change (treat as product update). Every output must be concrete, time-bound, channel-specific, covering launch-day execution AND 30-day post-launch momentum actions. Never launch without a momentum plan.
05

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 Launch Strategy 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 Launch Strategy 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 Launch Strategy 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 Launch Strategy 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.
06

Risks and operating notes

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.

Verify commercial terms before acting

Any price, discount, cost, or margin recommendation is only as current as the values you provide. Recheck live prices, tax, shipping, and margin rules before publishing or sending an offer.

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: