New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release Openclaw Announcement

by openclaw in openclaw/openclaw

Draft or post OpenClaw beta, stable, or extended-stable Discord release announcements from changelog, tag, registry, and validation evidence.

MITAuto-check passedDevelopment

Install Release Openclaw Announcement

skills CLI
$ npx skills add openclaw/openclaw --skill release-openclaw-announcement -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install openclaw/openclaw release-openclaw-announcement --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/openclaw/openclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-openclaw-announcement .claude/skills/release-openclaw-announcement && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
release-openclaw-announcement
GitHub stars
392k
Token cost
~1.1k tokens
SKILL.md length
515 words
Files
2
Skills in repo
96
Repo updated
First seen
Licence
MIT

At a glance

Draft or post OpenClaw beta, stable, or extended-stable Discord release announcements from changelog, tag, registry, and validation evidence.

  • Works in 5 steps: GitHub release body and immutable tag;… → The released base version's… → Commits since the previous shipped… → …
  • Announcing a release
  • SKILL.md covers Evidence First, Required Copy, Style and Posting
  • Calls node; reaches openclaw.ai

What it does

Release Openclaw Announcement is an agent skill from openclaw/openclaw. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Changelog and release notes. It works with Discord. The repository describes itself as: The AI that really does things. Any OS. Any Platform. The lobster way. 🦞. The licence is MIT.

When your agent uses it

  • Announcing a release
  • Release candidate
  • Asking what users should test after an OpenClaw release

Example prompts

  • “/release-openclaw-announcement”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. GitHub release body and immutable tag; for extended-stable, also confirm the
  2. The released base version's CHANGELOG/.md and contribution
  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.

What it can do on your machine

Read from SKILL.md and the folder at commit f8e594e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • openclaw.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release Openclaw Announcement loads about 1.1k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 515 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from openclaw/openclaw at commit f8e594e, republished under its MIT licence (© openclaw). 515 words, ~1,083 tokens.

Download SKILL.mdSave it as .claude/skills/release-openclaw-announcement/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
release-openclaw-announcement
description
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.

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.

Show full SKILL.md (275 more words)Show less

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.

© openclaw, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/release-openclaw-announcement of openclaw/openclaw.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit f8e594e

Compare with similar skills

Release Openclaw Announcement next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release Openclaw Announcement compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Openclaw Announcement this skillopenclaw/openclaw392k—~1.1kAutomated safety check: PassMIT
Releasepwrdrvr/openclaw-codex-app-server265—~2.2kAutomated safety check: PassMIT
Writing Release NotesGoneTone/genshin-impact-wish-gacha-analyzer152—~1.6kAutomated safety check: PassMIT
Maintain DisCatSharpAiko-IT-Systems/DisCatSharp140—~1.2kAutomated safety check: PassMIT
Release Discord Postnevalang/neva1.1k—~500Automated safety check: PassMIT
Subwave Discord Releaseperminder-klair/subwave1.4k—~2.3kAutomated safety check: PassMIT

Similar skills

  • Release

    pwrdrvr/openclaw-codex-app-server

    Plan and publish a GitHub Release in a tag-driven repository.

    265 GitHub stars~2.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Writing Release Notes

    GoneTone/genshin-impact-wish-gacha-analyzer

    A skill your agent uses when drafting GitHub release notes or changelog content for this project (Genshin Impact Wish Gacha Analyzer).

    152 GitHub stars~1.6k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Maintain DisCatSharp

    Aiko-IT-Systems/DisCatSharp

    Guides changes to the DisCatSharp C# Discord library: tracing a payload field through parsing, serialization and caches, then validating across target frameworks.

    140 GitHub stars~1.2k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

  • Release Discord Post

    nevalang/neva

    Create a Discord-ready Neva release announcement from a GitHub release payload.

    1.1k GitHub stars~500 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Subwave Discord Release

    perminder-klair/subwave

    Draft a Discord release announcement for SUB/WAVE from a release PR, tag, or version number.

    1.4k GitHub stars~2.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Write Release Announcements

    Gremlinq/ExRam.Gremlinq

    A skill your agent uses to write the release notes and the announcement texts for an upcoming release, from the pull requests merged since the previous tag.

    187 GitHub stars~1.6k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from openclaw/openclaw

