skills.rest
openclaw
openclawOFFICIAL
Explore all skills by this author →
Website𝕏@openclawGitHub

release-openclaw-announcement

Draft Discord release announcements from changelog, tag, and validation evidence.

388k|81.5k|Updated Nov 24, 2025
Search Tags:#communication#Discord#Versioning#release announcement#Openclaw#ChangeLog#Beta
One-click install
npx skills add https://github.com/openclaw/openclaw --skill release-openclaw-announcement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-openclaw-announcement
Source: https://github.com/openclaw/openclaw/tree/main/.agents/skills/release-openclaw-announcement
Command: npx skills add https://github.com/openclaw/openclaw --skill release-openclaw-announcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Announcing software releases requires synthesizing evidence from multiple sources into a clear, accurate, and channel-appropriate message. This Skill eliminates guesswork by enforcing evidence-based drafting for OpenClaw beta, stable, and extended-stable releases.

Core Features & Use Cases

  • Evidence-Based Drafting: Reads GitHub release bodies, CHANGELOG.md sections, commits, registry metadata, and validation status before writing copy.
  • Channel-Specific Templates: Generates appropriate copy for beta, stable, and extended-stable channels with correct update commands and risk framing.
  • Use Case: After shipping OpenClaw 2026.5.25-beta.1, use this Skill to produce a Discord announcement that highlights user-observable changes, includes the correct openclaw update --channel beta --yes command, and links to the GitHub release.

Quick Start

Draft a Discord beta announcement for the latest OpenClaw release using changelog, tag, and validation evidence.

Frequently Asked Questions about release-openclaw-announcement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I announce a beta release on Discord?▼

Draft the announcement from GitHub release body, CHANGELOG.md, and registry metadata. Include the exact version, beta risk framing, focused test areas, the `openclaw update --channel beta --yes` command, and a link to the GitHub release.

What evidence should I gather before writing a release announcement?▼

Read the GitHub release body or immutable tag, the CHANGELOG.md section for the released version, commits since the previous shipped version, registry metadata for the exact version, and relevant validation status.

Can I post the announcement directly through OpenClaw?▼

No. Use the `$discord-user-post` skill to operate the logged-in Discord desktop app as the user. Never use OpenClaw channel sends, bots, webhooks, relays, or tokens for posting.

Why are npm install commands excluded from beta announcements?▼

Beta announcements promote the `openclaw update --channel beta --yes` command and the openclaw.ai install path. npm install commands are only included when the operator explicitly asks for npm-specific copy.

What is the difference between stable and extended-stable announcement wording?▼

Stable announcements use `openclaw update --channel stable --yes`. Extended-stable announcements omit `--yes` so users moving from newer regular stable see the downgrade warning, and they avoid inheriting regular stable platform claims.

Related Skills

Explore More Content & Communication Skills→
Unique-AGUnique-AG
5

changelog-pyproject

Update CHANGELOG.md and pyproject.toml versions from commit history.

Official
Intermediate
Claude-Code-Community-IrelandClaude-Code-Community-Ireland
10

discord

Manages Discord servers including announcements, events, moderation, and statistics via API/MCP tools.

Official
Intermediate
anthony-chaudharyanthony-chaudhary
18

stable-release

Promote a shipped DOS rolling release into a stable channel with rollback evidence.

Community
Advanced
vorynkavitaliyvorynkavitaliy

changelog-automation

Generate Keep a Changelog release notes from commits and PRs.

Community
Advanced