launch-strategy

Plan and execute product launches using a tiered framework — from major new products down to small improvements. Use this skill whenever someone asks to plan a launch, create a launch checklist, define launch tiers, write launch messaging, or coordinate a product release. Also trigger when someone says "we're launching X" or "how should we announce this feature" or "what's our launch plan" — even if they don't use the word "strategy." Covers messaging, naming, launch assets, timelines, and post-launch retros. This is the master launch skill; it references the companion skills (launch-tweet, launch-landing-page, launch-distribution, launch-email, launch-video, launch-metrics) for specific execution.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable strategy skill with a clear sequenced workflow and built-in validation/feedback loops. Its weaknesses are motivational padding that inflates token cost and a monolithic layout that keeps large reference material inline rather than splitting it into bundle files.

Suggestions

Trim the motivational narrative — collapse 'The everything is a launch philosophy' section and the 'mediocre video vs beautiful video' aside, since the opening 'launch engine, not a one-off event' line already conveys the insight.

Move the large per-tier checklist matrix and the three tier timelines into a reference file (e.g. references/launch-checklist.md) and link to it from the body, turning SKILL.md into a lean overview with one-level-deep references.

Convert the messaging-brief fields and retro questions into compact checklist form rather than prose so the guidance stays concrete while reducing token count.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and concrete, but padded with motivational narrative Claude doesn't need — 'A mediocre video with great messaging outperforms a beautiful video with confused positioning' and the entire 'The everything is a launch philosophy' section restate the opening insight. Not a score 3 because several tokens do not earn their place; not a 1 because the bulk is actionable rather than concept-explaining.	2 / 3
Actionability	Highly concrete for an instruction-only skill: tier definitions with prep times, a five-field messaging brief, a 20+ row checklist matrix mapping actions per tier, and week-by-week timelines — specific and copy-ready per the code-vs-instruction scoring note.	3 / 3
Workflow Clarity	Clear sequence (tier → messaging → checklist → timeline → retro) with an explicit validation checkpoint ('Read your primary value prop out loud. If it could describe a competitor's product just as well, it's too generic') and a feedback loop where the retro updates the master checklist.	3 / 3
Progressive Disclosure	Well-organized into clear sections, but it is a monolithic ~150-line document with the large checklist table and full timelines inline and no one-level-deep bundle references (no references/scripts/assets exist). Matches the anchor where content that could be separate stays inline; not a 1 because section structure is clean, not a 3 because nothing is split out.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states capabilities, provides explicit and natural trigger phrasing, and distinguishes the master strategy skill from its execution companions. Verbosity is the only minor weakness — it is longer than necessary for the information conveyed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Plan and execute product launches', 'define launch tiers', 'write launch messaging', 'coordinate a product release' — and enumerates coverage ('messaging, naming, launch assets, timelines, and post-launch retros').	3 / 3
Completeness	Explicitly answers both what ('Plan and execute product launches using a tiered framework') and when ('Use this skill whenever someone asks to plan a launch... Also trigger when someone says...'), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Good coverage of natural phrases users would say — 'plan a launch', 'create a launch checklist', 'we're launching X', 'how should we announce this feature', 'what's our launch plan' — matching the anchor for natural-term coverage.	3 / 3
Distinctiveness Conflict Risk	Clearly positions itself as 'the master launch skill' for strategy/planning while delegating execution to named companion skills, giving it a distinct niche with unlikely wrong-skill triggering.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: amplitude/builder-skills
Path: launch-skills/skills/launch-strategy/SKILL.md
Commit: 51838c2

Reviewed: 21 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.