Release
pwrdrvr/openclaw-codex-app-server
Plan and publish a GitHub Release in a tag-driven repository.
Write the Discord announcement for a stable Paperclip release from the release changelog.
$ npx skills add paperclipai/paperclip --skill release-changelog-discord-message -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install paperclipai/paperclip release-changelog-discord-message --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-changelog-discord-message .claude/skills/release-changelog-discord-message && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "release-changelog-discord-message" agent skill from https://github.com/paperclipai/paperclip/tree/master/.agents/skills/release-changelog-discord-message into .claude/skills/release-changelog-discord-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-changelog-discord-message", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/paperclipai/paperclip/tree/master/.agents/skills/release-changelog-discord-messageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add paperclipai/paperclip --skill release-changelog-discord-message -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install paperclipai/paperclip release-changelog-discord-message --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release-changelog-discord-message .agents/skills/release-changelog-discord-message && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-changelog-discord-message" agent skill from https://github.com/paperclipai/paperclip/tree/master/.agents/skills/release-changelog-discord-message into .agents/skills/release-changelog-discord-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-changelog-discord-message", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add paperclipai/paperclip --skill release-changelog-discord-message -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install paperclipai/paperclip release-changelog-discord-message --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release-changelog-discord-message .cursor/skills/release-changelog-discord-message && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release-changelog-discord-message" agent skill from https://github.com/paperclipai/paperclip/tree/master/.agents/skills/release-changelog-discord-message into .cursor/skills/release-changelog-discord-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-changelog-discord-message", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/paperclipai/paperclip.git --path .agents/skills/release-changelog-discord-message--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add paperclipai/paperclip --skill release-changelog-discord-message -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install paperclipai/paperclip release-changelog-discord-message --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release-changelog-discord-message .gemini/skills/release-changelog-discord-message && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release-changelog-discord-message" agent skill from https://github.com/paperclipai/paperclip/tree/master/.agents/skills/release-changelog-discord-message into .gemini/skills/release-changelog-discord-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-changelog-discord-message", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install paperclipai/paperclip release-changelog-discord-messageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add paperclipai/paperclip --skill release-changelog-discord-message -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release-changelog-discord-message .github/skills/release-changelog-discord-message && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release-changelog-discord-message" agent skill from https://github.com/paperclipai/paperclip/tree/master/.agents/skills/release-changelog-discord-message into .github/skills/release-changelog-discord-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-changelog-discord-message", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add paperclipai/paperclip --skill release-changelog-discord-message -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install paperclipai/paperclip release-changelog-discord-message --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release-changelog-discord-message .opencode/skills/release-changelog-discord-message && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release-changelog-discord-message" agent skill from https://github.com/paperclipai/paperclip/tree/master/.agents/skills/release-changelog-discord-message into .opencode/skills/release-changelog-discord-message/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-changelog-discord-message", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
release-changelog-discord-messageWrite the Discord announcement for a stable Paperclip release from the release changelog.
Release Changelog Discord Message is an agent skill from paperclipai/paperclip. 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 discordannouncement document.
Its SKILL.md is about 5.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes. It works with Discord. The repository describes itself as: The open-source app everyone uses to manage agents at work. The licence is MIT.
8 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit de9ab8e. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npxFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
x.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Release Changelog Discord Message loads about 5.4k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 1,362 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from paperclipai/paperclip at commit de9ab8e, republished under its MIT licence (© paperclipai). 1,362 words, ~5,421 tokens.
.claude/skills/release-changelog-discord-message/SKILL.md (or your agent's skills folder).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.
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.
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).discord_announcement document that needs to
be refreshed for a new date/version.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.
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.
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:
:paperclip: :paperclip: :paperclip: bookends are
part of the brand — keep them.npx paperclipai@latest
for the stable, @beta / @nightly / @canary for earlier access, and
Docker :latest moving only on stable releases.releases/v{VERSION}.md on
master — that file exists only after the post-stable canonicalization
PR merges. Merge it before the announcement is posted.||@everyone|| (Discord spoiler-wrapped) at the very end so it pings
exactly once when the spoiler is removed by the poster.These are extracted from how dotta has written the last several announcements. Mimic this register; do not invent a "professional" tone.
:lock: for secrets, :brain: for planning, :mag: for search,
:cloud: for cloud / sandbox, :jigsaw: for plugins, :rewind: for
history/restore, :thread: for threads, etc.).@username, @username.
Exclude bots and the specific folks on the changelog skill's canonical
exclusion list — same rules.ITS TIME TO CLIP :paperclip: :paperclip: :paperclip:. Keep it.release-changelog — the
beta-keyed file during the soak, releases/vYYYY.MDD.P.md once
canonicalized. Use the version and contributor list from that file —
never re-derive them.release case with key paperclip-release:vYYYY.MDD.P.
If it does not exist and Cases are enabled, create it using the schema in
.agents/skills/release-changelog/SKILL.md before creating child cases.WHATS NEXT and What's on my mind. Commits already
on origin/master after the beta source commit are prime "what's
next" material: they are literally the next release's content. Pull real
themes, not invented ones.discord_announcement document on the release issue (see
"Output" above). If updating, send the latest baseRevisionId.tweet_storm child case with parentCaseId set to the release
case id, then PUT its body document to the announcement body.Use this child case for the Discord/social announcement thread. The key must be stable so retries update the same child case:
POST /api/companies/:companyId/cases
{
"caseType": "tweet_storm",
"key": "paperclip-release:vYYYY.MDD.P:tweet-storm",
"title": "Paperclip vYYYY.MDD.P tweet storm",
"summary": "Social announcement thread for Paperclip vYYYY.MDD.P.",
"status": "in_review",
"parentCaseId": "<release-case-id>",
"fields": {
"schema_version": 1,
"version": "vYYYY.MDD.P",
"channel": "x",
"discord_source": true,
"post_count": 1,
"target_audience": ["operators", "contributors", "agent-company builders"],
"links": {
"release_notes": "https://github.com/paperclipai/paperclip/blob/master/releases/vYYYY.MDD.P.md",
"official_account": "https://x.com/papercliping"
},
"review": {
"needs_human_copy_paste": true,
"approved_by": null
}
}
}Then write the body document:
PUT /api/cases/:tweetStormCaseId/documents/body
{
"title": "Paperclip vYYYY.MDD.P tweet storm body",
"format": "markdown",
"body": "<announcement body>",
"changeSummary": "Draft social announcement"
}If updating an existing document, fetch the case and pass the latest
baseRevisionId.
Do not publish to Discord. This skill only prepares the artifact.
Three previous Discord announcements from dotta, included verbatim as the ground-truth examples for voice, structure, and emoji usage. When in doubt, match these.
CLIPPERS! v2026.403.0 has dropped!! :paperclip: :paperclip: :paperclip:
## Highlights
:inbox_tray: **Inbox overhaul** - there is a new "mine" tab that has mail-client like keyboard shortcuts. It's my new default view for managing work
:thumbsup: **Feedback and evals** - you can now vote :thumbsup: / :thumbsdown: on your agent's responses. If you choose to share your traces with me, I'll use it to make Paperclip better. In either case you can export locally for your own org's learning
:page_with_curl: **Document revisions** - you can now restore old versions of your documents
:ping_pong: **Telemetry** - this version has anonymized telemetry that helps me better understand the basic uses of Paperclip (adapters and so on) - if you hate that, just it disable with `DO_NOT_TRACK=1` or `PAPERCLIP_TELEMETRY_DISABLED=1` environment variables
:construction_worker: **Execution Workspaces (experimental)** - Paperclip is not a "code review" tool, but I have been finding worktrees are important for certain projects. Enable it in experimental settings
:loop: **Routine variables** - sometimes you need to customize a routine and the new variables feature makes that easy
PLUS **tons** of improvements aound adapters, bugfixes, qol
## COMMUNITY
HUGE THANKS to the contributors with commits in this release:
@aronprins, @bittoby, @edimuj, @HenkDz, @kevmok, @mvanhorn, @radiusred, @remdev, @statxc, @vanductai
## WHATS NEXT (ROADMAP)
* **Multi-human users** -- you've been asking for it, we have a draft and will have this shortly
* **Sandbox execution** - the other half of cloud deployment: run your agents in a sandbox across any provider
PLUS: just dealing with the excellent PRs we have sitting in our inbox.
**What's also on my mind (coming soonish)**
* MAXIMIZER MODE - for when you've got a dream and tokens to burn
* Artifacts, work products, and deployments
* CEO Chat
* Stronger agent defaults
## PRESS
I've been doing my part to spread the word about Paperclip
* We talked to the incredible [Andrew Warner of Mixergy Fame](https://x.com/dotta/status/2039087507514507407)
* We gave a tutorial with the [inimitable Greg Isenberg](https://x.com/dotta/status/2037279902445994345)
* We met with the [Seed Club guys](https://x.com/dotta/status/2039020365926576377)
* We crossed [40k stars (46k now!)](https://x.com/dotta/status/2038638188227387613)
* ... and a couple others that will be released in a few days
## SUCCESS STORIES
* [Nevo made $76k in march](https://x.com/dotta/status/2039406772859920758) after using Paperclip to automate his marketing
* [Lewis Jackson](https://x.com/WhatSayLew/status/2039810227394978158) said 34 agents were already operating his trading firm through Paperclip and called it his "holy s***" AI moment.
* [Neal Kotak](https://x.com/nkotak1/status/2039582439459209638) said Paperclip already runs most of Roominary for him and praised how strong the product is.
* [Sam Woods](https://x.com/samwoods/status/2039039305960587755) said he knows several people who moved from OpenClaw to Paperclip, often with Hermes in the stack, and that they love it.
* [Josh Galt](https://x.com/JoshGalt/status/2039386307219095557) called Paperclip the coolest agent tooling he has used and said it is finally something that just works.
## IN SUMMARY
I know there are still some rough edges, but
Paperclip will be *the* control plane for AI agents in **every** company.
and I think we're moving at a pretty good clip :paperclip: :paperclip: :paperclip:
FULL RELEASE NOTES HERE
https://github.com/paperclipai/paperclip/releases/tag/v2026.403.0
||@everyone||:paperclip: :paperclip: :paperclip: CLIPPERS!!! v2026.416.0 IS OUT :paperclip: :paperclip: :paperclip:
## Highlights
This release has *tons* of quality of life improvements around speed, performance, and workflow. You should notice that comment threads feel faster and your agents stay on task longer
:thread: Issue chat threads now are a conversation more than comments
:police_officer: Execution policies like **Reviewer** and **Approver** are now first-class in the harness (e.g. enforce that QA *must* review a task)
:no_smoking: Blocker dependencies - first-class "wake on blocker resolved" which means now you can have "task graphs" that depend on one another and it's enforced by Paperclip
:woman_feeding_baby: Parent-child tasks - better support for sub-tasks all around, which makes it much easier to organize your work
And then a million fixes around ux, details, keyboard shortcuts, bug fixes, security fixes, etc. Really you should read the [full release notes here](https://github.com/paperclipai/paperclip/releases/tag/v2026.416.0)
## COMMUNITY
INCREDIBLE INCREDIBLE WORK BY folks with commits and reports in this release:
@AllenHyang, @antonio-mello-ai, @aronprins, @chrisschwer, @cleanunicorn, @DanielSousa, @davison, @ergonaworks, @HearthCore, @HenkDz, @KhairulA, @kimnamu, @Lempkey, @marysomething99-prog, @mvanhorn, @officialasishkumar, @plind-dm, @shoaib050326, @sparkeros, @wbelt, @offset, @sagilayani, @mattdonnelly10, @peaktwilight, @YuvalElbar6
## WHATS NEXT (:motorway: Roadmap)
* **Multi-human users** - in the last stages of testing, Paperclip is better with teams
* **Memory Infrastructure** - your agents will remember everything about yoru business
* **Sandbox execution** - run your agents anywhere
## What's on my mind
* I want to meet with companies who are using Paperclip in their business - if that's you let me know
* We need more Paperclip tutorials, defaults, and education - thanks to @aronprins for his work in this area already!
* We still need to get better at reviewing your PRs and we're improving our process every day
* "Zero-human company" language has to go - we're the human control plane for ai labor
* We're adding better support for *knowledge (wikis & files)*, *artifacts*, and *work product* in Paperclip soon.
## PRESS
* **AI Engineer Europe Tutorial** - I gave a tutorial for AIE. If someone is looking for a basics ABC of Paperclip [you can send them this](https://x.com/dotta/status/2044575580264316931)
* **AI Club Chicago** - JB gave a talk on Paperclip [at AI Tinkerers in Chicago](https://x.com/developwithJB/status/2044281068778316268) !
## IN SUMMARY
PAPERCLIP WILL BE THE DEFAULT AGENT-MANAGEMENT TOOL FOR EVERY COMPANY
If there's anything I can do to help you and your company use Paperclip, hit me up. Until then, enjoy the new release
ITS TIME TO CLIP :paperclip: :paperclip: :paperclip:
FULL RELEASE NOTES
https://github.com/paperclipai/paperclip/releases/tag/v2026.416.0
||@everyone||:paperclip: :paperclip: :paperclip: CLIPPERS!!! v2026.427.0 IS OUT :paperclip: :paperclip: :paperclip:
THIS IS THE OFFICIAL TWITTER FOLLOW IT: https://x.com/papercliping
## Highlights
:man_feeding_baby: **MULTI USER** - you can now invite multiple users to your instance
:factory_worker: **HARDER WORKING** - robosut liveness continuations and lifecycle recovery means your instance tries harder before involving you
:white_check_mark: **SUBISSUE CHECKLISTS** - subissues have better ordering which allows for long-run planning
:thread: **Rich Thread UX** - now your agents can ask you questions, ask for approvals, suggest tasks and you can approve or refine them right in your task threads
:cloud: **BETA: Sandbox Providers** - Cloud sandboxing is in beta - the API ships in this release and we'll be adding more providers
... and *tons* of other improvements and bugfixes.
## Community
Thank you to everyone who contributed to this release!
@akhater, @aronprins, @GodsBoy, @LeonSGP43, @neerazz, @NoronhaH, @rbarinov, @rvanduiven, @SgtPooki, @superbiche
## WHATS NEXT (:motorway: Roadmap)
* **Longer-range planning and execution** - Paperclip will support longer and longer tasks and work until it's done
* **Secrets Service v2** - an important prereq for Paperclip cloud
* **Artifacts, memory, and knowledge**
* **Conference Room** aka CEO/Agent Chat
## What's on my mind
* **Documentation & Blog posts** - I've fallen behind on the docs but aron has done a good job here - we'll be setting up Clips to help maintain these
* **Paperclip Cloud** - will be a critical unlock for us, but even the shared team story needs developed more - *where should the work be done* and *where are the outputs stored* and *how do we surface them to users*? Each of these questions are a core Paperclip service that needs developed
* **Paperclip Bench** - In the vein of SWE-Bench I've started an internal benchmark for Paperclip - we have to be able to measure that our changes are improving the system and not regressing
* **Paperclip Connections Store** - connecting to Github, Slack, Google Docs, and the hundreds of other services we use every day should be easy, secure, and configurable per agent and team
## Press
I met with the [Wisemen about Paperclip](https://x.com/dotta/status/2045146539534827998)
## WHAT I NEED FROM YOU
FOLLOW THIS TWITTER ACCOUNT: https://x.com/papercliping - that's the only official one, report any others
## 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/v2026.427.0.md
||@everyone||Before handing off:
releases/vYYYY.MDD.P.md exactly.WHATS NEXT and What's on my mind are pulled from real recent issues /
active goals — not invented themes.ITS TIME TO CLIP :paperclip: :paperclip: :paperclip:
and ||@everyone|| is the very last line.discord_announcement is updated on the release issue, and the
announcement is also posted in a comment inside a fenced code block.This skill never posts to Discord. It only prepares the announcement artifact.
© paperclipai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/release-changelog-discord-message of paperclipai/paperclip.
Open the folder on GitHubat commit de9ab8e
Release Changelog Discord Message next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release Changelog Discord Message this skillpaperclipai/paperclip | 100k | — | ~5.4k | Automated safety check: Pass | MIT | |
| Releasepwrdrvr/openclaw-codex-app-server | 265 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Writing Release NotesGoneTone/genshin-impact-wish-gacha-analyzer | 152 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Maintain DisCatSharpAiko-IT-Systems/DisCatSharp | 140 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Release Discord Postnevalang/neva | 1.1k | — | ~500 | Automated safety check: Pass | MIT | |
| Subwave Discord Releaseperminder-klair/subwave | 1.4k | — | ~2.3k | Automated safety check: Pass | MIT |
pwrdrvr/openclaw-codex-app-server
Plan and publish a GitHub Release in a tag-driven repository.
GoneTone/genshin-impact-wish-gacha-analyzer
A skill your agent uses when drafting GitHub release notes or changelog content for this project (Genshin Impact Wish Gacha Analyzer).
Aiko-IT-Systems/DisCatSharp
Guides changes to the DisCatSharp C# Discord library: tracing a payload field through parsing, serialization and caches, then validating across target frameworks.
nevalang/neva
Create a Discord-ready Neva release announcement from a GitHub release payload.
perminder-klair/subwave
Draft a Discord release announcement for SUB/WAVE from a release PR, tag, or version number.
Gremlinq/ExRam.Gremlinq
A skill your agent uses to write the release notes and the announcement texts for an upcoming release, from the pull requests merged since the previous tag.
paperclipai/paperclip
Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.
paperclipai/paperclip
Interact with the Paperclip control plane API for task coordination and governance.
paperclipai/paperclip
A skill your agent uses for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and…
paperclipai/paperclip
Paperclip UI design system guide for building consistent, reusable frontend components.
paperclipai/paperclip
Publish static HTML pages and asset folders to the Paperclip S3/CloudFront page host.
paperclipai/paperclip
Create new agents in Paperclip with governance-aware hiring.
Works with
Categories
Write the Discord announcement for a stable Paperclip release from the release changelog. Release Changelog Discord Message is an agent skill from paperclipai/paperclip. Write the Discord announcement for a stable Paperclip release from the release changelog.
Release Changelog Discord Message fits situations like: A release issue needs a copy-pasteable dotta-voice Discord post; refreshed discordannouncement document.
Run `npx skills add paperclipai/paperclip --skill release-changelog-discord-message -a claude-code`. Or copy the skill folder (.agents/skills/release-changelog-discord-message in paperclipai/paperclip) into .claude/skills/release-changelog-discord-message in your project. Claude Code loads it when a task matches its description.
Run `npx skills add paperclipai/paperclip --skill release-changelog-discord-message -a codex`. Or copy the skill folder (.agents/skills/release-changelog-discord-message in paperclipai/paperclip) into .agents/skills/release-changelog-discord-message in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add paperclipai/paperclip --skill release-changelog-discord-message -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-changelog-discord-message, .gemini/skills/release-changelog-discord-message, .github/skills/release-changelog-discord-message and .opencode/skills/release-changelog-discord-message in your project.
Going by SKILL.md and its folder, Release Changelog Discord Message needs the command-line tools its instructions call (npx). Our summary lists: Node.js; Docker.
SKILL.md names 1 domain. In commands or code: x.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Release Changelog Discord Message is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.4k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Release Changelog Discord Message: Release (pwrdrvr/openclaw-codex-app-server, 265 stars), Writing Release Notes (GoneTone/genshin-impact-wish-gacha-analyzer, 152 stars), Maintain DisCatSharp (Aiko-IT-Systems/DisCatSharp, 140 stars) and Release Discord Post (nevalang/neva, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
paperclipai (a GitHub organization) maintains it in paperclipai/paperclip, which has 99,905 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on October 11, 2026.
Source: paperclipai/paperclip on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.