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

Openclaw Release Validation

by openclaw in openclaw/openclaw

Guide human release testing on an isolated OCM copy or approved in-place gateway, collect feedback, or refresh the release campaign.

MITAuto-check passed

Install Openclaw Release Validation

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

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

GitHub CLI
$ gh skill install openclaw/openclaw openclaw-release-validation --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/openclaw-release-validation .claude/skills/openclaw-release-validation && 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
openclaw-release-validation
GitHub stars
392k
Token cost
~987 tokens
SKILL.md length
472 words
Files
13 (incl. scripts, references, assets)
Skills in repo
93
Repo updated
First seen
Licence
MIT

At a glance

Guide human release testing on an isolated OCM copy or approved in-place gateway, collect feedback, or refresh the release campaign.

  • Works in 5 steps: Read installed skill check. Introduce… → Read campaign lookup/dispatch. Require a… → Read Gateway preparation. Discover… → …
  • SKILL.md covers Choose the mode, Human validation and Boundaries
  • Runs JavaScript scripts from its folder

What it does

Openclaw Release Validation is an agent skill from openclaw/openclaw. Guide human release testing on an isolated OCM copy or approved in-place gateway, collect feedback, or refresh the release campaign.

Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 15 other files, including scripts, reference files and assets (for example `assets/tooling-feedback.md`, `assets/validation-worksheet.md` and `references/campaign-artifact.md`).

The repository describes itself as: The AI that really does things. Any OS. Any Platform. The lobster way. 🦞. The licence is MIT.

Example prompts

  • “/openclaw-release-validation”

Requirements

  • Node.js

Workflow steps

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

  1. Read installed skill check. Introduce the run briefly: choose a Gateway, protect it with a disposable OCM copy or approve an in-place…
  2. Read campaign lookup/dispatch. Require a current campaign and record its stable train and current beta. Gateway preparation pins the main…
  3. Read Gateway preparation. Discover without mutation, let the tester choose source and mode, then prepare the selected target. Never use…
  4. Only after readiness succeeds, offer local diagnostics for an isolated target, then read human testing to create the worksheet and guide…
  5. On finish validation, read cleanup and report approval. It handles blocked upgrades too. Review the complete batch before any post and…

What it can do on your machine

Read from SKILL.md and the folder at commit 1eb5970. 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

    Ships 1 file in scripts/ (JavaScript), which the agent can run.

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

  • Network

    No URLs in SKILL.md.

    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

Openclaw Release Validation loads about 987 tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 40 tokens; SKILL.md has 472 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~987
With references · SKILL.md plus every file in references/, read only if the agent opens them
~13k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from openclaw/openclaw at commit 1eb5970, republished under its MIT licence (© openclaw). 472 words, ~987 tokens.

Download SKILL.mdSave it as .claude/skills/openclaw-release-validation/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
openclaw-release-validation
description
Guide human release testing on an isolated OCM copy or approved in-place gateway, collect feedback, or refresh the release campaign.
user-invocable
true
disable-model-invocation
true

OpenClaw Release Validation

Help a human test an immutable latest-main build against a selected real Gateway's state. Automate preparation, triage, and reporting; the human drives interactive surfaces and judges quality. This skill collects feedback, not a release go/no-go decision.

Choose the mode

  • Campaign artifact: only when RELEASE_VALIDATION_ARTIFACT_PATH is present. Read artifact generation, write that artifact, and stop. GitHub is read-only; no skill-update request or interactive setup.
  • Update campaign: for an explicit refresh request, read installed skill check, then campaign lookup/dispatch. Dispatch the isolated runner for the selected explicit tag, verify its issue, and stop. Never analyze or edit the canonical issue yourself.
  • Validate release: default human-testing workflow below. It joins the campaign; it never creates or rewrites the issue body directly.

Human validation

  1. Read installed skill check. Introduce the run briefly: choose a Gateway, protect it with a disposable OCM copy or approve an in-place update, prepare the pinned main build, then test and review feedback.
  2. Read campaign lookup/dispatch. Require a current campaign and record its stable train and current beta. Gateway preparation pins the main test target separately.
  3. Read Gateway preparation. Discover without mutation, let the tester choose source and mode, then prepare the selected target. Never use the caller's active checkout.
  4. Only after readiness succeeds, offer local diagnostics for an isolated target, then read human testing to create the worksheet and guide one chosen surface at a time.
  5. On finish validation, read cleanup and report approval. It handles blocked upgrades too. Review the complete batch before any post and preserve the exact structured-report contract.

Before readiness is terminal, show only campaign/beta identity, source/mode choice, and upgrade progress or errors. Do not expose testing instructions or create a worksheet for a Gateway that never became ready.

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

Boundaries

An isolated OCM copy must prove all candidate-writable paths remain contained. Do not bypass a failed containment check with manual copying. Copied channel credentials require explicit authorization to stop their current owner and a restoration plan. In-place mode changes real state: present verified backup/snapshot and dry-run evidence before obtaining update approval. Rollback requires separate approval because newer migrations can make code-only reversion unsafe.

Keep one worksheet for a ready candidate; only tester-authored results count as tested. A blocked candidate uses its final upgrade-report draft instead. For setup, OCM, backup, build or cleanup failures, use the private tooling-feedback packet; do not turn these into candidate findings. With no candidate evaluation, clean up and report that fact without producing a candidate vote or posting batch.

