CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

64

Quality

81%

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

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.

A well-structured, genuinely actionable launch-marketing playbook whose domain knowledge (ORB framework, phased launches, real case studies) earns its place in context. Its weaknesses are padding — motivational prose and repeated Product Hunt guidance — and a monolithic single-file layout where reference material is inlined rather than split out.

Suggestions

Move the Product Hunt playbook, its case studies, and the ORB-framework example stories (Superhuman, Notion, TRMNL, SavvyCal, Reform) into a references/ file (e.g. references/case-studies.md), keeping SKILL.md as a lean overview with one-level-deep, clearly signaled references.

Trim motivational and restated-truism prose (the 'Core Philosophy' narrative, 'Rented channels give speed, not stability', 'It's easier to build on existing momentum than start from scratch') to cut tokens without losing guidance.

Add explicit advancement criteria between the five phases (e.g. 'Proceed to Phase 2 only when N internal users have completed onboarding without critical bugs'), turning the per-phase 'Goal' statements into real validation gates.

DimensionReasoningScore

Conciseness

The body is mostly efficient — phase action lists, checklists, and genuinely novel case studies — but padded sections remain: motivational 'Core Philosophy' prose, restated truisms ('Rented channels give speed, not stability'), and Product Hunt guidance repeated across 'How to Launch Successfully' and two case studies, matching anchor 3's 'could be tightened' rather than anchor 2's pervasive padding.

3 / 5

Actionability

As an instruction-only skill it offers concrete, specific guidance: per-phase action lists, platform-specific tactics, named tools (SparkToro, Listen Notes, Navattic), and a pre/launch/post checklist. It falls short of anchor 5 only because some guidance stays abstract ('Build buzz', 'Maximize exposure') without concrete examples of what to do.

4 / 5

Workflow Clarity

The Five-Phase Launch Approach is a clearly sequenced multi-step workflow, each phase carrying an explicit 'Goal:' checkpoint plus a pre/post checklist. It misses anchor 5 because there are no explicit criteria or validation gates for advancing from one phase to the next — the checkpoints are present but the gates are implicit.

4 / 5

Progressive Disclosure

The body has good section structure but is a ~340-line monolith with no bundle files: content that clearly belongs in separate references — the Product Hunt playbook with its case studies, platform-specific tactics, and the Superhuman/Notion/TRMNL examples — is inlined, matching anchor 3's 'content that should be separate is inline' and falling short of anchor 4's mostly-split structure.

3 / 5

Total

14

/

20

Passed

Description

91%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.

A strong description with an explicit 'Use when' trigger clause, a clear statement of what the skill covers, and a rich set of natural trigger terms in third-person voice. Its only weaknesses are the mildly vague 'ongoing launch momentum' phrase and a couple of broad trigger terms that could collide with sibling marketing skills.

DimensionReasoningScore

Specificity

The description names the domain and several specific objects of work ("plan a product launch, feature announcement, or release strategy"; "phased launches, channel strategy"), which is concrete for a strategy skill, but the coverage list mixes in a buzzwordy item ("ongoing launch momentum") and stops short of comprehensive, matching anchor 4 rather than 5.

4 / 5

Completeness

It explicitly answers both what ("This skill covers phased launches, channel strategy, and ongoing launch momentum") and when ("When the user wants to plan a product launch... Also use when the user mentions..."), with concrete trigger phrases — a clean match to anchor 5, clearly above anchor 4's weaker 'when' clause.

5 / 5

Trigger Term Quality

It lists nine natural trigger phrases users would actually say ('launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update'), covering synonyms and variants comprehensively as in the anchor 5 example.

5 / 5

Distinctiveness Conflict Risk

The niche is mostly distinct with strong specific triggers (Product Hunt, beta launch, waitlist), but 'announcement' and 'product update' are broad enough to overlap with the general marketing skills this very file lists as related, placing it between anchors 4 and 5 rather than at 5.

4 / 5

Total

18

/

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.

Validation — 15 / 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

Path

config/claude/skills/marketing/skills/launch-strategy/SKILL.md

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.