agentsclimarketplace

Changelog voice

Skill Dragoon0x/product-skills/skills/communication/changelog-voice

The product thinking layer for AI agents. 580 skills. 48 commands. 8 domains. - Product strategy, discovery, execution, analytics, growth, experience, conversion, communication and more.

Install
npx -y skills add Dragoon0x/product-skills --skill changelog-voice

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Ship updates people actually want to read. Structures release notes, changelog entries, and product updates with what-changed, why-it-matters, and what-to-do-next. Use when writing changelogs or release announcements.

SKILL.md

1.5 KB, as published. Nobody here has run it

Changelog Voice

Ship updates people actually want to read.

How to use

  • /changelog-voice Apply changelog constraints to this conversation.

Constraints

Entry Structure

  1. What changed (specific, concrete, no marketing language)
  2. Why it matters (what the user can now do that they couldn't before)
  3. How to use it (link or brief instruction)

Rules

  • MUST lead with the user benefit, not the technical change
  • MUST categorize: New, Improved, Fixed, Removed
  • SHOULD include a visual (screenshot, gif, video) for UI changes
  • NEVER say "various bug fixes" without specifics
  • NEVER announce something as "new" that was previously broken and is now working
  • SHOULD mention breaking changes prominently with migration steps

Tone

  • Direct, not corporate ("You can now..." not "We are pleased to announce...")
  • Honest about what's still missing or in progress
  • Brief. Respect the reader's time.
  • SHOULD acknowledge when a change was user-requested ("You asked, we built it")

Anti-Patterns

  • Changelogs that read like marketing emails
  • Burying breaking changes in a long list of improvements
  • Announcing features that aren't actually available yet
  • Using changelogs as a growth channel (no "invite a friend" CTAs in release notes)
  • Updates without dates

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.