agentsclimarketplace
Sign in

Product announcements

Skill shinzoxD/knackbox/skills/writing/product-announcements

Write product launch and feature announcements for users and stakeholders. Use whenever the user asks for a launch announcement, feature blog, "what's new" marketing note, launch email, or customer-facing message about a new capability — even from a bullet list of changes.From its SKILL.md

Install
npx -y skills add shinzoxD/knackbox --skill product-announcements

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

One thing to look at

  • 0 stars0 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 file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, 319 tokens by cl100k_base, as published. Nobody here has run it

Product Announcements

Announcements sell outcomes, not ticket IDs. Be accurate: do not claim what the product cannot do today.

Workflow

  1. Audience (users, admins, internal, press-lite) and channel (email, blog, in-app).
  2. Core value prop in one sentence; 1–3 supporting benefits.
  3. Who gets it (plan tiers, regions, flags) and when.
  4. How to start (CTA) and where to learn more.
  5. Proof (customers, metrics) only if provided.
  6. Risks/caveats (beta, breaking changes) honestly.

Output format

# <Headline>

**Subhead:** …

## Why it matters
…

## What's new
- benefit-led bullets

## Get started
CTA + steps

## Details / availability
…

## FAQ (optional)
…

Rules

  1. No invented metrics, logos, or launch dates.
  2. Benefit → feature, not feature dump.
  3. Match channel length (in-app shorter than blog).
  4. Breaking changes get plain-language migration notes.
  5. Separate internal stakeholder note if both audiences needed.
  6. Avoid hype words without substance ("revolutionary", "seamless") unless user brand voice requires — still ground in facts.

Edge cases

  • Quiet launch / beta: set expectations; invite feedback.
  • Multiple features: theme them; don't laundry-list 20 equal bullets.
  • Regulated claims: stay conservative; mark legal review needed.

What ships with it: 1 file

1.3 KB alongside SKILL.md

benchmarks/

Keep looking

Skills are one crate of 326,422. 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.