skillboardUpdated every 6 hours
skillboardVerify regular or extended-stable OpenClaw releases against the exact publication surfaces, workflow identities, package provenance, smoke tests, and live Gateway behavior expected for that release track.
b1e27dbVerify 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 before changing release state. Rules Resolve short suffixes like to the concrete CalVer version from the current date/context, then say the resolved version. Resolve the track first. Regular beta/stable uses a GitHub Release and the platform graph; extended stable uses its canonical branch, npm selector, and…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/verify-release · pinned to the source commit
git clone https://github.com/openclaw/openclaw.git
cd openclaw
git checkout b1e27db51ce36bc26669f6a00d7990908a481ff6
mkdir -p ".claude/skills/verify-release"
cp -r ".agents/skills/verify-release" ".claude/skills/verify-release"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit b1e27db51ce3. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References credentials, tokens or secret files that a skill should not need.
Evidence: [redacted]· fingerprint ccae6d912a41bfef