launch-strategy

launch-strategy is a skill for Claude Code from mysticaltech/marketingskills. It costs 77 tokens per session (2,627 once invoked), scanned A, a copy of launch, MIT.

A guide for planning how to release a product, feature, or update to users. It covers staged releases, launch channels, early access, feedback, and building ongoing interest.

In plain words
What is it for?
Use it to plan beta launches, waitlists, feature announcements, Product Hunt launches, and broader go-to-market campaigns.
Why use it?
It helps organize the work around a launch so that reaching users, collecting feedback, and communicating the release are handled together.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the marketing-skills plugin — 25 skills shipped together

Good fit Use it to plan beta launches, waitlists, feature announcements, Product Hunt launches, and broader go-to-market campaigns.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mysticaltech/marketingskills/launch-strategy
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add mysticaltech/marketingskills --skill launch-strategy
Clone the repo
git clone --depth 1 https://github.com/mysticaltech/marketingskills

Made for: Claude Code.

Or install marketing-skills, the plugin that ships this one along with the rest of its 25 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for launch-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/mysticaltech/marketingskills/launch-strategy/github.svg)](https://agentmods.dev/skills/mysticaltech/marketingskills/launch-strategy)
Your own site
<a href="https://agentmods.dev/skills/mysticaltech/marketingskills/launch-strategy"><img src="https://agentmods.dev/badge/skills/mysticaltech/marketingskills/launch-strategy/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for launch-strategy

Your own site · 80×15
<a href="https://agentmods.dev/skills/mysticaltech/marketingskills/launch-strategy"><img src="https://agentmods.dev/badge/skills/mysticaltech/marketingskills/launch-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,627 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.02627
Opus 5 $0.00039 $0.01314
Sonnet 5 $0.00015 $0.00525
Haiku 4.5 $0.00008 $0.00263

Measured 9d ago against content hash a6bd96df9866, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

launch-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

91% identical to launch — 43 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/launch-strategy/SKILL.md · 351 lines

How it starts

The opening of the file, as written. The whole thing — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Launch Strategy

You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.

Before Starting

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.


Core Philosophy

The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.

A strong launch isn't about a single moment. It's about:

  • Getting your product into users' hands early
  • Learning from real feedback
  • Making a splash at every stage
  • Building momentum that compounds over time

The ORB Framework

Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.

Owned Channels

You own the channel (though not the audience). Direct access without algorithms or platform rules.

Examples:

  • Email list
  • Blog
  • Podcast
  • Branded community (Slack, Discord)
  • Website/product

Why they matter:

  • Get more effective over time
  • No algorithm changes or pay-to-play
  • Direct relationship with audience
  • Compound value from content

Start with 1-2 based on audience:

  • Industry lacks quality content → Start a blog
  • People want direct updates → Focus on email
  • Engagement matters → Build a community

Example - Superhuman: Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement.

Rented Channels

Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.

Read the full file on GitHub · 351 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 351 lines · 77 tokens per session scan A a6bd96df9866

Subscribe to this mod's changes

launch-strategy is a skill published in the GitHub repository mysticaltech/marketingskills (349 stars, last pushed 7mo ago), licensed MIT. It adds 77 tokens to every session and 2,627 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to launch, differing in 43 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens