How do I install the Release skill?

Run npx skillmds@latest add rivet-dev/release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Release skill do?

Cut an AgentOS release via the scripts/publish flow. Use when the user asks to release, publish, cut a release, or bump the AgentOS version. It is listed under Coding & Dev Tools on SkillMD.

Is Release safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release?

rivet-dev (@rivet-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release by rivet-dev — Agent Skill

Name: Release
Author: rivet-dev

File contents

AgentOS Release

The publish flow lives in scripts/publish and is driven by .github/workflows/publish.yaml.

AgentOS is the source of truth. It publishes npm packages, crates, runtime sidecars, Pyodide/R2 assets, and @agentos-software/* registry packages from this repository. agentos releases are generated compatibility shims that follow the AgentOS version; never release agentos first.

Procedure

Start from a clean, pushed merge-aos or main bookmark.
Run the local trigger:

just release --version 0.2.0       # exact version
just release --version 0.2.0-rc.1  # rc (npm tag `rc`)
just release --patch               # semver bump from latest git tag

Watch the workflow:

run=$(gh run list -R rivet-dev/agentos --workflow=publish.yaml -L1 --json databaseId --jq '.[0].databaseId')
gh run watch -R rivet-dev/agentos "$run" --exit-status

Notes

Never publish to npm or crates.io locally; always go through publish.yaml.
scripts/publish/src/local/cut-release.ts is a pure trigger; version changes happen in the ephemeral CI checkout.
workspace:* deps are rewritten to literal versions by the publish bump pass.
Generated agentos shims are dispatched after AgentOS publishes and must use the same version.
If anything fails, stop and report — do not retry automatically.

Frequently asked questions

Release