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.
86
Quality
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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. The main weakness is that the capabilities section lists categories (phased launches, channel strategy) rather than specific concrete actions Claude would perform. The description successfully carves out a distinct niche for product launch planning.
Suggestions
Replace category terms with specific actions: instead of 'phased launches, channel strategy,' use verbs like 'create launch timelines, draft announcement copy, develop channel distribution plans, build waitlist strategies.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (product launches) and mentions some actions like 'phased launches, channel strategy, and ongoing launch momentum,' but these are more categories than concrete actions. Missing specific verbs like 'create launch timeline,' 'draft announcements,' or 'build waitlist strategy.' | 2 / 3 |
Completeness | Clearly answers both what (plan product launches, feature announcements, release strategies, phased launches, channel strategy) and when (explicit 'Use when' equivalent with 'When the user wants to...' and 'Also use when the user mentions...' with specific trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update.' These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on product launches and release strategies. The specific triggers like 'Product Hunt,' 'go-to-market,' 'beta launch,' and 'waitlist' create a distinct domain unlikely to conflict with general marketing or project planning skills. | 3 / 3 |
Total | 11 / 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, highly actionable launch strategy skill with excellent workflow clarity through its five-phase approach and detailed checklists. The main weaknesses are verbosity (explaining marketing concepts Claude already knows) and lack of progressive disclosure (all content inline rather than split into reference files). The case studies and concrete examples are strong assets.
Suggestions
Trim explanatory content about basic marketing concepts (e.g., what owned/rented/borrowed channels are) and focus on the specific tactics and examples
Extract detailed sections like Product Hunt strategy and ORB framework into separate reference files (e.g., PRODUCT-HUNT.md, ORB-FRAMEWORK.md) with brief summaries in the main skill
Condense the channel examples - the Superhuman, Notion, and TRMNL case studies are valuable but could be more concise
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains valuable information but is verbose in places, explaining concepts Claude likely knows (e.g., what owned/rented/borrowed channels are, basic marketing concepts). Some sections could be tightened significantly while preserving actionability. | 2 / 3 |
Actionability | Provides highly concrete, actionable guidance with specific tactics, checklists, case studies with named companies, and clear step-by-step processes. The launch checklist and phase-by-phase approach give copy-paste ready frameworks. | 3 / 3 |
Workflow Clarity | The five-phase launch approach provides clear sequencing with explicit goals for each phase. The checklist format with pre-launch, launch day, and post-launch sections creates natural validation checkpoints. Progression between phases is well-defined. | 3 / 3 |
Progressive Disclosure | While the skill references related skills at the end, the main content is a monolithic document (~400 lines) that could benefit from splitting detailed sections (Product Hunt strategy, ORB framework details) into separate reference files. The structure is good but content is all inline. | 2 / 3 |
Total | 10 / 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
355d067
- 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.