CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

59

Quality

68%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/launch-strategy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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 but overly verbose launch strategy guide that reads more like a marketing blog post than a concise skill for Claude. Its strongest aspect is the well-structured five-phase workflow with clear checklists, but it's weighed down by extensive explanations of concepts Claude already understands, lengthy case studies, and general marketing advice that doesn't provide concrete, executable artifacts like template copy or specific commands.

Suggestions

Cut the Core Philosophy section, case studies, and explanatory text about what owned/rented/borrowed channels are—reduce to just the actionable tactics and channel-specific instructions Claude needs to generate recommendations.

Add concrete, copy-paste-ready templates: example launch email copy, example Product Hunt taglines, example social post formats, and example waitlist landing page copy structure.

Move the ORB Framework details and Product Hunt deep-dive into separate reference files to keep SKILL.md as a concise overview with clear pointers.

Replace vague directives like 'Create landing page with clear value proposition' with specific structural templates or example content blocks Claude can adapt.

DimensionReasoningScore

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 (Superhuman, Notion, TRMNL, SavvyCal, Reform) add bulk without providing actionable specificity. The 'Core Philosophy' section is pure padding.

1 / 3

Actionability

The skill provides structured checklists and phased steps which are somewhat actionable, but lacks concrete executable artifacts—no template text, no example email copy, no specific commands or code. 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 specific actions at each stage.

3 / 3

Progressive Disclosure

The skill references related skills at the bottom (marketing-ideas, email-sequence, page-cro, etc.) which is good navigation, but the main body is a monolithic wall of text that could benefit from splitting detailed sections (Product Hunt strategy, ORB framework details, case studies) into separate reference files. No bundle files exist to offload content.

2 / 3

Total

8

/

12

Passed

Description

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 skill 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 actions rather than listing domain areas. The description effectively distinguishes itself from other marketing or strategy skills through its focused launch-specific terminology.

Suggestions

Add more concrete specific actions to improve specificity, e.g., 'Creates launch timelines, drafts announcement copy, designs phased rollout plans, builds channel distribution strategies.'

DimensionReasoningScore

Specificity

The description mentions some actions like 'plan a product launch, feature announcement, or release strategy' and references 'phased launches, channel strategy, and ongoing launch momentum,' but these are more domain areas than concrete specific actions. It doesn't list discrete tasks like 'create launch timelines, draft announcement copy, build channel distribution plans.'

2 / 3

Completeness

Clearly answers both 'what' (plan product launches, feature announcements, release strategies, phased launches, channel strategy, launch momentum) and 'when' (explicit 'Use when' clause with specific trigger terms and scenarios).

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,' and 'product update.' These are highly natural and cover many common variations.

3 / 3

Distinctiveness Conflict Risk

The description carves out a clear niche around product launches and go-to-market strategy with highly specific trigger terms like 'Product Hunt,' 'beta launch,' 'waitlist,' and 'go-to-market' that are unlikely to conflict with other skills.

3 / 3

Total

11

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
freekmurze/dotfiles
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.