Diagnostics are opt-in, disposable-target-only, loopback-only and content-off. Public feedback excludes raw logs, telemetry, paths, Gateway names, identifiers, credentials and setup/cleanup details. Apply the report's narrow environment allowlist and sanitization before showing the complete draft. finish validation does not authorize posts; existing explicit batch approval does. The Discord summary is a copy-ready handoff, never an automatic send.

© 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 12 other files (scripts, references, assets) in .agents/skills/openclaw-release-validation of openclaw/openclaw.

  • SKILL.md
  • assets/tooling-feedback.md
  • assets/validation-worksheet.md
  • references/campaign-artifact.md
  • references/campaign.md
  • references/gateway-preparation.md
  • references/human-testing.md
  • references/local-diagnostics.md
  • references/report-closeout.md
  • references/skill-update.md
  • references/structured-report.md
  • references/tooling-feedback.md
  • scripts/check-update.mjs

Open the folder on GitHubat commit 1eb5970

Compare with similar skills

Openclaw Release Validation 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.

Openclaw Release Validation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Openclaw Release Validation this skillopenclaw/openclaw392k—~987Automated safety check: PassMIT
Copy Editingcoreyhaines31/marketingskills54k—~4.5kAutomated safety check: PassMIT
Cross Origin Isolationthedaviddias/Front-End-Checklist74k—~565Automated safety check: PassMIT
Bio Copy Number Subclonal Copy NumberGPTomics/bioSkills1.2k2 repos~3.5kAutomated safety check: PassMIT
Hunting For Shadow Copy Deletionmukul975/Anthropic-Cybersecurity-Skills34k—~891Automated safety check: PassApache-2.0
Bio Copy Number Copy Ratio SegmentationGPTomics/bioSkills1.2k2 repos~3.5kAutomated safety check: PassMIT

Similar skills

  • Copy Editing

    coreyhaines31/marketingskills

    When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content.

    54k GitHub stars~4.5k tokensUpdated today
    Writing & ContentAuto-check passed

  • Cross Origin Isolation

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing security-sensitive web apps, SharedArrayBuffer usage, worker-heavy apps, editors, or measurement features that require cross-origin isolation.

    74k GitHub stars~565 tokensUpdated 2 days ago
    Auto-check passed

  • Bio Copy Number Subclonal Copy Number

    GPTomics/bioSkills

    Resolve subclonal copy number, whole-genome doubling, and copy-number tumor evolution from bulk sequencing with Battenberg, TITAN, and MEDICC2.

    1.2k GitHub starsUsed in 2 repos~3.5k tokens
    Research & ScienceAuto-check passed

  • Hunting For Shadow Copy Deletion

    mukul975/Anthropic-Cybersecurity-Skills

    Runs a hypothesis-driven threat hunt for Volume Shadow Copy deletion (T1490) by querying SIEM/EDR telemetry for vssadmin, wmic shadowcopy, and PowerShell shadow-copy-deletion commands.

    34k GitHub stars~891 tokensUpdated 1 mo ago
    SecurityAuto-check passed

  • Bio Copy Number Copy Ratio Segmentation

    GPTomics/bioSkills

    Normalize read-depth copy-ratio profiles and segment them into copy-number regions using circular binary segmentation (CBS, DNAcopy), hidden Markov models, HaarSeg, and fused-lasso methods.

    1.2k GitHub starsUsed in 2 repos~3.5k tokens
    DatabasesAuto-check passed

  • UX Copy

    sickn33/agentic-awesome-skills

    Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone

    47k GitHub starsUsed in 1 repo~1k tokens
    Writing & ContentAuto-check passed

More from openclaw/openclaw

All 93 skills in this repo

  • 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

  • Tmux

    openclaw/openclaw

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

    392k GitHub starsUsed in 2 repos~640 tokens
    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

  • 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

  • Clawsweeper

    openclaw/openclaw

    A skill your agent uses for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed…

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

Questions about Openclaw Release Validation

What does Openclaw Release Validation do?

Guide human release testing on an isolated OCM copy or approved in-place gateway, collect feedback, or refresh the release campaign. Openclaw Release Validation is an agent skill from openclaw/openclaw. Guide human release testing on an isolated OCM copy or approved in-place gateway, collect feedback, or refresh the release campaign.

How do I install Openclaw Release Validation in Claude Code?

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

How do I install Openclaw Release Validation in Codex?

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

Can I use Openclaw Release Validation 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 openclaw-release-validation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openclaw-release-validation, .gemini/skills/openclaw-release-validation, .github/skills/openclaw-release-validation and .opencode/skills/openclaw-release-validation in your project.

What does Openclaw Release Validation need to run?

Going by SKILL.md and its folder, Openclaw Release Validation needs JavaScript for the scripts in its folder. Our summary lists: Node.js.

Does Openclaw Release Validation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Openclaw Release Validation 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Openclaw Release Validation use?

Openclaw Release Validation 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 Openclaw Release Validation use?

About 987 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.

What are the alternatives to Openclaw Release Validation?

Skills that share tags, products or a category with Openclaw Release Validation: Copy Editing (coreyhaines31/marketingskills, 54k stars), Cross Origin Isolation (thedaviddias/Front-End-Checklist, 74k stars), Bio Copy Number Subclonal Copy Number (GPTomics/bioSkills, 1.2k stars) and Hunting For Shadow Copy Deletion (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Openclaw Release Validation?

openclaw (a GitHub organization) maintains it in openclaw/openclaw, which has 391,610 GitHub stars. The repository holds 93 skills in this directory. The repository was last updated on October 8, 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.