Release Openclaw Announcement
Draft or post OpenClaw beta, stable, or extended-stable Discord release announcements from changelog, tag, registry, and validation evidence. Use when announcing a release, release candidate, or asking what users should test after an OpenClaw release.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Release Openclaw Announcement when an AI agent needs a reusable SKILL.md workflow for this job: Draft or post OpenClaw beta, stable, or extended-stable Discord release announcements from changelog, tag, registry, and validation evidence. Use when announcing a release, release candidate, or asking what users should test after an OpenClaw release.
When not to use it
Skip Release Openclaw Announcement when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/release-openclaw-announcement # Save SKILL.md to ~/.claude/skills/release-openclaw-announcement/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/release-openclaw-announcement/SKILL.md. For a shared project, commit the folder at .claude/skills/release-openclaw-announcement/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Release Openclaw Announcement skill for this task: Use Release Openclaw Announcement when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# OpenClaw Release Announcement
Use with `release-openclaw-maintainer` after a release is live. Use with `$discord-user-post` when actually posting to Discord as the logged-in user.
## Evidence First
Before drafting focus areas, read real release evidence:
1. GitHub release body and immutable tag; for extended-stable, also confirm the npm/container-only scope and non-Latest classification. 2. The released base version's `CHANGELOG/<version>.md` and contribution record, resolved with `node scripts/release-changelog.mjs read --version <version> [--ref <sha-or-tag>]` (add `--record` for accounting). The shared resolver reads historical monolithic tags; current `CHANGELOG.md` is an index. After approved docs publication, read the complete docs mirror and frozen record rather than treating the compact GitHub body as full notes. 3. Commits since the previous shipped version or the operator-specified base. 4. Registry/package metadata for the exact version and current dist-tag. 5. Validation status that is relevant to user confidence.
Do not claim a full changelog audit unless you did it. If you only read the generated release notes or selected 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:
- install/update paths - OS/platform-specific behavior - Gateway startup/restart, config, and runtime behavior - provider/model/runtime routing - plugin loading and local plugin development - channels and media paths - security/data-loss/user-impact fixes
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.
## Required Copy
Every beta announcement must make beta status explicit and include:
- exact version, e.g. `OpenClaw 2026.5.25-beta.1` - one-sentence risk framing: beta, useful for testing, not stable promotion - focused test areas derived from evidence, not guesswork - update command promoted near the top: ```sh openclaw update --channel beta --yes openclaw --version ``` - fresh install path: `Install from https://openclaw.ai` - GitHub release link - concise validation note, without making CI the headline
Do 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:
```sh openclaw update --channel stable --yes openclaw --version ```
Fresh installs still point to `https://openclaw.ai`.
For extended-stable, name the exact version and trailing month. Mention only observable backports, and use:
```sh openclaw update --channel extended-stable openclaw --version ```
Do not add `--yes`: users moving from newer regular stable must see the downgrade warning because older versions may not understand newer configuration. Link the GitHub Release, but do not inherit regular stable macOS, Windows, ClawHub, `latest`, or website claims.
## Style
- Discord Markdown, no tables. - Keep it skimmable: short intro, bullets, commands, links. - Lead with what users can feel or test, not proof plumbing. - Mention validation only after install/update instructions. - Be specific about where feedback is useful. - Do not mention private local proof paths in public announcements. - Do not overstate unverified platforms, channels, or provider behavior.
## Posting
When asked to post, use `$discord-user-post` to operate the logged-in Discord desktop app as the user. Resolve and visibly verify the exact server/channel, inspect the final body, and request action-time confirmation before entering or sending it. Never use OpenClaw channel sends, bots, webhooks, relays, or tokens.
Intended uses
- Use Release Openclaw Announcement when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.