Agent skill · operations · steipete
release-openclaw-maintainer
Manage one OpenClaw release or orchestrate release owners across beta, stable, and extended-stable: preparation, fix-inclusion tracing, hotfix routing, publication, handoff, and closeout.
Why this skill is useful
Provides detailed workflows and specific procedures for managing OpenClaw releases that the AI wouldn't reliably generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-08-07. 385,400 stars on the source repository.
What this skill does
OpenClaw Release Maintainer Use for a release operation, not ordinary development or advisory mutation. Read docs/reference/RELEASING.md for current policy. Load $release-private when available before resolving private credential locators or host topology; credential operations use $one-password. Choose the role Release owner (default): “Manage this release” owns one release from preparation through verification, retrospective, and closeout. Start with the owner lifecycle, even for a short prompt. Release manager / orchestrator: coordinate several release owners, draft their kickoff or handoff briefs, and route hotfix opportunities. Start with manager mode. This role does not become a second writer of an owner's release branch or publication state. The skill owns the general process; the initial prompt carries release-specific intent, authority, and state, not a copied runbook. A handoff resumes that intent with current evidence rather than starting another release. Choose the operation Read only the references needed for the selected phase: Regular beta/stable preparation or publication: regular release, which routes preparation and phase-specific proof. If the request does not specify stable/full, default to beta; beta authorization does not authorize later stable promotion. Fix status, candidate inclusion, first published version, or cumulative upstream-fix counts: fix-inclusion tracing. Backport discovery and porting: candidate inventory and worker brief. For extended-stable also read backport preparation; SDK/config changes need a visible maintenance-risk warning and maintainer decision. Extended-stable .33+ Gateway publication: extended-stable publication. Use the shared publisher with extended-stable inputs; its non-Latest GitHub Release carries evidence without native-app or ClawHub publication. Validation selection or failed proof: validation and confidence, with $release-openclaw-ci for workflow execution and immutable manifests. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/release-openclaw-maintainer