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,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.
74
68%
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 ./config/claude/skills/launch-strategy/SKILL.mdQuality
Discovery
89%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 is a well-structured description with excellent trigger term coverage and clear 'when to use' guidance. Its main weakness is that the 'what it does' portion could be more specific about concrete deliverables and actions rather than listing broad domain areas like 'channel strategy' and 'launch momentum.' The description uses appropriate third-person voice throughout.
Suggestions
Replace vague capability phrases like 'covers phased launches, channel strategy, and ongoing launch momentum' with specific concrete actions such as 'creates launch timelines, drafts announcement copy, designs channel distribution plans, builds post-launch engagement strategies.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions some actions like 'phased launches, channel strategy, and ongoing launch momentum' but these are more domain areas than concrete specific actions. It doesn't list specific deliverables like 'create launch timelines, draft announcement copy, build channel distribution plans.' | 2 / 3 |
Completeness | Clearly answers both 'what' (plan a product launch, feature announcement, release strategy, phased launches, channel strategy, launch momentum) and 'when' (explicit 'Use when' equivalent with detailed trigger terms and scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update.' These are terms users would naturally use when seeking launch planning help. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around product launches and release strategies with highly specific trigger terms like 'Product Hunt,' 'go-to-market,' 'beta launch,' and 'waitlist' that are unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 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 marketing strategy guide that reads more like a blog post or playbook than a concise skill instruction. Its strength is the well-structured five-phase workflow and actionable checklists, but it's severely undermined by verbosity—explaining general marketing concepts Claude already understands, including lengthy case studies, and providing philosophical framing that doesn't add operational value. The skill would benefit greatly from aggressive trimming and splitting detailed content into reference files.
Suggestions
Cut the content by 50-60%: remove case studies (Superhuman, Notion, TRMNL, SavvyCal, Reform), the 'Core Philosophy' section, and explanations of what owned/rented/borrowed channels are—Claude knows these concepts. Focus on the specific tactical guidance.
Move the ORB Framework details, Product Hunt strategy, and post-launch marketing sections into separate reference files, keeping only a brief summary and links in the main SKILL.md.
Add concrete templates or fill-in-the-blank examples (e.g., a Product Hunt tagline template, a launch email outline, a waitlist landing page copy structure) to increase actionability beyond directional advice.
Tighten the task-specific questions section into a decision tree format: 'If launching new product → follow Phase 1-5; if feature update → use the prioritization matrix to determine scope' rather than open-ended questions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines, explaining general marketing concepts Claude already knows (what owned/rented/borrowed channels are, why email lists matter, what Product Hunt is). Extensive case studies and philosophy sections add bulk without adding actionable specificity. Much of this reads like a marketing blog post rather than a concise skill instruction. | 1 / 3 |
Actionability | The skill provides structured frameworks (ORB, five phases) and checklists with concrete actions, but lacks any executable code, commands, or specific templates. Guidance is directional rather than copy-paste ready—e.g., 'Create landing page with early access signup form' without showing what that looks like or providing a template. | 2 / 3 |
Workflow Clarity | The five-phase launch approach is clearly sequenced with explicit goals for each phase, and the launch checklist provides pre/during/post validation checkpoints. The progression from internal → alpha → beta → early access → full launch is well-defined with clear actions and decision points at each stage. | 3 / 3 |
Progressive Disclosure | The skill references related skills at the bottom (email-sequence, page-cro, etc.) which is good, but the main body is a monolithic wall of content that could benefit from splitting detailed sections (Product Hunt strategy, ORB framework details, case studies) into separate reference files. The checklist context file pattern is mentioned but most content is inline. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
2c6f6e8
- 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.