CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

launch

Builds a launch plan, launch story and press/distribution plan, then drafts the pitch emails and announcement copy. Use when you say 'launch plan', 'how do I get press', 'pitch a reporter', 'announce funding', 'go-to-market for a feature', 'Product Hunt', 'press release', 'launch messaging' or 'we shipped and nobody noticed'. Draws on 394 insights from 124 Lenny's Podcast guests, led by Emilie Gerber, Lulu Cheng Meservey and Jason Feifer.

Quality

95%

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

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

An exceptionally dense, actionable playbook: sequenced plays with explicit exit criteria, a decision table, ready-to-fill deliverables, a grading feedback loop, and clean one-level-deep references verified against the real bundle files. The main cost is token duplication — the Receipts section repeats quotes.md verbatim — which keeps conciseness at 4.

Suggestions

Trim the "Receipts" section to one exemplar quote or remove it: all six quotes appear verbatim in references/quotes.md, so the body spends ~15 lines on duplicated content that "Go deeper" already points to.

Move the "Grade existing work" scoring table into a reference file (e.g. a section of references/frameworks.md) and keep a one-line pointer, since it is a secondary mode used only when the user brings existing work to score.

Add "Done when:" exit criteria to Plays 3, 5, and 6 to match Plays 1, 2, and 4, so every play has an explicit completion checkpoint.

DimensionReasoningScore

Conciseness

The body is dense and telegraphic and assumes competence (never explains what a press release or Product Hunt is; e.g. "Skip the $300-2,000 wire release... Give absolute scale, not 700% from a tiny base"), but the "Receipts" section duplicates all six quotes verbatim from references/quotes.md and the "Grade existing work" table is secondary material — token duplication that keeps it below the every-token-earns-its-place anchor, though well above the some-unnecessary-explanation anchor.

4 / 5

Actionability

Exact parameters throughout: "Max 4 questions", "Max 3 short paragraphs", "follow up after 3-4 days with new info", "expect ~1 opportunity per 20-30 sends", "a fixed window (e.g. three hours head start)", plus a fill-in-the-blank deliverable template and a subject-line formula ("Subject: ___ (goal + column/show named)") — fully executable instruction-only guidance covering the common cases.

5 / 5

Workflow Clarity

Explicit Step 1→3 sequence with a situation→play decision table, per-play exit checkpoints ("Done when: ranked target table, 3 customized pitches, assets staged, follow-up dates set"), a go/no-go readiness gate ("If you cannot say what the press is for, postpone pitching"), and a grade-existing-work feedback loop with 1/3/5 scoring anchors — explicit validation steps, feedback loops, and checklists, above the most-checkpoints-present anchor.

5 / 5

Progressive Disclosure

Scored against the actual bundle: the "Go deeper" section clearly signals references/frameworks.md ("every framework in this skill, how to run it") and references/quotes.md ("verified quotes with timestamps"); both files exist, are one level deep (no nested references inside them), and hold run-detail and the full quote archive while SKILL.md keeps the overview, and a related-skills map (position, pmf-check, growth-model, exec-comms) adds navigation.

5 / 5

Total

19

/

20

Passed

Description

96%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 near-exemplar description: a concrete third-person capability list, an explicit trigger clause with nine natural user phrases, and a distinctive launch/press niche. Only minor overlap risk with adjacent go-to-market and messaging skills keeps distinctiveness at 4.

DimensionReasoningScore

Specificity

"Builds a launch plan, launch story and press/distribution plan, then drafts the pitch emails and announcement copy" lists five concrete, sequenced deliverable actions in third-person voice ("Builds", "drafts", "Draws on"), matching the comprehensive multiple-concrete-actions anchor rather than the several-actions-with-minor-gaps anchor.

5 / 5

Completeness

Explicit 'what' (the five build/draft actions) plus an explicit "Use when..." clause with concrete trigger phrases — exactly the anchor-5 pattern of clearly and explicitly answering both what and when; it is well above the anchor-4 case where the 'when' could be more specific.

5 / 5

Trigger Term Quality

"Use when you say 'launch plan', 'how do I get press', 'pitch a reporter', 'announce funding', 'go-to-market for a feature', 'Product Hunt', 'press release', 'launch messaging' or 'we shipped and nobody noticed'" provides nine natural user phrasings with synonyms (press release / launch messaging / go-to-market) — comprehensive natural-term coverage for this domain, above the good-coverage-with-a-few-missing anchor.

5 / 5

Distinctiveness Conflict Risk

The launch/PR niche is clear with distinctive triggers ("Product Hunt", "pitch a reporter", "we shipped and nobody noticed"), but "go-to-market for a feature" and "launch messaging" are broad enough to carry minor overlap risk with closely related positioning/GTM/comms skills, fitting the mostly-distinct anchor better than the minimal-conflict anchor.

4 / 5

Total

19

/

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

menkesu/awesome-pm-skills

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.