$ loading_
Draft OpenClaw release announcements and testing guidance from release evidence.
Overall this is a prompt-only skill with no required secrets, no declared remote endpoints, and no described local code execution or file access, so the risk is low. The main caution is that it drafts announcements from external release evidence, so unverified claims could be propagated into public posts.
No keys, tokens, or environment variables are required, and there is no evidence of credential collection or forwarding, so credential risk is very low.
No remote endpoint hosts are declared, and there is no described exfiltration of user data; it only references reading GitHub release notes, changelogs, and registry metadata as evidence sources.
Objective checks mark it as prompt-only, with no indication of spawning processes, running scripts, or invoking system capabilities, so there is no code-execution exposure.
It reads release notes, CHANGELOGs, commit history, and validation evidence to draft announcements, which is normal document/metadata access; no overbroad local file or sensitive data access is indicated.
The source is a GitHub open-source repository with very high community adoption (377k+ stars), which supports auditability and trust; however, the license is unspecified and maintenance status is unknown, so supply-chain sustainability still warrants attention.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "release-openclaw-announcement" skill from askskill: 1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/release-openclaw-announcement/SKILL.md 2. Save it as ~/.claude/skills/release-openclaw-announcement/SKILL.md 3. Reload skills and tell me it's ready
Draft a Discord announcement for an OpenClaw beta release using the changelog, GitHub release, registry version, and validation results. Highlight new features, known risks, upgrade steps, and what users should test most. Keep the tone clear, friendly, and concise.
A clear beta release announcement with version details, highlights, cautions, and testing requests.
Using the OpenClaw stable release changelog, GitHub release link, registry status, and validation evidence, write a Discord announcement for the stable release. Emphasize production readiness, key fixes, upgrade notes, and how users should report issues.
A community-facing stable release announcement highlighting readiness, key fixes, and feedback channels.
OpenClaw has just released an RC build. Based on the changelog, fixed issues, validation results, and high-risk changes, create a Discord-ready checklist of what users should test first. Group items by priority and explain what each test is meant to validate.
A prioritized post-release testing checklist that helps the community validate the release quickly.
Use with release-openclaw-maintainer after a beta or stable release is live.
Use with openclaw-discord when actually posting to Discord.
Before drafting focus areas, read real release evidence:
CHANGELOG.md section for the released base version.Do not claim a full changelog audit unless you did it. If you only read the generated release notes or top changelog section, say that and either audit properly or draft with that limitation.
For beta focus areas, prioritize user-observable changes over internal test or CI mechanics:
Do not let late release-branch fixes automatically dominate the announcement. If the version includes a large delta from the previous shipped version, rank focus areas by the whole release delta and expected user impact; mention late fixes in their natural category.
Every beta announcement must make beta status explicit and include:
OpenClaw 2026.5.25-beta.1openclaw update --channel beta --yes
openclaw --version
Install from https://openclaw.aiDo not suggest npm install commands in beta announcements unless the operator explicitly asks for npm-specific copy or troubleshooting text. It is fine to use registry metadata as evidence; do not turn that into public install guidance.
For stable announcements, use the stable channel wording:
openclaw update --channel stable --yes
openclaw --version
Fresh installs still point to https://openclaw.ai.
When asked to post, use the configured Discord workflow from
openclaw-discord or the approved OpenClaw relay. Never print tokens.
For public channels, inspect the final body before sending.
Verify an OpenClaw release is fully published and working across all channels.
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.
Prepare and verify OpenClaw stable or beta releases and release notes.
Create and review technical docs and agent instruction files in repositories.
Run, debug, monitor, and summarize OpenClaw release CI workflows.
Run or recover OpenClaw macOS signing, notarization, and release promotion.
Refactor OpenClaw docs pages with source-checked preservation, clearer structure, and verification.
Automate OpenClaw nightly releases, branch maintenance, and forward-porting to main.
Choose and run the safest, cheapest OpenClaw test and validation path.
Plan and run end-to-end pre-release validation for OpenClaw plugins.