release-publishinglisted

# Publish Meteor agent skills Prepare one catalog version for Codex, Claude Code, GitHub release assets, and direct skill installation. Read [`RELEASING.md`](../../../RELEASING.md) before changing release state. ## Choose the release stage | Stage | Repository visibility | Version and tag | Purpose | |---|---|---|---| | Working-tree test | Private or public | No new tag required | Validate local manifests and behavior. | | Public beta | Public | `X.Y.Z-beta.N` and `vX.Y.Z-beta.N` | Test the exact remote installation path. | | Stable | Public | `X.Y.Z` and `vX.Y.Z` | Publish the accepted catalog and submit it to directories. | A GitHub repository does not need to be public for local working-tree tests. It must be public before testing installation through `meteor/agent-skills@<tag>` or submitting to public directories. Catalog releases may be published independently for skill additions, corrections, evaluation improvements, packaging changes, or other catalog maintenance. For an independent release, follow the normal beta or stable flow without requiring a Meteor release audit, compatibility mapping, or Meteor artifact gates. Apply the coordinated rules below only when the catalog is intentionally paired with a Meteor release. ## Coordinate with a Meteor release When Meteor's release process requests a paired catalog, record the Meteor version, release commit, Agent Skills audit report, audited Agent Skills revision, publish commit, and exact catalog tag. Catalog semver