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.
npx skills add w95/awesome-claude-corporate-skills --skill product-launch-playbookgit clone --depth 1 https://github.com/w95/awesome-claude-corporate-skillsWrote 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.
[](https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/product-launch-playbook)<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/product-launch-playbook"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/product-launch-playbook/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.
<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/product-launch-playbook"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/product-launch-playbook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00039 | $0.03950 |
| Opus 5 | $0.00019 | $0.01975 |
| Sonnet 5 | $0.00008 | $0.00790 |
| Haiku 4.5 | $0.00004 | $0.00395 |
Grade A, and why
product-launch-playbook 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.
How it starts
The opening of the file, as written. The whole thing — 598 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Launch Playbook
Overview
The Product Launch Playbook skill guides product managers through all phases of launching features or products, from pre-launch planning through post-launch analysis. It ensures coordinated execution across engineering, marketing, sales, and support teams.
When to Use This Skill
- Planning major feature launches
- Launching new product or product line
- Planning beta testing programs
- Executing go-to-market strategies
- Communicating with stakeholders
- Managing launch day operations
- Analyzing post-launch performance
- Planning customer success initiatives
Launch Framework Overview
Launch Timeline (8-12 weeks):
- Pre-Launch Phase (4-5 weeks) - Strategy, assets, readiness
- Beta Phase (2-3 weeks) - Customer validation, feedback
- Launch Phase (1-2 weeks) - Coordinated release
- Post-Launch Phase (4+ weeks) - Support, iteration, analysis
Pre-Launch Planning (4-5 weeks before)
Launch Steering Committee Formation
Core team members:
- Product Manager (Owner)
- Engineering Lead
- Design Lead
- Marketing Lead
- Sales Lead
- Support/Customer Success Lead
- Analytics Owner
Responsibilities:
- Weekly launch status meetings
- Escalation authority for decisions
- Budget and resource approval
- Cross-functional alignment
Go-to-Market (GTM) Strategy
Target Customer Definition:
-
Primary segment: [Specific customer profile]
- Company size, industry, use case
- How they will benefit most
- Why they should care vs. competitors
-
Secondary segment: [Broader customer profile]
Value Proposition:
- Core benefit: [One sentence, customer-focused]
- Supporting benefits: [3-4 specific advantages]
- Differentiation: [vs. competition or status quo]
Positioning Statement: "For [customer segment], [product/feature] is a [category] that [solves problem]. Unlike [alternative], our [feature] [key differentiator]."
Example: "For remote engineering teams, Real-time Project Sync is a collaboration system that eliminates status update meetings. Unlike email and Slack, our feature creates a persistent, queryable project state that updates in real-time."
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.
- 9d ago First seen · 598 lines · 39 tokens per session scan A 548643e6d7b0
product-launch-playbook is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 3,950 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
design-por-referencia
Use when a landing page, marketing site, or hero section looks generic/AI-made ("cara de vibe coding") and needs a $10k-agency-level redesign, or when building a new landing from scratch. Triggers - "o site ficou com cara de IA", "quero uma landing premium", "redesenha a landing", "faz o site baseado em [site de…
lighthouse-95
Use when a website must score 95+ in every Lighthouse category (Performance, Accessibility, Best Practices, SEO), when scores are stuck below target, or when diagnosing poor FCP, LCP, TBT, or CLS on a deployed site.
seo-validate
SEO validator: meta/OG, Schema.org, hreflang, Core Web Vitals, crawlability. Triggers: SEO, meta tags, Schema.org, hreflang, LCP, INP, CLS, Core Web Vitals, sitemap, crawlability.
debug
Systematic debugging via logs, health checks, hypothesis-driven investigation. Triggers: debug, error, trace root cause, fix bug, reproduce symptom, investigation.
pr
Creates GitHub PR after pre-flight checks (lint/typecheck/tests), structured summary from commits. Triggers: pr, pull request, create PR, ready to merge.
research-mastery
Hierarchical retrieval: KB → MCP/Context7 → web. Triggers: research, fact-check, verify, synthesize, cross-reference, multi-source, cite sources.