skills.rest
steipete
steipeteCOMMUNITY
Explore all skills by this author →
Website𝕏@steipeteGitHub

verify-release

Verify OpenClaw release publication, provenance, and live Gateway behavior against track-specific surfaces.

388k|81.5k|Updated Nov 24, 2025
Search Tags:#release verification#Openclaw#GitHub Releases#gateway smoke test#npm provenance#clawhub plugins#docker digests
One-click install
npx skills add https://github.com/steipete/clawdis --skill verify-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-release
Source: https://github.com/steipete/clawdis/tree/main/.agents/skills/verify-release
Command: npx skills add https://github.com/steipete/clawdis --skill verify-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release verification for OpenClaw requires checking multiple publication surfaces (GitHub Releases, npm registry, ClawHub, Docker images, workflow runs) and confirming live Gateway behavior. Without a structured verification process, teams risk declaring a release complete when artifacts are missing, provenance is unverified, or the published package fails smoke tests.

Core Features & Use Cases

  • Track-aware verification: Resolves the release track (regular beta/stable vs. extended-stable) and applies the correct checks for each, avoiding false failures from cross-track artifact mismatches.
  • Publication surface checks: Verifies GitHub Release state, npm registry versions and dist-tags, ClawHub plugin publication, Docker image digests, and workflow run conclusions.
  • Provenance and integrity validation: Confirms npm registry signatures, provenance attestation, SHA256 checksums on immutable evidence assets, and digest binding to the release SHA.
  • Live Gateway smoke testing: Runs the published CLI in an isolated environment and executes a Gateway-backed agent turn with a known-available model to confirm runtime behavior.
  • Use Case: A maintainer needs to confirm whether OpenClaw v2025.11.27 is fully released. Use this skill to verify the GitHub Release is published (not draft), root npm latest matches, all expected plugins are published to npm and ClawHub, the stable main closeout workflow succeeded, and a live Gateway smoke test passes.

Quick Start

Verify whether OpenClaw release v2025.11.27 is fully published, smoke-tested, and live-verified by checking all track-specific publication surfaces and running the shared Gateway smoke test.

Frequently Asked Questions about verify-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify an OpenClaw release is fully published?▼

Check the GitHub Release state with `gh release view`, confirm root npm `latest` matches the version, verify all expected plugins are published to npm and ClawHub, and confirm relevant workflow runs succeeded. For extended-stable, verify the canonical branch tag and Docker image digests instead.

What is the difference between regular and extended-stable release verification?▼

Regular beta/stable uses a GitHub Release and the platform graph with assets like zip, dmg, and dSYM. Extended-stable has no GitHub Release ledger and instead verifies the canonical branch tag, npm `extended-stable` selector, Docker images, and provenance binding to the release SHA.

Does the verify-release skill run live Gateway smoke tests?▼

Yes, after track-specific publication checks pass, it runs the published CLI in an isolated HOME and executes a Gateway-backed agent turn with inherited API keys, a short prompt, and a known-available model. It distinguishes Gateway-backed success from local embedded fallback.

Why would a release verification fail despite all workflows succeeding?▼

Verification can fail if npm registry signatures are not verified, provenance attestation does not match, SHA256 checksums on evidence assets do not match, or the live Gateway smoke test cannot reach a known-available model. A divergent local checkout is also flagged as a caveat requiring live source verification.

Can I use verify-release to publish or promote a release?▼

No, this is a verification skill only. It does not change release state. Use the release maintainer skill before publishing or promoting, then return to verify-release to confirm the publication surfaces and live behavior.

Related Skills

Explore More Software Engineering Skills→
mifunedevmifunedev
28

release

Automate CalVer release workflows with version computation, pre-flight checks, and artifact publishing.

Official
Advanced
cpowe-ADTcpowe-ADT

adinsights-release-readiness

Aggregate router, scope, contract, and runbook evidence to compute release gate outcomes.

Community
Advanced
connectedxmconnectedxm

ship-to-prod

Open a formatted release pull request into main with Linear references.

Official
Advanced
elbrunoelbruno
2

ci-validation-gates

Enforce CI/CD gates validating semver, NPM_TOKEN, and release events.

Community
Advanced