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.
71
61%
Does it follow best practices?
Impact
81%
1.39xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/launch-strategy/SKILL.mdQuality
Discovery
44%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 but fundamentally fails at its core purpose by never explaining what the skill actually does. It reads as a comprehensive list of when to invoke the skill, but provides zero information about the capabilities, outputs, or actions the skill performs.
Suggestions
Add concrete actions at the beginning describing what the skill does, e.g., 'Creates launch checklists, go-to-market strategies, and announcement plans for product releases.'
Restructure to lead with capabilities before the 'Use when...' clause - the current format is inverted from best practices.
Specify deliverables or outputs the skill produces (e.g., 'Generates launch timelines, messaging frameworks, channel strategies')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks any concrete actions - it never states what the skill actually does. It only describes when to use it, not what capabilities it provides (e.g., 'plan a product launch' is a trigger, not an action the skill performs). | 1 / 3 |
Completeness | While the 'when' is thoroughly covered with explicit triggers, the 'what' is completely missing. The description never explains what the skill actually does or produces - it only describes triggering conditions. | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'launch,' 'Product Hunt,' 'feature release,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'GTM plan,' and conversational phrases like 'how do I launch this' and 'we're about to ship.' | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused on product launches with distinct triggers. The explicit boundary with marketing-ideas skill ('For ongoing marketing after launch, see marketing-ideas') further reduces conflict risk. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
77%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 and highly actionable launch strategy skill with excellent workflow clarity and real-world examples. Its main weakness is verbosity—the philosophical framing and some explanatory content could be trimmed significantly. The content would also benefit from splitting into a concise overview with detailed reference files for specific topics like Product Hunt strategy.
Suggestions
Trim the 'Core Philosophy' section to 2-3 sentences—Claude understands why launches matter
Move the detailed ORB Framework examples and Product Hunt strategy into separate reference files (e.g., ORB-FRAMEWORK.md, PRODUCT-HUNT.md) and link from the main skill
Reduce explanatory text in favor of more bullet points and direct instructions—the case studies are valuable but the surrounding context is verbose
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains valuable information but is verbose in places, explaining concepts like the ORB framework philosophy and general marketing principles that Claude likely already understands. Some sections could be tightened significantly while preserving actionability. | 2 / 3 |
Actionability | Provides highly concrete, actionable guidance with specific tactics, real company examples (Superhuman, Notion, TRMNL, SavvyCal, Reform), detailed checklists, and clear step-by-step processes for each launch phase. The guidance is specific enough to execute immediately. | 3 / 3 |
Workflow Clarity | The five-phase launch approach provides clear sequencing with explicit goals for each phase. The comprehensive pre-launch, launch day, and post-launch checklists serve as validation checkpoints. The progression from internal to full launch is well-structured with clear decision points. | 3 / 3 |
Progressive Disclosure | While the skill has good internal structure with clear sections and headers, it's quite long (300+ lines) and could benefit from splitting detailed content (like Product Hunt strategy or the ORB framework) into separate reference files. The related skills section at the end is helpful but the main content is monolithic. | 2 / 3 |
Total | 10 / 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
9d4d29a
- 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.