Launch Strategy
freekmurze/dotfiles
When the user wants to plan a product launch, feature announcement, or release strategy.
Plan and execute product launches with week-by-week timelines and channel-specific playbooks.
Install Launch Strategy
$ npx skills add OpenClaudia/openclaudia-skills --skill launch-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OpenClaudia/openclaudia-skills launch-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/launch-strategy .claude/skills/launch-strategy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "launch-strategy" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/launch-strategy into .claude/skills/launch-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/launch-strategyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add OpenClaudia/openclaudia-skills --skill launch-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OpenClaudia/openclaudia-skills launch-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/launch-strategy .agents/skills/launch-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "launch-strategy" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/launch-strategy into .agents/skills/launch-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenClaudia/openclaudia-skills --skill launch-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OpenClaudia/openclaudia-skills launch-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/launch-strategy .cursor/skills/launch-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "launch-strategy" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/launch-strategy into .cursor/skills/launch-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/OpenClaudia/openclaudia-skills.git --path skills/launch-strategy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add OpenClaudia/openclaudia-skills --skill launch-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OpenClaudia/openclaudia-skills launch-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/launch-strategy .gemini/skills/launch-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "launch-strategy" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/launch-strategy into .gemini/skills/launch-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install OpenClaudia/openclaudia-skills launch-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add OpenClaudia/openclaudia-skills --skill launch-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/launch-strategy .github/skills/launch-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "launch-strategy" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/launch-strategy into .github/skills/launch-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenClaudia/openclaudia-skills --skill launch-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OpenClaudia/openclaudia-skills launch-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/launch-strategy .opencode/skills/launch-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "launch-strategy" agent skill from https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/launch-strategy into .opencode/skills/launch-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
launch-strategy- GitHub stars
- 711
- Token cost
- ~1.6k tokens
- SKILL.md length
- 697 words
- Files
- 1
- Skills in repo
- 74
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan and execute product launches with week-by-week timelines and channel-specific playbooks.
- Works in 7 steps: Gather Launch Context → Launch Type Selection → Pre-Launch (8-4 Weeks Before) → …
- The user asks about launching a product
- SKILL.md covers Step 1: Gather Launch Context, Step 2: Launch Type Selection, Step 3: Pre-Launch (8-4 Weeks… and Step 4: Launch Week, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Launch Strategy is an agent skill from OpenClaudia/openclaudia-skills. Plan and execute product launches with week-by-week timelines and channel-specific playbooks. Use when the user asks about launching a product, Product Hunt launch, go-to-market strategy, launch plan, beta program, pre-launch marketing, launch day execution, or post-launch growth. Trigger phrases include "product launch", "launch plan", "Product Hunt", "Hacker News launch", "go-to-market", "GTM strategy", "launch checklist", "pre-launch", "beta launch", "launch day", "launch sequence", "how to launch".
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Product launch strategy and Go-to-market strategy. The repository describes itself as: 77 open-source marketing skills for Claude Code, Codex, and other AI coding agents. SEO, content, email, ads, analytics, and growth. The licence is MIT.
When your agent uses it
- The user asks about launching a product
- Product Hunt launch
- Go-to-market strategy
- Pre-launch marketing
Example prompts
- “product launch”
- “launch plan”
- “Product Hunt”
- “/launch-strategy”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 28bf209. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Launch Strategy loads about 1.6k tokens when it runs. Until then it costs about 131 tokens; SKILL.md has 697 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from OpenClaudia/openclaudia-skills at commit 28bf209, republished under its MIT licence (© OpenClaudia). 697 words, ~1,648 tokens.
Download SKILL.mdSave it as
.claude/skills/launch-strategy/SKILL.md (or your agent's skills folder).- name
- launch-strategy
- description
- Plan and execute product launches with week-by-week timelines and channel-specific playbooks. Use when the user asks about launching a product, Product Hunt launch, go-to-market strategy, launch plan, beta program, pre-launch marketing, launch day execution, or post-launch growth. Trigger phrases include "product launch", "launch plan", "Product Hunt", "Hacker News launch", "go-to-market", "GTM strategy", "launch checklist", "pre-launch", "beta launch", "launch day", "launch sequence", "how to launch".
Product Launch Strategy
You are an expert product launch strategist. When the user asks you to plan a launch, prepare for Product Hunt, or build a go-to-market strategy, follow this framework.
Step 1: Gather Launch Context
Establish: product (new/feature/update), target audience, launch type (soft/beta/public), timeline, budget, team size, existing audience (list size, following), relevant channels, competitive timing, success metrics.
Step 2: Launch Type Selection
| Type | Timeline | Audience | Best For |
|---|---|---|---|
| Stealth/Alpha | Ongoing | 10-50 hand-picked | Validating concept |
| Closed Beta | 2-4 weeks | 50-500 invited | Refining, testimonials |
| Open Beta | 2-4 weeks | Anyone | Waitlist buzz, stress test |
| Soft Launch | 1 week | Existing audience | Low-risk iteration |
| Full Public | 1 day (4-8 week prep) | Everyone | Maximum impact, PR |
| Rolling | 4-8 weeks | Phased access | Manage load, build FOMO |
Step 3: Pre-Launch (8-4 Weeks Before)
Week 8-6: Foundation
Positioning: One-sentence value prop. Elevator pitch (30s/60s/2min). Positioning statement:
For [audience] who [need], [product] is a [category] that [benefit].
Unlike [alternative], we [differentiator].Landing Page: Clear headline, demo video, 3 benefits, email capture, social proof, FAQ. Set up analytics and email automation.
Content Prep: 3-5 blog posts for launch week, product demo video (60-90s), screenshots, social calendar, press release draft, founder story narrative.
Week 6-4: Audience Building
Waitlist Growth: Building-in-public updates, referral waitlist, content marketing, community engagement (Reddit/Discord/Slack), micro-influencer outreach (20-50 people), LinkedIn founder posts.
Waitlist Targets: Solo founder: 500-5,000+. Small team: 1,000-10,000+. Funded: 5,000-50,000+.
Beta Setup: Select 50-200 from waitlist. Private feedback channel. Feedback template: What did you try? Success (1-5)? What was frustrating? Would you recommend? Would you pay?
Week 4-2: Momentum
Social Proof: Request testimonials ("[Result] since using [product]. Before [pain]. Now [benefit]."). Collect usage metrics. Video testimonials.
Amplification: Newsletter authors, cross-promotion with complementary founders, advisors/investors briefed, "launch support" doc for network.
Technical: Load test for 10x traffic. Monitoring/alerting. Scaling plan. War room channel. On-call assignments.
Step 4: Launch Week
Day Before
- Final QA of product, page, links
- Queue social posts, pre-schedule email
- Brief team on roles
- Verify tracking pixels
- Test payment flows
Launch Day
Hour 0: Publish everywhere. Send waitlist email. Post all social. Submit Product Hunt. Hours 1-4: Respond to every mention/comment. Share traction updates. Fix bugs immediately. DM supporters. Hours 4-12: Publish "why we built this" post. Share customer reactions. Behind-the-scenes content. Hours 12-24: Day 1 recap email. Wrap-up social post. Respond to all tickets. Plan Day 2.
Product Hunt Playbook
Prep: Build maker profile 2+ weeks early. Prepare: tagline (60 chars), description (260 chars), 5+ gallery images, maker comment (200+ words), 60-90s video.
Launch Day: Launch 12:01 AM PT. Post maker comment immediately. Share link by 6 AM PT. Respond to every comment within 30 min. Never ask for "upvotes" -- ask for "feedback." Target top 5.
Post-PH: Thank community. Add PH badge. Reach out to commenters. Write retrospective.
Show full SKILL.md (257 more words)Show less
Hacker News Playbook
Title: "Show HN: [Name] - [What it does in plain English]" Comment: Technical architecture, why built, what's unique, honest limitations. Rules: Post 8-10 AM ET Tue-Thu. Be humble and transparent. No superlatives. Respond to criticism gracefully.
Social Media Blitz
Twitter Thread: (1) Hook + announcement + link, (2) Problem, (3) Solution + screenshot, (4) Proof/metrics, (5) Story/motivation, (6) CTA + link. LinkedIn: Personal story, hook opening, lessons learned, CTA, tag supporters. Reddit: Follow sub rules, lead with value/story, engage extensively.
Step 5: Post-Launch (Weeks 2-8)
Week 2: Recap email, first case study, retargeting ads, media outreach, NPS collection. Week 3-4: SEO content, comparison pages, onboarding optimization, outbound from leads. Week 5-6: Funnel analysis, landing page A/B tests, double down on best channels, referral program. Week 7-8: Scale paid ads, content partnerships, integrations, plan v2 launch.
Step 6: Metrics
| Phase | Metric | Target |
|---|---|---|
| Pre-Launch | Waitlist sign-ups | [goal] |
| Pre-Launch | Waitlist CR | 20-40% |
| Pre-Launch | Beta activation | 60%+ |
| Launch Day | Sign-ups | [goal] |
| Launch Day | PH rank | Top 5 |
| Post-Launch | Activation rate | 40%+ |
| Post-Launch | D1/D7/D30 retention | 60%/30%/15%+ |
| Post-Launch | Trial-to-paid | 10-25% |
| Post-Launch | NPS | 40+ |
Track channel attribution by quality (activation rate, retention, LTV), not just volume.
Step 7: Budget Allocation
| Category | % | Activities |
|---|---|---|
| Content | 20-25% | Video, blog, graphics |
| Paid Acquisition | 30-40% | Social ads, search ads, sponsorships |
| PR/Outreach | 10-15% | Media, influencers |
| Tools | 5-10% | Email, analytics, hosting |
| Reserve | 10-15% | Double down on what works |
Zero-Budget: Personal network, Product Hunt, Show HN, Reddit, Twitter thread, cold email journalists, cross-promotion, free email tools.
Output Format
LAUNCH PLAN: [Product]
=======================
TYPE: [type] | DATE: [date] | TARGET: [metric]
TIMELINE: Week-by-week activities
CHANNEL PLAYBOOKS: Detailed per-channel plans
CONTENT CALENDAR: Pieces with publish dates
LAUNCH DAY CHECKLIST: Hour-by-hour execution
BUDGET: Category allocation
METRICS: KPIs with targets
RISK MITIGATION: Contingency plansTailor to the user's resources. A solo founder needs a different plan than a funded startup.
© OpenClaudia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/launch-strategy of OpenClaudia/openclaudia-skills.
Open the folder on GitHubat commit 28bf209
Compare with similar skills
Launch Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Launch Strategy this skillOpenClaudia/openclaudia-skills | 711 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Launch Strategyfreekmurze/dotfiles | 1k | 22 repos | ~3.1k | Automated safety check: Pass | None | |
| Marketing StrategistCoWork-OS/CoWork-OS | 473 | — | ~893 | Automated safety check: Pass | MIT | |
| Go To Marketemotixco/claude-skills-founder | 517 | — | ~884 | Automated safety check: Pass | MIT | |
| Multi-Platform Launch Plannertech-leads-club/agent-skills | 7k | — | ~3.9k | Automated safety check: Pass | Custom licence | |
| Gingiris Go GlobalGingiris-1031/Competitor-analysis-tool | 110 | — | ~868 | Automated safety check: Pass | None |
Similar skills
Marketing Strategist
CoWork-OS/CoWork-OS
Comprehensive marketing strategy across 25 disciplines — positioning, copywriting frameworks, buyer psychology, SEO, CRO, paid ads, funnel architecture, content strategy, growth loops, analytics…
Go To Market
emotixco/claude-skills-founder
Plan a product launch from pre-launch audience building to a 90-day growth plan, with named communities, platform-specific launch tactics, channel rankings, and a budget for $0-$500 a month.
Multi-Platform Launch Planner
tech-leads-club/agent-skills
Plans a product launch across Product Hunt, Hacker News, BetaList and other directories, with timing from the pre-launch waitlist through post-launch follow-up.
Gingiris Go Global
Gingiris-1031/Competitor-analysis-tool
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization.
Launch
menkesu/awesome-pm-skills
Builds a launch plan, launch story and press/distribution plan, then drafts the pitch emails and announcement copy.
More from OpenClaudia/openclaudia-skills
All 74 skills in this repoCompetitor Traffic Report
OpenClaudia/openclaudia-skills
Build an interactive competitive-traffic report for any company and its rivals — monthly visits (SimilarWeb), organic search traffic and Domain Rating (Ahrefs) — as one self-contained HTML page with…
Geo Difficulty
OpenClaudia/openclaudia-skills
Score how hard a keyword is to rank for in the AI-search era — page-level URL Rating of real competitors (not just domain DR), Ahrefs keyword difficulty, and whether a given site already ranks or is…
Gsc Portfolio Audit
OpenClaudia/openclaudia-skills
Audit EVERY Google Search Console property at once — rank all sites by clicks and impressions with period-over-period deltas, then diff keywords per site to surface what is newly ranking, rising…
Similarweb Traffic
OpenClaudia/openclaudia-skills
Fetch website traffic estimates (monthly visits, traffic sources, top countries, keywords, engagement, ranks) for any domain from SimilarWeb.
Ahrefs Python
OpenClaudia/openclaudia-skills
Manages Ahrefs API usage in Python using ahrefs-python library.
Ab Test Setup
OpenClaudia/openclaudia-skills
Design, plan, and analyze A/B tests with statistical rigor. An agent skill from OpenClaudia/openclaudia-skills.
Related
Categories
Questions about Launch Strategy
What does Launch Strategy do?
Plan and execute product launches with week-by-week timelines and channel-specific playbooks. Launch Strategy is an agent skill from OpenClaudia/openclaudia-skills. Plan and execute product launches with week-by-week timelines and channel-specific playbooks.
When should I use Launch Strategy?
Launch Strategy fits situations like: the user asks about launching a product; product Hunt launch; go-to-market strategy; pre-launch marketing.
How do I install Launch Strategy in Claude Code?
Run `npx skills add OpenClaudia/openclaudia-skills --skill launch-strategy -a claude-code`. Or copy the skill folder (skills/launch-strategy in OpenClaudia/openclaudia-skills) into .claude/skills/launch-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Launch Strategy in Codex?
Run `npx skills add OpenClaudia/openclaudia-skills --skill launch-strategy -a codex`. Or copy the skill folder (skills/launch-strategy in OpenClaudia/openclaudia-skills) into .agents/skills/launch-strategy in your project. Codex loads it when a task matches its description.
Can I use Launch Strategy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OpenClaudia/openclaudia-skills --skill launch-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/launch-strategy, .gemini/skills/launch-strategy, .github/skills/launch-strategy and .opencode/skills/launch-strategy in your project.
What does Launch Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Launch Strategy is instructions for the agent only.
Does Launch Strategy access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Launch Strategy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Launch Strategy use?
Launch Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Launch Strategy use?
About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Launch Strategy?
Skills that share tags, products or a category with Launch Strategy: Launch Strategy (freekmurze/dotfiles, 1k stars), Marketing Strategist (CoWork-OS/CoWork-OS, 473 stars), Go To Market (emotixco/claude-skills-founder, 517 stars) and Multi-Platform Launch Planner (tech-leads-club/agent-skills, 7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Launch Strategy?
OpenClaudia (a GitHub organization) maintains it in OpenClaudia/openclaudia-skills, which has 711 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on September 18, 2026.
Source: OpenClaudia/openclaudia-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.