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.
SkillScore82Maintained
Automatic
◆Marketing & Content pack
Last verified 8/16/2026
What it changes
Passed 18 of 22 test cases with the skill, and 9 of 22 without it.
Without skill41%
With skill82%
Checks it passed that the model alone missed
Uses 'Maybe later' as the explicit dismiss text
Includes Asset 6 Sales Enablement Brief for this major update
Includes an Objection Handling matrix or table with responses
and 13 more in the full report
11 fixed7 passed either way2 still failing2 broke
Pass-rate lift
+41 pp
Tokens
+62%
Agent turns
0%
Response time
-18%
Model gemini-3.6-flashMeasured 8/16/2026v118 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
Create the core messaging foundation for a launch of 'QuickExport', a button allowing database admins to dump queries directly into CSV format. Ensure the subhead strictly follows the standard feature-to-outcome template structure.
What was checked, without and with the skill
Checked
Without skill
With skill
Formats SUBHEAD following '[Feature name] lets [audience] do [capability] so they can [outcome]'
Missed
Passed
case-07 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md274 linessingle file
Feature Launch Playbook
Turn a feature spec or product update into a complete launch kit — every asset you need to announce, from changelog to cold email insert. One input, all outputs.
Built for: PMMs or founders who ship features faster than they can write about them. The goal is to go from "feature merged" to "launch assets ready" in one session.
When to Use
"We just shipped [feature] — help me launch it"
"Write launch copy for [feature/update]"
"I need a changelog entry, email, and LinkedIn post for [feature]"
"Generate the full launch kit for [product update]"
"Turn this feature spec into marketing assets"
Phase 0: Intake
Feature Context
Feature name — What are you launching?
One-paragraph description — What does it do? (Can be a Notion doc, PRD excerpt, or plain text)
Who benefits most? — Which ICP segment cares about this? (e.g., "growth teams running outbound")
Problem it solves — What was painful before this existed?
Key capability — The single most impressive thing it does (for the headline)
Launch Context
Launch tier — How big is this?
Tier 1 (Major): New product line, major feature, pricing change → Full launch kit
Tier 2 (Medium): Significant feature, new integration → Email + social + changelog
Tier 3 (Minor): Small improvement, bug fix → Changelog + social mention
Launch date — When does this go live?
CTA — What should the reader do? (Try it, book a demo, read docs, upgrade)
Visual assets available? — Screenshots, GIFs, demo video URL?