release-announcement-writer
Skill3 starsChanged 6 months agoMITView on GitHub
Write release notes, GitHub release copy, website update blurbs, and short launch posts from changelogs, git diffs, README changes, shipped feature lists, or product/system updates. Use when the user asks to announce a release, summarize what changed, prepare public launch copy, write a changelog, turn implementation notes into marketing-safe copy, or create LinkedIn/GitHub/X posts for a new version.
In this repository47 other files it gives its agents.
- agents-md-writerSkill
- ai-image-run-pacingSkill
- automation-state-reconcilerSkill
- backup-readiness-auditorSkill
- brand-voice-linterSkill
- case-study-writerSkill
- client-delivery-auditorSkill
- client-intake-builderSkill
- client-workspace-scaffolderSkill
- code-deduplicatorSkill
- cold-outreach-writerSkill
- demo-animationSkill
- demo-animation-v2Skill
- discovery-briefSkill
- em-dash-removerSkill
- etsy-listing-optimizerSkill
- follow-up-radarSkill
- github-profile-proof-updaterSkill
- github-safe-publisherSkill
- idea-inboxSkill
- implement-client-feedbackSkill
- lead-scorerSkill
- llms-txt-generatorSkill
- local-app-public-demoSkill
- media-spec-checkerSkill
- obsidian-daily-noteSkill
- ops-status-reportSkill
- outreach-pipeline-designerSkill
- php-form-mailerSkill
- proposal-writerSkill
- remove-ai-image-metadataSkill
- research-brief-curatorSkill
- research-to-articleSkill
- screen-recorderSkill
- session-handoffSkill
- skill-builderSkill
- skill-reviewerSkill
- social-campaign-proof-trackerSkill
- skill-nameSkill
- thumbnail-legibility-checkSkill
- thumbnail-set-designerSkill
- vault-janitorSkill
- verify-public-claimsSkill
- web-scraperSkill
- website-change-verifierSkill
- windows-reinstall-plannerSkill
- write-evidence-backed-profileSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill to turn a shipped change into clear public release communication.
- Distinctive: line 21
Write only claims supported by the source material.
- Distinctive: line 22
Add links to the most useful destination: release tag, GitHub repo, website case study, docs, or demo asset.
- Distinctive: line 27
Create only the formats the user needs.
- Distinctive: line 39
Prefer "Added X so users can Y" over "Implemented X".
- Distinctive: line 40
Keep technical nouns when they matter to the audience.
- Distinctive: line 41
Avoid hype, vague AI claims, and unsupported metrics.
- Distinctive: line 45
Do not publish private local paths, API keys, tokens, client names, internal prompts, logs, or deployment details.
- Distinctive: line 46
Do not claim compatibility with a platform unless the release material includes install or usage evidence.
- Distinctive: line 47
If source material is messy or private, rewrite from facts instead of quoting it.
- Distinctive: line 48
If screenshots or GIFs are included, confirm they contain only public-safe UI and assets.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release Announcement Writer
Overview
Use this skill to turn a shipped change into clear public release communication. The output should be accurate, concrete, and safe to publish: what changed, why it matters, who it helps, where to try it, and what to do next.
Workflow
- Gather source material: changelog, release tag, README diff, commit list, issue list, screenshots, demo links, website URLs, and target audience.
- Separate facts from interpretation. Facts include version, date, links, changed files, features, fixes, and install steps. Interpretation includes value proposition, positioning, and social copy.
- Identify the release tier:
patch: fixes, docs, copy, small polish.minor: new skill, new workflow, new install path, meaningful usability improvement.major: compatibility change, large repositioning, or breaking behavior.
- Draft the core release summary in plain language before writing channel-specific variants.
- Write only claims supported by the source material. Avoid inflated wording such as "revolutionary", "first", "complete", or "production-grade" unless the source proves it.
- Add links to the most useful destination: release tag, GitHub repo, website case study, docs, or demo asset.
- Finish with a short verification checklist: links work, version is correct, screenshots/GIFs are public-safe, and private implementation details are absent.
Output Set
Create only the formats the user needs. If they ask for a full launch pack, include:
- GitHub release notes: concise title, summary, highlights, install/upgrade notes, links.
- README or website blurb: 1 short paragraph that explains the user-facing value.
- Social post: 1 plain-language announcement with the repo/case-study link.
- Short version: 1-2 sentences for profile READMEs, cards, or newsletters.
- Optional changelog bullets: grouped under Added, Changed, Fixed, Docs, Safety.
Voice
- Be specific and practical.
- Lead with the outcome, not the internal effort.
- Prefer "Added X so users can Y" over "Implemented X".
- Keep technical nouns when they matter to the audience.
- Avoid hype, vague AI claims, and unsupported metrics.
Safety
- Do not publish private local paths, API keys, tokens, client names, internal prompts, logs, or deployment details.
- Do not claim compatibility with a platform unless the release material includes install or usage evidence.
- If source material is messy or private, rewrite from facts instead of quoting it.
- If screenshots or GIFs are included, confirm they contain only public-safe UI and assets.
Reference Template
For a reusable structure, read references/release-copy-template.md.
Final Response
Return the finished copy first. Then include a compact note listing source facts used, any assumptions, and links or assets that still need verification.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

