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.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./config/claude/skills/launch-strategy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable instruction skill with clear phasing and useful checklists, scoring well on actionability and workflow clarity. It is held back by motivational padding and a monolithic single-file structure with no progressive disclosure into reference files.

Suggestions

Trim motivational/restatement prose (e.g., the 'Core Philosophy' intro and the closing summary lines under each channel type) to assume Claude's competence and save tokens.

Move the Product Hunt section and case studies into a reference file (e.g., references/product-hunt.md) and link to it from the body, enabling one-level-deep progressive disclosure.

Add explicit validation checkpoints between phases (e.g., 'Only proceed to the next phase when the current phase goal is met') to make the soft per-phase goals into hard feedback loops.

DimensionReasoningScore

Conciseness

Mostly efficient and well-organized, but includes motivational prose and restatements Claude doesn't need (e.g., 'The best companies don't just launch once—they launch again and again,' 'Rented channels give speed, not stability').

3 / 5

Actionability

Provides concrete per-phase action lists, platform-specific tactics, named tools (SparkToro, Navattic), case studies, and checklists; minor gaps in measurable cadence/timing specifics.

4 / 5

Workflow Clarity

The five-phase launch is a clearly sequenced multi-step process with a goal per phase as a soft checkpoint, plus pre/launch/post checklists; explicit validate->fix->retry feedback loops are absent but the skill is not destructive/batch so no cap applies.

4 / 5

Progressive Disclosure

No bundle files exist (references/scripts/assets absent), so all content sits inline in one ~350-line file; internal section headers are good, but bulk that could be split (Product Hunt deep-dive, case studies) is inlined with no one-level-deep references.

3 / 5

Total

14

/

20

Passed

Description

81%Weight 40%Scale 1-5

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 is strong: it includes an explicit 'Use when' clause with a rich set of natural trigger terms and a clear niche, making it highly distinct. Its only weakness is that the 'what' coverage is stated abstractly rather than as a list of concrete capabilities.

Suggestions

Replace the abstract coverage clause ('covers phased launches, channel strategy, and ongoing launch momentum') with a short list of concrete actions (e.g., 'plan phased launches, map owned/rented/borrowed channels, run Product Hunt launches, and sequence post-launch momentum').

Tighten the 'when' clause by deduplicating near-synonyms (e.g., 'feature release'/'announcement'/'product update') to reduce token cost without losing trigger coverage.

DimensionReasoningScore

Specificity

Names the domain plus coverage areas ('phased launches, channel strategy, and ongoing launch momentum'), but the actions are high-level and abstract rather than a list of several specific concrete actions.

3 / 5

Completeness

Explicitly answers both what (phased launches, channel strategy, ongoing momentum) and when ('Also use when the user mentions...'), but the 'what' side is slightly less concrete than the fully-specified anchor.

4 / 5

Trigger Term Quality

Comprehensive set of natural trigger terms including synonyms and a platform name ('launch,' 'Product Hunt,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update') that users would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear product-launch niche with many distinct, specific triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.