launch-strategy
When the user needs to plan or execute a product launch — including pre-launch content sequences, launch funnels, JV/affiliate launches, cart open/close strategy, or evergreen launch funnels.
73
67%
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
72%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description effectively identifies when the skill should be used and includes strong, natural trigger terms specific to the product launch domain. Its main weakness is the lack of concrete action verbs describing what the skill actually produces — it reads more like a topic list than a capability description. Adding explicit outputs (e.g., 'creates launch timelines, drafts email sequences, designs funnel strategies') would significantly improve it.
Suggestions
Add concrete action verbs describing what the skill produces, e.g., 'Creates launch timelines, drafts pre-launch email sequences, designs cart open/close strategies, and builds evergreen funnel plans.'
Restructure to lead with 'what it does' followed by 'Use when...' to clearly separate capabilities from trigger conditions, e.g., 'Plans and builds product launch strategies including email sequences, funnel designs, and affiliate coordination. Use when the user needs to plan or execute a product launch...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (product launches) and lists several sub-areas like 'pre-launch content sequences', 'launch funnels', 'JV/affiliate launches', 'cart open/close strategy', and 'evergreen launch funnels'. However, it doesn't describe concrete actions (e.g., 'creates launch timelines', 'drafts email sequences', 'builds funnel pages') — it lists topics rather than specific capabilities. | 2 / 3 |
Completeness | The description starts with 'When the user needs to...' which addresses the 'when' aspect well, but the 'what does this do' part is weak — it says 'plan or execute' but doesn't clearly enumerate the specific outputs or actions the skill performs. The 'what' is implied through the listed topics rather than explicitly stated as capabilities. | 2 / 3 |
Trigger Term Quality | Includes strong natural trigger terms a user would actually say: 'product launch', 'launch funnels', 'JV/affiliate launches', 'cart open/close', 'evergreen launch funnels', 'pre-launch content sequences'. These cover a good range of variations a user might use when requesting help with product launches. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around product launches with specific sub-domains like JV/affiliate launches, cart open/close strategy, and evergreen funnels. This is unlikely to conflict with general marketing, content creation, or other skills due to the specificity of the launch-related terminology. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured launch strategy skill with a clear workflow and useful frameworks, but it's somewhat verbose and lacks the concrete, executable artifacts (email templates, sales page structures, swipe file examples) that would make it truly actionable. The content would benefit from being split across files with the SKILL.md serving as a leaner overview pointing to detailed reference materials.
Suggestions
Add concrete, copy-paste-ready templates for key deliverables: a sample PLC email, a sales page outline with specific sections, and a JV recruitment email template.
Move the detailed frameworks (Sideways Sales Letter, Launch Timeline Template, S-Tier/A-Tier tactics, Common Mistakes) into a separate LAUNCH-REFERENCE.md file and reference it from the main skill to improve progressive disclosure and reduce token usage.
Trim explanatory text that Claude already understands — e.g., remove the 'Results in Advance' rationale paragraph and the explanations of why each common mistake is bad; just list the mistakes and correct approaches.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary elaboration. Concepts like 'Results in Advance (Frank Kern)' explaining why generosity works, and some of the common mistakes section, explain things Claude would already understand. The content could be tightened by ~30% without losing actionable value. | 2 / 3 |
Actionability | The skill provides structured frameworks, a timeline template, and tiered tactics, which are useful. However, it lacks concrete executable artifacts — no actual email templates, no sales page copy structure, no specific swipe file examples. The examples section gives good directional guidance but remains at the summary level rather than providing copy-paste-ready outputs. | 2 / 3 |
Workflow Clarity | The 9-step workflow is clearly sequenced with logical progression from offer definition through execution and debrief. The launch timeline template provides explicit timing. The workflow includes validation checkpoints (seed launch first, build list before content, debrief after close) and the overall sequence is unambiguous. | 3 / 3 |
Progressive Disclosure | The skill references related skills at the bottom with clear descriptions, which is good. However, the content itself is quite long and monolithic — the frameworks, tactics, and common mistakes sections could be split into separate reference files. The inline launch timeline table and detailed PLC framework add significant length that could be referenced rather than included. | 2 / 3 |
Total | 9 / 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
- shawnpang/startup-founder-skills
- Commit
4ad31b4
- 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.