$ loading_
Prepare and verify OpenClaw stable or beta releases and release notes.
The material indicates a prompt-only release-maintainer skill for an open-source community project, with no declared secrets, remote endpoints, or local execution interface, making overall risk low. Its workflow semantics touch release operations and possible private release docs, but the provided material shows no concrete high-risk red flags.
The material explicitly states that no keys or environment variables are required. Although the README mentions loading "$release-private" if present and resolving private credential locators, the skill itself does not declare any mechanism to collect, store, or exfiltrate credentials.
Neither the objective checks nor the material declare any remote endpoints. The content is primarily release-process guidance, with no stated behavior of sending user data to third parties or unrelated hosts.
The system marks it as prompt-only. The README describes release guardrails and operational constraints, not a tool interface that directly spawns processes, runs scripts, or invokes system capabilities on the host.
No capability is declared to read or write local files, non-repository data, or system resources. While the documentation mentions checking specific source paths and possibly consulting private docs, that is workflow guidance rather than standalone data-access permission.
The source is an open-source GitHub repository with very high community adoption (about 377k stars), providing strong auditability and source credibility. License and maintenance status are not explicit, which is a minor uncertainty but not enough to raise the risk level.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "release-openclaw-maintainer" skill from askskill: 1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/release-openclaw-maintainer/SKILL.md 2. Save it as ~/.claude/skills/release-openclaw-maintainer/SKILL.md 3. Reload skills and tell me it's ready
Create a stable release checklist for OpenClaw v1.4.0, including version checks, changelog preparation, release notes, artifact verification, publish commands, and rollback checks.
A structured stable release checklist covering key pre-, during-, and post-release steps and verification items.
Review this draft of OpenClaw 1.5.0-beta1 release notes. Check whether it clearly explains new features, known issues, and upgrade notes, and point out missing content and improvements.
A release notes review listing issues, risk points, and ready-to-use revision suggestions.
Based on OpenClaw's release workflow, produce sample commands from tagging to artifact upload, and include verification steps for packages, checksums, versions, and file integrity.
A usable set of publish command examples with matching artifact verification instructions and check order.
Use this skill for release and publish-time workflow. Load $release-private if it exists before resolving Peter-owned credential locators or private host topology. Keep ordinary development changes and GHSA-specific advisory work outside this skill.
docs/reference/RELEASING.md for public policy.openclaw publish is manual workflow_dispatch; creating or pushing a tag does not publish by itself.main, not directly on
main. Use release/YYYY.M.D for the branch name.main and confirm current main CI is
green. Then branch from that commit so regular development can continue on
main while release validation runs.CHANGELOG.md on main from merged PRs and all
direct commits since the last reachable release tag. Commit/push/pull that
changelog rewrite immediately before creating the release branch.src/plugins/compat/registry.ts and
src/commands/doctor/shared/deprecation-compat.ts before branching and again
before final publish. For every deprecated or removal-pending compatibility
record whose removeAfter date is on or before the release date, either
remove the compatibility path where safe and validate the affected tests, or
write down why removal is blocked and get explicit maintainer approval before
shipping the expired compatibility path.src/commands/doctor/shared/deprecation-compat.ts until maintainers confirm
the repair is no longer needed.-beta.N, delete/recreate or force-move the git tag
and prerelease to the fixed commit, and rerun preflight. Do not increment to
the next beta number until the matching npm package has actually published.
If a published beta needs a fix, commit the fix on the release branch and
increment to the next -beta.N.main, move the unpublished beta tag/prerelease to
the fixed commit, and rerun the affected pre-publish gates. If anything fails
after npm publish, fix it, forward-port to main, increment beta number, and
repeat. After each beta publish, run the published-package roster focused on
install/update/Docker/Parallels/NPM Telegram. For later beta attempts, rerun…
Fetch GitHub issues, create fixes, open PRs, and handle reviews.
Convert text to speech locally and offline with sherpa-onnx, no cloud needed.
Regenerate OpenClaw release changelog sections from Git history before releases.
Automate web page workflows, login checks, tab handling, and recovery steps.
Manage issues, PRs, logs, releases, and repos with GitHub CLI.
Verify an OpenClaw release is fully published and working across all channels.
Draft OpenClaw release announcements and testing guidance from release evidence.
Run, debug, monitor, and summarize OpenClaw release CI workflows.
Run or recover OpenClaw macOS signing, notarization, and release promotion.
Automate OpenClaw nightly releases, branch maintenance, and forward-porting to main.
Review, triage, and manage OpenClaw issues and pull requests faster.
Refactor OpenClaw docs pages with source-checked preservation, clearer structure, and verification.