Changelog Social Recap
FlorianBruniaux/claude-code-ultimate-guide
Turns CHANGELOG.md entries for a release or a week into LinkedIn, Twitter/X, newsletter and Slack posts in French and English.
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…
$ npx skills add gooseworks-ai/goose-skills --skill feature-launch-playbook -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gooseworks-ai/goose-skills feature-launch-playbook --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content/composites/feature-launch-playbook .claude/skills/feature-launch-playbook && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "feature-launch-playbook" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/content/composites/feature-launch-playbook into .claude/skills/feature-launch-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-launch-playbook", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gooseworks-ai/goose-skills/tree/main/skills/content/composites/feature-launch-playbookType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gooseworks-ai/goose-skills --skill feature-launch-playbook -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gooseworks-ai/goose-skills feature-launch-playbook --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/content/composites/feature-launch-playbook .agents/skills/feature-launch-playbook && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "feature-launch-playbook" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/content/composites/feature-launch-playbook into .agents/skills/feature-launch-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-launch-playbook", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gooseworks-ai/goose-skills --skill feature-launch-playbook -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gooseworks-ai/goose-skills feature-launch-playbook --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/content/composites/feature-launch-playbook .cursor/skills/feature-launch-playbook && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "feature-launch-playbook" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/content/composites/feature-launch-playbook into .cursor/skills/feature-launch-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-launch-playbook", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gooseworks-ai/goose-skills.git --path skills/content/composites/feature-launch-playbook--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gooseworks-ai/goose-skills --skill feature-launch-playbook -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gooseworks-ai/goose-skills feature-launch-playbook --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/content/composites/feature-launch-playbook .gemini/skills/feature-launch-playbook && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "feature-launch-playbook" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/content/composites/feature-launch-playbook into .gemini/skills/feature-launch-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-launch-playbook", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gooseworks-ai/goose-skills feature-launch-playbookInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gooseworks-ai/goose-skills --skill feature-launch-playbook -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/content/composites/feature-launch-playbook .github/skills/feature-launch-playbook && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "feature-launch-playbook" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/content/composites/feature-launch-playbook into .github/skills/feature-launch-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-launch-playbook", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gooseworks-ai/goose-skills --skill feature-launch-playbook -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gooseworks-ai/goose-skills feature-launch-playbook --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/content/composites/feature-launch-playbook .opencode/skills/feature-launch-playbook && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "feature-launch-playbook" agent skill from https://github.com/gooseworks-ai/goose-skills/tree/main/skills/content/composites/feature-launch-playbook into .opencode/skills/feature-launch-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-launch-playbook", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
feature-launch-playbookTake 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…
Feature Launch Playbook is an agent skill from gooseworks-ai/goose-skills. 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.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `skill.meta.json`).
It sits in Product & Project Management, covering Social media posts, Feature launches and release readiness and PRD writing. It works with LinkedIn and X (Twitter). The repository describes itself as: Library of Growth & GTM skills + data APIs for Claude Code, Codex, Cursor to run ads, social, content, lead gen, seo and data scraping. The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c650c6d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Feature Launch Playbook loads about 1.8k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 493 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from gooseworks-ai/goose-skills at commit c650c6d, republished under its MIT licence (© gooseworks-ai). 493 words, ~1,845 tokens.
.claude/skills/feature-launch-playbook/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.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.
Before generating assets, define the messaging foundation:
HEADLINE: [Outcome-driven, not feature-driven]
Bad: "Introducing Advanced Filtering"
Good: "Find your best leads in seconds, not hours"
SUBHEAD: [What it is + who it's for]
"[Feature name] lets [audience] do [capability] so they can [outcome]."
PROOF POINT: [Metric or before/after comparison]
"In beta, [customer] saw [X% improvement / saved X hours]."
CTA: [Single clear action]
"[Try it now / See it in action / Book a demo]"## [Feature Name] — [Date]
[1-2 sentence summary: what + why it matters]
**What's new:**
- [Capability 1]
- [Capability 2]
- [Capability 3]
**Who it's for:** [ICP segment]
[CTA button text] → [link]Subject line options (pick 1, A/B test if possible):
A: [Outcome-driven] — e.g., "Your [workflow] just got 10x faster"
B: [Curiosity-driven] — e.g., "We built the thing you've been asking for"
C: [Direct] — e.g., "New: [Feature Name] is live"
---
Hi [First Name],
[1-sentence hook tied to their pain point]
Today we're launching [Feature Name] — [1-sentence description of what it does].
Here's what this means for you:
- [Benefit 1 — outcome, not feature]
- [Benefit 2]
- [Benefit 3]
[Social proof line if available: "Teams like [Customer] are already using it to [result]."]
[CTA: Try it now / See it in action / Reply to learn more]
[Signature]
P.S. [Urgency or bonus — e.g., "Available on all plans" or "Early access for the next 48 hours"]Generate 3 variants:
Variant A: Story-driven
[Hook: personal story or observation about the problem]
[2-3 lines on why this matters]
Today we shipped [Feature Name].
Here's what it does:
→ [Benefit 1]
→ [Benefit 2]
→ [Benefit 3]
[Social proof or early result]
[CTA — soft: "Check it out" or "Link in comments"]Variant B: Contrarian/hot take
[Hot take about the problem or industry norm]
[2-3 lines on why the status quo is broken]
So we built [Feature Name] to fix it.
[How it works in 2-3 bullets]
[CTA]Variant C: Customer-proof-driven
[Customer result or quote as hook]
[Context on what they were doing before]
[Feature Name] made this possible:
→ [Capability that drove the result]
[CTA]Tweet 1 (hook):
[Announcement + outcome claim in <200 chars]
🧵
Tweet 2:
The problem: [Pain point in ICP language]
Tweet 3:
What we built: [Feature description + screenshot/GIF]
Tweet 4:
Key capabilities:
- [Bullet 1]
- [Bullet 2]
- [Bullet 3]
Tweet 5:
[Social proof or early result]
Tweet 6:
[CTA + link]Headline: [6-8 words max]
Body: [1 sentence, 15 words max]
CTA button: [2-3 words]
Dismiss: "Maybe later"# [Feature Name] — Sales Enablement Brief
## What It Is
[2-3 sentences]
## Who Cares
- [Persona 1]: [Why they care]
- [Persona 2]: [Why they care]
## Talk Track
"[Suggested pitch — 3-4 sentences a rep can use on a call]"
## Objection Handling
| Objection | Response |
|-----------|----------|
| "[Common objection]" | "[Response]" |
## Discovery Questions
- "[Question that surfaces the pain this solves]"
- "[Question that qualifies for this feature]"
## Competitive Context
- [Competitor X]: [Does / doesn't have this]
- [Competitor Y]: [Their approach vs ours]
## Resources
- Demo video: [link]
- Docs: [link]
- Customer story: [link]Generate a launch checklist based on the tier:
Save all assets to the current working directory (or user-specified path) under a [feature-slug]/ folder:
launch-kit.md — All assets in one documentchecklist.md — Launch checklist with owner assignments| Component | Cost |
|---|---|
| All asset generation | Free (LLM reasoning) |
| Total | Free |
None. Pure reasoning skill. Works with any LLM agent.
© gooseworks-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/content/composites/feature-launch-playbook of gooseworks-ai/goose-skills.
Open the folder on GitHubat commit c650c6d
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gooseworks-ai/goose-skills, which our catalogue first saw on October 7, 2026.
Feature Launch Playbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Feature Launch Playbook this skillgooseworks-ai/goose-skills | 1.2k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Changelog Social RecapFlorianBruniaux/claude-code-ultimate-guide | 6.1k | — | ~1.8k | Automated safety check: Notes | CC-BY-SA-4.0 | |
| Money Socialiamzifei/show-me-the-money | 1k | — | ~2k | Automated safety check: Pass | Custom licence | |
| Launch Distributionamplitude/builder-skills | 159 | — | ~2.8k | Automated safety check: Pass | None | |
| Feature Launch Playbookrampstackco/claude-skills | 945 | — | ~6.6k | Automated safety check: Pass | MIT | |
| Socialcoreyhaines31/marketingskills | 54k | 4 repos | ~4.5k | Automated safety check: Pass | MIT |
FlorianBruniaux/claude-code-ultimate-guide
Turns CHANGELOG.md entries for a release or a week into LinkedIn, Twitter/X, newsletter and Slack posts in French and English.
iamzifei/show-me-the-money
Social media management and community building automation. An agent skill from iamzifei/show-me-the-money.
amplitude/builder-skills
Plan and execute multi-channel distribution for product launches across X/Twitter, Reddit, LinkedIn, Hacker News, and other platforms.
rampstackco/claude-skills
The operational playbook for launching a feature well. An agent skill from rampstackco/claude-skills.
coreyhaines31/marketingskills
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.
freekmurze/dotfiles
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms.
gooseworks-ai/goose-skills
Scrape and search Reddit posts using Apify. An agent skill from gooseworks-ai/goose-skills.
gooseworks-ai/goose-skills
Generate or edit an image via any FAL image model (nano-banana edit, gpt-image, flux, ...), ROUTED THROUGH THE fal-proxy so it bills the Ads agent.
gooseworks-ai/goose-skills
Replace an existing video's opening with a supplied clip or free kinetic text hook while retaining and verifying every original body frame, audio, captions and ending.
gooseworks-ai/goose-skills
Scrape blog posts via RSS feeds (free, no API key) with Apify fallback for JS-heavy sites.
gooseworks-ai/goose-skills
Find leads by scraping engagers from a competitor's top LinkedIn posts.
gooseworks-ai/goose-skills
Assemble a ChatGPT chat-reveal video ad from a thread + timeline JSON — one continuous Playwright recording of a ChatGPT mobile chat (user types with the iOS keyboard up → taps send → keyboard…
Works with
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…. Feature Launch Playbook is an agent skill from gooseworks-ai/goose-skills. 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.
Feature Launch Playbook fits situations like: A product marketing team needs to turn a feature spec into launch-ready assets fast; tasks that involve Social media posts; tasks that involve Feature launches and release readiness.
Run `npx skills add gooseworks-ai/goose-skills --skill feature-launch-playbook -a claude-code`. Or copy the skill folder (skills/content/composites/feature-launch-playbook in gooseworks-ai/goose-skills) into .claude/skills/feature-launch-playbook in your project. Claude Code loads it when a task matches its description.
Run `npx skills add gooseworks-ai/goose-skills --skill feature-launch-playbook -a codex`. Or copy the skill folder (skills/content/composites/feature-launch-playbook in gooseworks-ai/goose-skills) into .agents/skills/feature-launch-playbook in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gooseworks-ai/goose-skills --skill feature-launch-playbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feature-launch-playbook, .gemini/skills/feature-launch-playbook, .github/skills/feature-launch-playbook and .opencode/skills/feature-launch-playbook in your project.
SKILL.md names no scripts, command-line tools or credentials: Feature Launch Playbook is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Feature Launch Playbook is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Feature Launch Playbook: Changelog Social Recap (FlorianBruniaux/claude-code-ultimate-guide, 6.1k stars), Money Social (iamzifei/show-me-the-money, 1k stars), Launch Distribution (amplitude/builder-skills, 159 stars) and Feature Launch Playbook (rampstackco/claude-skills, 945 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
gooseworks-ai (a GitHub organization) maintains it in gooseworks-ai/goose-skills, which has 1,240 GitHub stars. The repository holds 273 skills in this directory. The repository was last updated on October 8, 2026.
Source: gooseworks-ai/goose-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.