mcpbeat

Release Preview

rivet-dev/release-preview

Cut an AgentOS release-preview. Use when the user asks for a preview, release-preview, or a branch dist-tag build.

291 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
4293
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/rivet-dev/agentos --skill release-preview

The instruction itself

3 sections, as written by the author

AgentOS Release Preview

AgentOS previews are branch snapshots from this repository. The workflow builds

debug artifacts and publishes npm packages under a sanitized branch dist-tag.

No crates.io release, git tag, or GitHub release is created.

agentos is a generated mirror. Do not bump a agentos ref or cut a

agentos preview by hand.

Procedure

  • Push the AgentOS branch.
  • Dispatch and watch:
just release-preview <agentos-branch>
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
  • Install a preview with:
npm install @rivet-dev/agentos-core@<sanitized-branch>

Rules

  • Release-preview is for previews only; releases use the release skill.
  • All code changes belong in AgentOS. The agentos mirror is regenerated

from AgentOS and follows the published AgentOS version.

  • On failure: gh run view <run> --log-failed, fix, re-dispatch, re-watch.

How to use it

Copy the folder

Take rivet-dev/release-preview from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npm. Without those the skill loads but fails at the first command.