launch-strategy
When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas.
64
55%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/launch-strategy/SKILL.mdQuality
Discovery
62%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at trigger terms and distinctiveness — it provides extensive natural language keywords and even cross-references a related skill to reduce overlap. However, it critically fails to describe what the skill actually does; there are no concrete actions or outputs mentioned, making it impossible for Claude to know what capabilities this skill provides beyond the general domain of product launches.
Suggestions
Add specific capability statements at the beginning, e.g., 'Generates product launch checklists, GTM plans, announcement drafts, and release timelines.'
Include concrete output types the skill produces, such as 'Creates launch strategies, Product Hunt submission plans, beta rollout schedules, and waitlist email sequences.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks any concrete actions or capabilities. It never states what the skill actually does — there are no verbs describing specific outputs like 'creates launch checklists,' 'generates GTM plans,' or 'drafts announcement copy.' It only describes when to use it. | 1 / 3 |
Completeness | The 'when' is thoroughly covered with explicit trigger guidance, but the 'what' is almost entirely missing — the description never explains what the skill actually produces or does. It only tells Claude when to select it, not what capabilities it provides. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'GTM plan,' 'we're about to ship,' and more. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around product launches and release strategies, and even explicitly differentiates from a related skill ('for ongoing marketing after launch, see marketing-ideas'), reducing conflict risk significantly. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
47%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive but overly verbose launch strategy guide that reads more like a marketing textbook chapter than a concise skill for Claude. The workflow structure and checklists are strong, but the content is bloated with general marketing knowledge, motivational framing, and case studies that don't add actionable value. It would benefit significantly from being trimmed to essential decision frameworks and concrete templates while moving detailed explanations to linked reference files.
Suggestions
Cut the content by 50-60%: remove case studies (Superhuman, Notion, TRMNL, SavvyCal, Reform), motivational framing ('Core Philosophy' section), and explanations of basic marketing concepts Claude already understands (what owned/rented/borrowed channels are).
Add concrete, copy-paste ready templates: launch email template, Product Hunt listing copy template, social media announcement templates, and a landing page wireframe structure.
Move the ORB Framework details, Product Hunt deep-dive, and post-launch marketing sections into separate linked reference files, keeping only a brief summary and link in the main skill.
Replace vague action items like 'Announce the product exists' with specific examples: exact email subject lines, tweet formats, or blog post outlines.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, explaining general marketing concepts Claude already knows (what owned/rented/borrowed channels are, why email lists matter, basic marketing philosophy). Extensive case studies and motivational framing ('The best companies don't just launch once') add token cost without actionable value. | 1 / 3 |
Actionability | The skill provides structured checklists and phase-by-phase actions, which are somewhat concrete. However, there's no executable code, no specific templates or copy examples, and guidance remains at the strategic/conceptual level rather than providing copy-paste ready artifacts like email templates, social post templates, or landing page copy frameworks. | 2 / 3 |
Workflow Clarity | The five-phase launch approach is clearly sequenced with explicit goals per phase, and the launch checklist provides clear pre/during/post validation checkpoints. The phases build logically on each other with clear progression criteria. | 3 / 3 |
Progressive Disclosure | The skill references related skills at the bottom and checks for a context file, which is good. However, the massive amount of inline content (ORB framework, Product Hunt strategy, case studies, post-launch marketing, ongoing strategy) should be split into separate reference files rather than being a monolithic document. The content that's inline would benefit from being in linked files. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- coreyhaines31/marketingskills
- Commit
1bcff9f
- Reviewed
Table of Contents
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.