mcpbeat

Publish Registry

rivet-dev/publish-registry

Publish @agentos-software/* registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.

249 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 publish-registry

The instruction itself

3 sections, as written by the author

Publish AgentOS Registry Packages

Registry packages live in agentos/registry and publish as

@agentos-software/*. They version independently per package.

Procedure

  • Build native command artifacts and package tarballs:
just registry-native
just registry-build [pkg]
just registry-status --remote
  • Bump the package's own package.json version and commit it.
  • Publish from AgentOS:
just registry-publish <pkg>         # dist-tag dev
just registry-publish <pkg> latest  # deliberate latest release
just registry-publish-all [tag]

Rules

  • Do not publish registry packages from agentos.
  • Do not move latest unless the user explicitly asks for a release.
  • Prefer AgentOS workspace builds while iterating; published pins are for

consumers and release validation.

How to use it

Copy the folder

Take rivet-dev/publish-registry 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.