All 96 skills in this repo

  • Model Usage

    openclaw/openclaw

    Summarize CodexBar local cost logs by model for Codex or Claude, including current or full breakdowns.

    392k GitHub starsUsed in 1 repo~637 tokens
    Auto-check passed

  • Openclaw Live Updater

    openclaw/openclaw

    Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.

    392k GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Feishu Doc

    openclaw/openclaw

    Feishu document read/write workflows. An agent skill from openclaw/openclaw.

    392k GitHub stars~516 tokensUpdated today
    Auto-check passed

  • Tmux

    openclaw/openclaw

    Control tmux sessions/panes for interactive CLIs: list, capture output, send keys, paste text, monitor prompts.

    392k GitHub starsUsed in 1 repo~640 tokens
    Auto-check passed

  • Openclaw PR Maintainer

    openclaw/openclaw

    Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

    392k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Browser Automation

    openclaw/openclaw

    A skill your agent uses when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.

    392k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Release Openclaw Announcement

What does Release Openclaw Announcement do?

Draft or post OpenClaw beta, stable, or extended-stable Discord release announcements from changelog, tag, registry, and validation evidence. Release Openclaw Announcement is an agent skill from openclaw/openclaw. Draft or post OpenClaw beta, stable, or extended-stable Discord release announcements from changelog, tag, registry, and validation evidence.

When should I use Release Openclaw Announcement?

Release Openclaw Announcement fits situations like: announcing a release; release candidate; asking what users should test after an OpenClaw release.

How do I install Release Openclaw Announcement in Claude Code?

Run `npx skills add openclaw/openclaw --skill release-openclaw-announcement -a claude-code`. Or copy the skill folder (.agents/skills/release-openclaw-announcement in openclaw/openclaw) into .claude/skills/release-openclaw-announcement in your project. Claude Code loads it when a task matches its description.

How do I install Release Openclaw Announcement in Codex?

Run `npx skills add openclaw/openclaw --skill release-openclaw-announcement -a codex`. Or copy the skill folder (.agents/skills/release-openclaw-announcement in openclaw/openclaw) into .agents/skills/release-openclaw-announcement in your project. Codex loads it when a task matches its description.

Can I use Release Openclaw Announcement in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openclaw/openclaw --skill release-openclaw-announcement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-openclaw-announcement, .gemini/skills/release-openclaw-announcement, .github/skills/release-openclaw-announcement and .opencode/skills/release-openclaw-announcement in your project.

What does Release Openclaw Announcement need to run?

Going by SKILL.md and its folder, Release Openclaw Announcement needs the command-line tools its instructions call (node). Our summary lists: Node.js.

Does Release Openclaw Announcement access the network?

SKILL.md names 1 domain. In commands or code: openclaw.ai; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Release Openclaw Announcement safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release Openclaw Announcement use?

Release Openclaw Announcement is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release Openclaw Announcement use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release Openclaw Announcement?

Skills that share tags, products or a category with Release Openclaw Announcement: Release (pwrdrvr/openclaw-codex-app-server, 265 stars), Writing Release Notes (GoneTone/genshin-impact-wish-gacha-analyzer, 152 stars), Maintain DisCatSharp (Aiko-IT-Systems/DisCatSharp, 140 stars) and Release Discord Post (nevalang/neva, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Openclaw Announcement?

openclaw (a GitHub organization) maintains it in openclaw/openclaw, which has 391,504 GitHub stars. The repository holds 96 skills in this directory. The repository was last updated on October 9, 2026.

Source: openclaw/openclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.