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 defining when to use the skill with rich trigger terms and clear differentiation from related skills, but critically fails to describe what the skill actually does. A user or Claude selecting this skill would know when to pick it but not what capabilities or outputs to expect from it.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Creates launch checklists, drafts announcement copy, builds go-to-market timelines, and outlines release strategies.'
Restructure to lead with a 'what it does' statement before the 'Use when...' clause, following the pattern: capabilities first, then triggers.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks any concrete actions or capabilities. It never states what the skill actually does — no verbs like 'creates,' 'generates,' 'plans,' or 'outlines.' It only describes when to use it, not what it does. | 1 / 3 |
Completeness | The 'when' is thoroughly covered with explicit triggers and even a cross-reference to a related skill. However, the 'what does this do' is essentially missing — there are no concrete actions or outputs described, only the triggering context. | 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 the marketing-ideas skill for post-launch activities. The trigger terms are specific to the launch domain. | 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 skill reads more like a comprehensive marketing guide or blog post than a concise, actionable skill for Claude. Its strengths are in workflow structure (the five-phase approach and checklists are well-organized) and breadth of coverage. However, it's severely over-verbose, explains concepts Claude already understands, and lacks the concrete executable specificity (templates, actual copy examples, specific tools/commands) that would make it truly actionable.
Suggestions
Cut the content by 50-60%: remove the Core Philosophy section, trim ORB framework explanations to just the tactical guidance, and eliminate case studies or move them to a separate EXAMPLES.md file.
Add concrete, copy-paste-ready templates: include actual email announcement templates, social post templates, Product Hunt tagline formulas, and landing page copy structures instead of abstract guidance.
Split into multiple files: keep SKILL.md as a concise overview with the five-phase framework and checklist, then move Product Hunt strategy, ORB framework details, and post-launch tactics into separate referenced files.
Remove explanations of basic concepts Claude already knows (what owned vs rented channels are, why email lists compound, what Product Hunt is) and focus only on specific, non-obvious tactical guidance.
| 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 definitions). Case studies and philosophy sections add significant token overhead without providing actionable specificity that Claude couldn't generate on its own. | 1 / 3 |
Actionability | The skill provides structured checklists and phase-by-phase actions which are somewhat concrete, but lacks executable specifics—no code, no templates, no actual email copy examples, no specific commands. Guidance like 'create landing page with clear value proposition' and 'optimize your listing' is directional but not copy-paste ready. | 2 / 3 |
Workflow Clarity | The five-phase launch approach is clearly sequenced with explicit goals per phase, and the pre-launch/launch-day/post-launch checklists provide clear validation checkpoints. The progression from internal → alpha → beta → early access → full launch is well-structured with distinct actions and goals at each stage. | 3 / 3 |
Progressive Disclosure | The skill references related skills at the bottom and links to one external tool, showing some progressive disclosure. However, the massive amount of inline content (ORB framework, Product Hunt strategy, post-launch marketing, ongoing strategy) could be split into separate reference files. The skill is essentially a monolithic document that tries to cover everything in one file. | 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
9125d82
- 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.