CtrlK
BlogDocsLog inGet started
Tessl Logo

feature-launch-playbook

Take a new feature or product update and generate the full launch kit: changelog entry, email announcement, LinkedIn post variants, in-app banner text, Twitter/X thread, and internal sales enablement one-pager. Pure reasoning skill that chains product context with audience-specific copy generation. Use when a product marketing team needs to turn a feature spec into launch-ready assets fast.

68

Quality

83%

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

75%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, actionable playbook with a clear phased workflow and concrete templates for each launch asset. It could be tightened slightly and consolidate the duplicate trigger-phrase sections.

Suggestions

Merge the 'Trigger Phrases' section into 'When to Use' to remove duplication and tighten the body.

Add a brief validation/review checkpoint after asset generation (e.g., confirm tier-appropriate assets were produced and CTA/links are filled) to push workflow clarity toward 5.

Consider splitting the six asset templates into a single one-level reference file to improve progressive disclosure given the body's length.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — the asset templates are the core value rather than padded explanation — but 'Trigger Phrases' partially duplicates 'When to Use', and a few template blocks could be tightened.

4 / 5

Actionability

Concrete fill-in-the-blank templates for every asset plus a numbered intake and tier-based checklists give mostly executable, copy-ready guidance, though they remain scaffolded templates rather than fully fleshed examples.

4 / 5

Workflow Clarity

Phases 0–4 (Intake → Core Messaging → Generate Assets → Checklist → Output) are clearly sequenced with the intake acting as a gating step; no destructive/batch validation is required for a copy-generation skill, so minor checkpoint gaps keep it at 4 rather than 5.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed phases and assets with no nested references, and no bundle files exist; the long inlined asset templates are appropriate for a generation skill, with only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

92%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, specific description that clearly names its deliverables, audience, and trigger condition in third person. Minor room to broaden natural trigger phrasing.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete deliverables — 'changelog entry, email announcement, LinkedIn post variants, in-app banner text, Twitter/X thread, and internal sales enablement one-pager' — giving comprehensive, specific coverage rather than vague abstraction.

5 / 5

Completeness

It explicitly states both what it does (generate the full launch kit with the listed assets) and when to use it ('Use when a product marketing team needs to turn a feature spec into launch-ready assets fast').

5 / 5

Trigger Term Quality

It surfaces natural terms a user would say ('launch kit', 'changelog entry', 'feature spec', 'launch-ready assets'), but lacks a few common synonyms/variations a requester might use, so it sits just below fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

The product-marketing launch-kit niche is clearly scoped with distinct triggers, making overlap with unrelated skills minimal.

5 / 5

Total

19

/

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
gooseworks-ai/goose-skills
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.