Agent skill · writing content · steipete
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.
Why this skill is useful
Provides a structured template and specific guidelines for drafting release announcements that the AI wouldn't reliably generate on its own.
What it needs
Requires discord account access. About 2k tokens when loaded. Last updated 2026-08-07. 385,400 stars on the source repository.
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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/release-openclaw-announcement