Release Changelog Discord MessageCAUTION

The open-source app everyone uses to manage agents at work

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: release-changelog-discord-message
description: >
  Write the Discord announcement for a stable Paperclip release from the release
  changelog. Use when a release issue needs a copy-pasteable dotta-voice Discord
  post or refreshed discord_announcement document.
---

# Release Discord Announcement Skill

Write the Discord release announcement for the **stable** Paperclip release.

This is the companion to `.agents/skills/release-changelog/SKILL.md`. That skill
writes the changelog — during the beta soak it lives at
`releases/beta/v{beta-version}.md` on the `release-notes/v{beta-version}`
branch, and after the stable ships a canonicalization PR renames it to
`releases/vYYYY.MDD.P.md` (see that skill's Channel Process section). This
skill turns that file into
a single copy-pasteable Discord block, in dotta's voice, and posts it as the
`discord_announcement` document on the release issue.

## What dotta said

> This is for discord — try to follow my format. If I have a section where I
> think about the future, pull from recent issues we're working on etc.

The Discord announcement is **not** the changelog. The changelog is exhaustive;
the announcement is opinionated, in-voice, and built around the same handful of
shipped highlights plus a real "what's next" + "what's on my mind" pulled from
current Paperclip work — not invented.

## When to use

- After `release-changelog` has produced the changelog (beta-keyed on the
  `release-notes/v{beta-version}` branch during the soak, or the
  canonicalized `releases/vYYYY.MDD.P.md` after the stable ships).
- When the release issue (the one assigned by the release routine) asks for a
  Discord announcement, or has a `discord_announcement` document that needs to
  be refreshed for a new date/version.
- Never run this in isolation. The version, date, contributor list, and
  highlight set MUST match the matching changelog file — if the changelog has
  been updated, refresh this too.

## Output

A single fenced markdown code block, ready to paste into Discord. Attached as
issue document key `discord_announcement` on the release issue, and pasted
verbatim into a comment on that issue so the human can copy it out.
When Cases are enabled, also upsert the social child case described below.

```bash
PUT /api/issues/{releaseIssueId}/documents/discord_announcement
{
  "title": "Discord announcement",
  "format": "markdown",
  "body": "<the announcement>",
  "baseRevisionId": "<latest if updating>"
}
```

If the document already exists, fetch it first and pass the current
`baseRevisionId`. Never overwrite silently — if the version has changed since
the document was last written, mention what changed in the issue comment.

## Format (follow this template)

Use Discord emoji shortcodes (`:paperclip:`, `:lock:`, `:brain:` ...) — NOT the
Unicode emoji. Discord renders the shortcodes; the changelog file uses prose.

```
:paperclip: :paperclip: :paperclip: CLIPPERS!!! v{VERSION} IS OUT :paperclip: :paperclip: :paperclip:

OFFICIAL TWITTER: https://x.com/papercliping - follow it, report any others

## Highlights

:emoji: **Feature Name** - one-sentence description in dotta's voice.
:emoji: **Feature Name** - ...
:emoji: **Feature Name** - ...

... and a long tail of {flavor of the rest}. Read the [full release notes](<github link>).

## WHATS NEXT (:motorway:  Roadmap)

* **Theme A** - one-line forward-looking blurb
* **Theme B** - ...
* **Theme C** - ...

## What's on my mind

* **Topic** - what's bugging dotta / what's queued / open questions
* **Topic** - ...

## PRESS                              (optional — only if there is real press)

* **Outlet / Person** - what happened ([link](<x.com link>))

## WHAT I NEED FROM YOU               (optional — only if there's a real ask)

FOLLOW THE TWITTER: https://x.com/papercliping - that's the only official one
TELL ME if you're using Paperclip in your business - I want to meet you

## Community

Thank you to everyone who contributed to this release!

```
@username1, @username2, @username3
```

## In Summary

PAPERCLIP IS THE AI ORCHESTRATOR FOR HUMANS TO ACCOMPLISH 100x MORE WORK

Every single person will be managing a team of a dozen, or a hundred, or a
thousand agents and Paperclip will be the default tool to manage it all.

ITS TIME TO CLIP :paperclip: :paperclip: :paperclip:

FULL RELEASE NOTES

https://github.com/paperclipai/paperclip/blob/master/releases/v{VERSION}.md

||@everyone||
```

Notes on the template:

- The opening and closing `:paperclip: :paperclip: :paperclip:` bookends are
  part of the brand — keep them.
- Name the install channels somewhere in the post: `npx paperclipai@latest`
  for the stable, `@beta` / `@nightly` / `@canary` for earlier access, and
  Docker `:latest` moving **only** on stable releases.
- The FULL RELEASE NOTES link points at `releases/v{VERSION}.md` on
  `master` — that file exists only after the post-stable canonicalization
  PR merges. Merge it before the announcement is posted.
- Sections may be UPPERCASE or Title Case — dotta has used both. Pick a style
  and stay consistent within a single post.
- Use `||@everyone||` (Discord spoiler-wrapped) at the very end so it pings
  exactly once when the spoiler is removed by the poster.

## Language tips

These are extracted from how dotta has written the last several announcements.
Mimic this register; do not invent a "professional" tone.

- **First person, conversational.** "I want to meet companies using Paperclip",
  "what's on my mind", "if that's you let me know". Not "Paperclip is excited
  to announce".
- **ALL CAPS for excitement and asks**, especially in the opener, the section
  headers, the "WHAT I NEED FROM YOU" section, and the closing tagline. Do not
  ALL-CAPS feature descriptions.
- **One emoji shortcode per highlight bullet**, picked to evoke the feature
  (`:lock:` for secrets, `:brain:` for planning, `:mag:` for search,
  `:cloud:` for cloud / sandbox, `:jigsaw:` for plugins, `:rewind:` for
  history/restore

CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (2)

.claude/skills/company-creator

.claude/skills/paperclip

Gates applied: no_behavioural_pass.