multi-platform-launch
When the user wants to launch a product across multiple platforms, plan a Product Hunt launch, build a waitlist, or execute a multi-channel launch strategy. Also use when the user mentions 'product launch,' 'Product Hunt,' 'launch strategy,' 'waitlist,' 'beta launch,' 'BetaList,' 'Hacker News,' 'launch day,' 'AppSumo,' 'multi-channel launch.' This skill covers multi-platform launch execution from pre-launch through post-launch optimization. Do NOT use for technical implementation, code review, or software architecture.
90
87%
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 strong skill description with excellent trigger term coverage and clear completeness, explicitly addressing both what the skill does and when to use it. The negative boundary clause is a nice addition that reduces conflict risk. The main weakness is that the specific capabilities could be more granular—listing concrete actions like 'create launch timelines' or 'draft launch announcements' rather than high-level activities.
Suggestions
Add more granular, concrete actions such as 'create launch timelines,' 'draft launch copy,' 'prepare press kits,' or 'design waitlist landing page content' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (product launches) and mentions some actions like 'plan a Product Hunt launch,' 'build a waitlist,' and 'execute a multi-channel launch strategy,' but these are more high-level activities than concrete specific actions. It lacks granular actions like 'create launch timelines,' 'draft launch copy,' or 'prepare press kits.' | 2 / 3 |
Completeness | Clearly answers both 'what' (multi-platform launch execution from pre-launch through post-launch optimization) and 'when' (explicit 'Use when' triggers and a list of trigger terms). Also includes a helpful negative boundary ('Do NOT use for technical implementation, code review, or software architecture'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'product launch,' 'Product Hunt,' 'launch strategy,' 'waitlist,' 'beta launch,' 'BetaList,' 'Hacker News,' 'launch day,' 'AppSumo,' 'multi-channel launch.' These are specific, natural terms that users would actually use when seeking help with product launches. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around product launch strategy and execution. The explicit exclusion of technical implementation, code review, and software architecture further reduces conflict risk with developer-oriented skills. The specific platform names (Product Hunt, BetaList, AppSumo, Hacker News) create a very distinct trigger profile. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured launch strategy skill with excellent actionability and workflow clarity. The week-by-week framework, platform-specific deep dives with benchmarks, and troubleshooting section provide genuinely useful, specific guidance. The main weakness is that the extensive platform landscape tables could be moved to a reference file to improve conciseness, as the skill is quite long for inline consumption.
Suggestions
Move the Platform Landscape tables (Discovery, Developer, Indie, AI/Tech, Social, Content, Paid) to a reference file like references/platform-landscape.md and keep only the top 3-4 most critical platforms inline to reduce token usage by ~40%.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~400+ lines) with extensive tables covering platform landscapes that could be in a reference file. The platform tables, while useful, include details like monthly users and domain authority that add bulk. However, most content is actionable rather than explanatory, and it avoids explaining basic concepts to Claude. | 2 / 3 |
Actionability | The skill provides highly specific, concrete guidance: exact times for posting (12:01 AM PT, 8-10 AM PT), specific title formulas with good/bad examples, numeric benchmarks (150-300 upvotes = good), referral tier structures with exact numbers, tool recommendations by name, and role assignments for launch day. This is copy-paste-ready strategic execution guidance. | 3 / 3 |
Workflow Clarity | The Launch Sequence Framework provides a clear week-by-week timeline from Week -4 through Week +4 with explicit sequencing. Launch day has hour-by-hour instructions. The troubleshooting section provides feedback loops for common failure modes (low traction → fix → retry). The 'Before Starting' section acts as a validation checkpoint before producing any plan. | 3 / 3 |
Progressive Disclosure | The skill maintains a clear overview structure with well-signaled references to external files (references/directories-timing-mistakes.md, references/quick-reference.md) for detailed content. Related skills are listed with clear descriptions. The inline content covers the most critical platforms (PH, HN, waitlists) while deferring secondary topics to reference files. | 3 / 3 |
Total | 11 / 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
- tech-leads-club/agent-skills
- Commit
81e7e0d
- 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.