CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launch

When the user wants to plan a product or feature launch, or asks whether it's ready, when to announce, or how to get noticed: Product Hunt, beta and early access, waitlists, release go-to-market, launch checklists, release notes. For marketing after launch, see marketing-ideas. For the offer, see offers.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/launch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 playbook with clear phase sequencing, a readiness gate, and properly wired one-level-deep references. Its main weakness is token efficiency: motivational framing and repeated content across the post-launch, ongoing-strategy, and checklist sections could be consolidated.

Suggestions

Consolidate duplicated post-launch content: the "Post-Launch Product Marketing", "Ongoing Launch Strategy", and Post-Launch checklist sections restate the same actions (onboarding emails, comparison pages, momentum) — merge into one section and reference it from the checklist.

Trim low-density prose: cut the "Core Philosophy" motivational framing and aphorism closers ("Rented channels give speed, not stability") to respect token budget; the ORB bullets and case studies already carry the substance.

Move the detailed Product Hunt strategy and case studies (SavvyCal, Reform) into a references/product-hunt.md file, keeping a short summary plus the before/on/after steps in SKILL.md to strengthen progressive disclosure.

DimensionReasoningScore

Conciseness

The body is genuine domain expertise (ORB framework, SLC gate, case studies) rather than concepts Claude already knows, but there is noticeable tightening opportunity: the motivational "Core Philosophy" section, aphorism closers, and substantive duplication between the Post-Launch section, Ongoing Strategy section, and the three checklists. This matches "mostly efficient but could be tightened" rather than the minor-trim profile of anchor 4.

3 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: "Recruit early users one-on-one to test for free", "Throttle invites in batches (5-10% at a time)", "Respond to every comment in real-time", plus named tools (SparkToro, ListenNotes, Navattic, Introw) and detailed case studies. A few directives remain high-level ("Build relationships with influential supporters"), so it stops short of fully actionable anchor 5.

4 / 5

Workflow Clarity

The five phases are clearly sequenced with per-phase goals, preceded by an explicit readiness gate with pass criteria ("Pass the gate, then run the phases below") and a quick-check checklist; Product Hunt is broken into before/on/after sequencing. It lacks the error-recovery feedback loops of anchor 5, though those are largely inapplicable to this non-destructive domain.

4 / 5

Progressive Disclosure

Both bundle files (references/shipped-changes.md, references/site-launch-qa.md) exist, are one level deep, and are clearly signaled exactly where relevant in the body. However, the SKILL.md itself is a ~380-line full playbook with the Product Hunt strategy, case studies, and ongoing tactics inlined, rather than a lean overview with content appropriately split — matching anchor 4's "most content appropriately placed; minor organization gaps".

4 / 5

Total

15

/

20

Passed

Description

78%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 explicit, natural trigger guidance, a concrete topic list, and unusually good boundary disambiguation against sibling skills. The only gap is that the "what" reads as a scope list rather than an explicit capability statement, and a few natural trigger synonyms are absent.

DimensionReasoningScore

Specificity

Lists several specific actions and scope items — "plan a product or feature launch", "whether it's ready", "when to announce", "how to get noticed", plus concrete topics (Product Hunt, waitlists, launch checklists, release notes). Coverage is topic-list style rather than a comprehensive enumeration of capabilities, so it falls just short of the anchor-5 example.

4 / 5

Completeness

The "When the user wants to..." clause provides explicit, concrete trigger guidance (so no cap applies), and the "what" is conveyed through "plan a product or feature launch" plus the topic list. The "what" is more an implied scope than an explicit capability statement, placing it between anchors 4 and 5.

4 / 5

Trigger Term Quality

Good keyword coverage with natural user phrases ("product or feature launch", "is it ready", "when to announce", "get noticed", "Product Hunt", "beta and early access", "waitlists", "release notes"). A few natural variations are missing (e.g., "ship a release", "GA", "announce"), keeping it below the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear launch-planning niche with distinct triggers (Product Hunt, waitlists, launch checklists) and explicit boundary disambiguation — "For marketing after launch, see marketing-ideas. For the offer, see offers." — minimizing conflict with adjacent skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/launch/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.