Agent skill · software engineering · steipete
verify-release
Verify regular or extended-stable OpenClaw releases against the exact publication surfaces, workflow identities, package provenance, and published CLI smoke tests expected for that release track.
Why this skill is useful
Adds a comprehensive verification script for OpenClaw releases that includes specific commands and checks not commonly found in public documentation.
What it needs
Requires gh, npm, openclaw installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 385,400 stars on the source repository.
What this skill does
Verify Release Use this when asked whether an OpenClaw release is fully released, published, promoted, smoke-tested, or live-verified. This is a verification skill, not a publish skill; use $release-openclaw-maintainer before changing release state. Rules Resolve short suffixes like .27 to the concrete CalVer version from the current date/context, then say the resolved version. Resolve the track first. Both tracks use the shared GitHub Release evidence ledger. Regular beta/stable also uses the platform graph; extended-stable uses its canonical branch, npm selector, and Gateway surfaces. Do not require one track's native or ClawHub artifacts from the other. Verify live state. Do not trust local checkout state, release notes, or old memory as current truth. If the checkout is dirty or divergent, use it only for scripts/reference. For version metadata, fetch from GitHub release/tag or unpack the tag tarball under /tmp. Never print secrets. Keep the final terse: yes/no, evidence bullets, caveats, cleanup. Regular beta/stable checks Use these checks only for the regular orchestrated release track. 1. GitHub release: gh release view v<VERSION> --repo openclaw/openclaw --json tagName,name,publishedAt,isDraft,isPrerelease,targetCommitish,url,body,assets Confirm stable releases are not draft/prerelease. Confirm release body has npm, CI, plugin npm, ClawHub, mac/appcast evidence links when expected. Confirm assets expected for stable mac releases are uploaded: zip, dmg, dSYM, dependency evidence, immutable full-validation manifest, postpublish evidence, and stable-main closeout manifest. Download each immutable evidence asset and its .sha256 companion, then verify the checksum before trusting the release record. 2. Root npm: npm view openclaw@<VERSION> version dist-tags.latest dist.tarball dist.integrity time.<VERSION> --json latest must equal <VERSION> for stable. Record tarball, integrity, publish time. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/verify-release