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.
79%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/verify-release/SKILL.mdUse 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.
.27 to the concrete CalVer version from the
current date/context, then say the resolved version./tmp.yes/no, evidence bullets, caveats, cleanup.Use these checks only for the regular orchestrated release track.
gh release view v<VERSION> --repo openclaw/openclaw --json tagName,name,publishedAt,isDraft,isPrerelease,targetCommitish,url,body,assets.sha256 companion, then
verify the checksum before trusting the release record.npm view openclaw@<VERSION> version dist-tags.latest dist.tarball dist.integrity time.<VERSION> --jsonlatest must equal <VERSION> for stable.npmRegistrySignaturesVerified: true and
npmProvenanceAttestationMatched: true.https://api.github.com/repos/openclaw/openclaw/tarball/v<VERSION>
into /tmp/openclaw-v<VERSION>-src.openclaw.build.bundledDist === true
explicitly defers external publication even when publish flags are set.
Record deferred package names and reasons separately.gh api repos/openclaw/openclaw/actions/runs/<RUN>/jobs --paginate.<VERSION> and
dist-tags.latest === <VERSION>.openclaw plugins search <known-plugin> --json.openclaw plugins install clawhub:@openclaw/matrix@<VERSION>.
Prefer matrix unless that plugin is not in the expected set. ClawHub
versions belong in the spec; --pin is only supported for npm installs.OpenClaw Stable Main Closeout succeeded and its
manifest records the matching release tag, current rollback drill, stable
soak, and blocking performance evidence.Extended-stable has a GitHub Release with shared release evidence but no native or ClawHub artifacts. Verify it alongside the live tag, workflow, registry, provenance, and image state.
v<VERSION> at patch 33+, with no suffix,
contained in extended-stable/YYYY.M.33. Only an active candidate must equal
the tip. Root and every publishable official plugin must declare <VERSION>.
Require the Git tag and a public, non-prerelease GitHub Release whose title
and canonical body match the tag. Require isLatest=false, the dependency
evidence, immutable Full Release Validation manifest, postpublish evidence,
and their checksums. Require no native or ClawHub assets.release-publish/* parent and canonical release-ci/*
validation producer with verified workflow SHA provenance. Validation must
use rerun_group=all, release_profile=stable, blocking soak/performance,
and the saved attempt. Core publish must reference all three run IDs and bind
its manifest, workflow ref, and tarball digest to the release SHA.extended-stable selectors to return
<VERSION> for root, every preflight corePackageTarballs entry, and every
publishToNpm === true official plugin derived from the tag. Compare the
plugin plan, jobs, and complete readback; never infer inventory from diffs.node --import tsx scripts/openclaw-npm-postpublish-verify.ts <VERSION>.
Require signatures, canonical-branch provenance, and publish/preflight
digest binding to the release SHA. Preserve output and workflow URLs.extended-stable* aliases may
resolve to those digests. Require the successful OpenClaw Release Publish
parent run and its completed Docker verification. The normal route finalizes
afterward; an explicitly requested fast path may activate GitHub first. Repair
aliases through current-main Docker Channel Promotion for the exact tag,
without rebuilding.promote_extended_stable in the
openclaw/releases dist-tag workflow for the root selector (an unsuffixed
final patch 33+) and approved credential-isolated tooling for others, then repeat
complete readback. Do not require ClawHub, native/mobile apps, website,
private dist-tags, or regular latest. Require shared release evidence, but
do not require regular native or ClawHub assets.After the track-specific publication checks pass, use a disposable installation/cache with isolated OpenClaw state:
npm exec --yes --package openclaw@<VERSION> -- openclaw --version.plugins --help or gateway --help.Do not start an extra local Gateway or run an ad hoc live model turn as a preliminary release check. Use the canonical release-validation workflows and publication evidence above; this does not remove any of their required lanes. Run additional manual live checks only when explicitly requested.
latest is release truth; if optional beta mirrors
still point at a beta version, report it as a caveat, not a stable-release
blocker, unless the user asked to verify beta promotion.openclaw/openclaw
092d800
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.