release-announcement Skill
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler. Published by microsoft in amplifier-app-paperclip.
Decision snapshot
Is this a fit?
Documentation, Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is release-announcement Skill?
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler. Published by microsoft in amplifier-app-paperclip. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Writing
- Documentation use cases
- Writing use cases
Declared skill metadata
- Source file: packages/skills-catalog/catalog/optional/content/release-announcement/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use release-announcement Skill
- Use it for documentation.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-app-paperclip
- Skill file: packages/skills-catalog/catalog/optional/content/release-announcement/SKILL.md
What it does
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
Skill instructions
Release Announcement Write the channel-appropriate announcement for a release without churn. Different surfaces need different shapes: a changelog entry is not a blog post is not a social card. The bar is: a reader of the chosen surface can decide in under 30 seconds whether this release affects them, and if so what to do. When to use - A version, feature, or fix is shipping and needs writeup for at least one surface. - A previously private feature is going GA. - A breaking change needs broadcast before users hit it. When not to use - An internal-only change with no user impact. Update internal docs; do not announce. - The release is incomplete (still in active development). Wait until it ships, even if marketing wants the post. Determine the audience and channel first | Audience | Best channel | Tone | |---|---|---| | Existing power users | Changelog, in-app note | Terse, factual, links | | Engineering teams adopting your API | Release notes, dev blog | Examples, migration steps, vers
Verified compatibility and discovery
Frequently asked questions
What is release-announcement?
release-announcement is a open-source AI agent skill with Copy skill directory. Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
Who is release-announcement best for?
release-announcement is best for reusing agent instructions, scripts, and references, documentation workflows, writing workflows.
How do I install release-announcement?
Install or run release-announcement using Copy skill directory. Check release-announcement for the latest setup command.
Is release-announcement actively maintained?
release-announcement may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
