Agent skill · operations · paperclipai
release
Coordinate a full Paperclip release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss versioning.
Why this skill is useful
Adds a detailed, executable release workflow with specific commands and procedures for managing Paperclip releases that the AI wouldn't reliably generate on its own.
What it needs
Requires docker, pnpm installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 75,771 stars on the source repository.
What this skill does
Release Coordination Skill Run the full Paperclip maintainer release workflow, not just an npm publish. This skill coordinates: stable changelog drafting via release-changelog canary verification and publish status from master Docker smoke testing via scripts/docker-onboard-smoke.sh manual stable promotion from a chosen source ref GitHub Release creation website / announcement follow-up tasks release-content Cases dogfood: a top-level release case with child blogpost and tweetstorm cases, all linked to the release issue/run Trigger Use this skill when leadership asks for: "do a release" "ship the release" "promote this canary to stable" "cut the stable release" Preconditions Before proceeding, verify all of the following: 1. .agents/skills/release-changelog/SKILL.md exists and is usable. 2. The repo working tree is clean, including untracked files. 3. There is at least one canary or candidate commit since the last stable tag. 4. The candidate SHA has passed the verification gate or is about to. 5. If manifests changed, the CI-owned pnpm-lock.yaml refresh is already merged on master. 6. npm publish rights are available through GitHub trusted publishing, or through local npm auth for emergency/manual use. 7. If running through Paperclip, you have issue context for status updates and follow-up task creation. If any precondition fails, stop and report the blocker. Inputs Collect these inputs up front: whether the target is a canary check or a stable promotion the candidate sourceref for stable whether the stable run is dry-run or live release issue / company context for website and announcement follow-up Step 0 — Release Model Paperclip now uses a commit-driven release model: 1. every push to master publishes a canary automatically 2. canaries use YYYY.MDD.P-canary.N 3. stable releases use YYYY.MDD.P 4. the middle slot is MDD, where M is the UTC month and DD is the zero-padded UTC day 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills paperclipai/release