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.

58

Quality

67%

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 ./.claude/skills/launch-strategy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%

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

A well-organized, comprehensive launch playbook with strong sequencing and checklists, but it is verbose and monolithic with no progressive disclosure into reference files. Actionability is decent but prose-heavy rather than template-driven.

Suggestions

Split the long-form content (ORB channel deep-dives, Product Hunt case studies) into reference files and keep SKILL.md as a concise overview with clearly signaled links, improving both conciseness and progressive_disclosure.

Add executable templates or copy-paste-ready artifacts (launch announcement drafts, email sequence skeletons, Product Hunt listing tagline templates) to lift actionability beyond prose instructions.

Tighten the Core Philosophy and channel definition sections to remove exposition of general marketing concepts Claude already knows.

DimensionReasoningScore

Conciseness

Mostly efficient and well-structured, but substantial narrative exposition on concepts Claude already knows (launch philosophy, channel definitions, case studies) could be tightened into denser actionable guidance.

2 / 3

Actionability

Provides concrete actions, checklists, and named steps, but guidance is instructional prose rather than executable artifacts (no templates, scripts, or copy-paste-ready launch assets).

2 / 3

Workflow Clarity

The five-phase launch approach is clearly sequenced with goals per phase, and the Product Hunt and checklist sections give explicit before/on/after sequencing with feedback follow-ups.

3 / 3

Progressive Disclosure

This is a monolithic wall of text with no references to separate files despite being long; the single inline reference is to an external context file rather than to bundled reference materials.

1 / 3

Total

8

/

12

Passed

Description

82%

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 explicit 'Use when' triggers and a rich set of natural keywords, plus a clear niche. It is slightly light on listing multiple concrete specific actions, leaning on broad categories instead.

Suggestions

Consider enumerating 1-2 more concrete actions (e.g., 'draft launch announcements, sequence pre-launch teasers') to strengthen specificity beyond the broad 'channel strategy' framing.

DimensionReasoningScore

Specificity

Names the domain and some concrete actions ('phased launches, channel strategy, and ongoing launch momentum') but the actions are broad categories rather than multiple specific concrete actions like 'fill forms, merge documents'.

2 / 3

Completeness

Clearly answers both what (covers phased launches, channel strategy, ongoing launch momentum) and when ('When the user wants to plan...', 'Also use when the user mentions...') with explicit triggers.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'launch', 'Product Hunt', 'feature release', 'announcement', 'go-to-market', 'beta launch', 'early access', 'waitlist', 'product update'.

3 / 3

Distinctiveness Conflict Risk

A clear niche in launch/go-to-market strategy with distinct trigger keywords unlikely to conflict with other skills.

3 / 3

Total

11

/

12

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
TheCraigHewitt/seomachine
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.