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

Workclaw Release Readiness

by haojing8312 in haojing8312/WorkClaw

A skill your agent uses when changes affect versioning, installer branding, release docs, packaging outputs, or vendor release lanes in WorkClaw before deciding a branch is ready to ship.

Apache-2.0Auto-check passedProduct & Project Management

Install Workclaw Release Readiness

skills CLI
$ npx skills add haojing8312/WorkClaw --skill workclaw-release-readiness -a claude-code

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

GitHub CLI
$ gh skill install haojing8312/WorkClaw workclaw-release-readiness --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/haojing8312/WorkClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/workclaw-release-readiness .claude/skills/workclaw-release-readiness && 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
workclaw-release-readiness
GitHub stars
141
Token cost
~559 tokens
SKILL.md length
243 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when changes affect versioning, installer branding, release docs, packaging outputs, or vendor release lanes in WorkClaw before deciding a branch is ready to ship.

  • Works in 4 steps: Identify which release-sensitive surface… → Run the matching release commands. → Start from "safe to ship" and only… → …
  • Changes affect versioning
  • SKILL.md covers Overview, When to Use, Command Routing and Required Output, plus 3 more sections
  • Calls pnpm

What it does

Workclaw Release Readiness is an agent skill from haojing8312/WorkClaw. Use when changes affect versioning, installer branding, release docs, packaging outputs, or vendor release lanes in WorkClaw before deciding a branch is ready to ship.

Its SKILL.md is about 560 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering Feature launches and release readiness and Technical writing. It works with pnpm. The licence is Apache-2.0.

When your agent uses it

  • Changes affect versioning
  • Installer branding
  • Packaging outputs
  • Vendor release lanes in WorkClaw before deciding a branch is ready to ship

Example prompts

  • “/workclaw-release-readiness”

Workflow steps

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

  1. Identify which release-sensitive surface changed.
  2. Run the matching release commands.
  3. Start from "safe to ship" and only downgrade when there is concrete evidence.
  4. If blocked, provide an explicit unblock checklist.

What it can do on your machine

Read from SKILL.md and the folder at commit 81ae074. 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:

    • pnpm

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

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    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

Workclaw Release Readiness loads about 559 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 243 words of instructions outside code blocks.

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

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 haojing8312/WorkClaw at commit 81ae074, republished under its Apache-2.0 licence (© haojing8312). 243 words, ~559 tokens.

Download SKILL.mdSave it as .claude/skills/workclaw-release-readiness/SKILL.md (or your agent's skills folder).
name
workclaw-release-readiness
description
Use when changes affect versioning, installer branding, release docs, packaging outputs, or vendor release lanes in WorkClaw before deciding a branch is ready to ship.

WorkClaw Release Readiness

Overview

Use this skill for shipping-sensitive changes. It separates release readiness from ordinary code verification and produces a clear ship recommendation with evidence.

When to Use

  • Version files or release metadata changed
  • Installer branding or installer checks changed
  • Release docs changed
  • Packaging outputs or desktop build expectations changed
  • Vendor lane or upstream sync release paths changed
  • A branch is being assessed for ship readiness after release-sensitive work

Do not use this for ordinary feature work that does not touch release-sensitive surfaces.

Command Routing

  • Run pnpm release:check-version for version and release metadata changes.
  • Run pnpm test:release for release-path validation.
  • Run pnpm test:installer for installer branding or installer flow changes.
  • Run pnpm test:release-docs for release note or release document changes.
  • Run pnpm test:openclaw-vendor-lane for vendor sync or lane changes.
  • Run pnpm build:runtime when packaging output or desktop build behavior changed.

Required Output

  • Release verdict: GREEN, YELLOW, or RED
  • Blocking issues, if any
  • Required release-note or documentation follow-ups
  • Final recommendation on whether the branch is safe to ship

Output Template

Use this shape:

md
## Release Readiness
- Verdict: GREEN | YELLOW | RED
- Changed release surface:
- Commands run:
- Blocking issues:
- Required follow-ups:
- Ship recommendation:

Core Pattern

  1. Identify which release-sensitive surface changed.
  2. Run the matching release commands.
  3. Start from "safe to ship" and only downgrade when there is concrete evidence.
  4. If blocked, provide an explicit unblock checklist.

Common Mistakes

  • Treating release-doc or installer changes as low-risk and skipping dedicated checks.
  • Reporting a release verdict without citing commands or evidence.
  • Mixing ordinary runtime verification with ship-readiness judgment and losing the release signal.

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

Files

Just SKILL.md in .agents/skills/workclaw-release-readiness of haojing8312/WorkClaw.

Open the folder on GitHubat commit 81ae074

Compare with similar skills

Workclaw Release Readiness 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.

Workclaw Release Readiness compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workclaw Release Readiness this skillhaojing8312/WorkClaw141—~559Automated safety check: PassApache-2.0
.NET MAUI Release Readinessdotnet/maui23k—~15kAutomated safety check: PassMIT
Release ValidationMesh-LLM/mesh-llm3.5k—~2.6kAutomated safety check: PassApache-2.0
Final Release Reviewopenai/openai-agents-python30k—~5.4kAutomated safety check: PassMIT
Final Release Reviewopenai/openai-agents-js3.9k—~4kAutomated safety check: PassMIT
Acceptance Demo GeneratorChachamaru127/claude-code-harness3.2k—~3.4kAutomated safety check: NotesMIT

Similar skills

  • .NET MAUI Release Readiness

    dotnet/maui

    Official

    Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.

    23k GitHub stars~15k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Release Validation

    Mesh-LLM/mesh-llm

    A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…

    3.5k GitHub stars~2.6k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Final Release Review

    openai/openai-agents-python

    Official

    Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.

    30k GitHub stars~5.4k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Final Release Review

    openai/openai-agents-js

    Official

    Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.

    3.9k GitHub stars~4k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Acceptance Demo Generator

    Chachamaru127/claude-code-harness

    Renders a single HTML page showing each acceptance criterion as verified or not, with a ship, wait, or reject recommendation for non-engineers.

    3.2k GitHub stars~3.4k tokensUpdated 5 days ago
    Product & Project ManagementAuto-check: notes

  • Schematic

    blader/schematic

    Reverse engineer a detailed product and technical specification document from a git branch's implementation.

    241 GitHub stars~2.2k tokensUpdated 7 mo ago
    Product & Project ManagementAuto-check passed

More from haojing8312/WorkClaw

All 14 skills in this repo

  • Design Style Skill

    haojing8312/WorkClaw

    Select a consistent visual design system for PPT slides using radius/spacing style recipes.

    141 GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed

  • Slack Messaging

    haojing8312/WorkClaw

    A skill your agent uses when asked to send or read Slack messages, check Slack channels, test Slack integrations, or interact with a Slack workspace from the command line.

    141 GitHub stars~897 tokensUpdated 4 mo ago
    Auto-check passed

  • Ppt Editing Skill

    haojing8312/WorkClaw

    Edit existing PowerPoint files or templates with XML-safe workflows.

    141 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

  • Slide Making Skill

    haojing8312/WorkClaw

    Implement single-slide PowerPoint pages with PptxGenJS. An agent skill from haojing8312/WorkClaw.

    141 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed

  • Workclaw Change Verification

    haojing8312/WorkClaw

    A skill your agent uses when changes affect runtime code, tests, skill assets, or build and test behavior in WorkClaw and verification is required before claiming completion.

    141 GitHub stars~555 tokensUpdated 4 mo ago
    Auto-check passed

  • Workclaw Implementation Strategy

    haojing8312/WorkClaw

    A skill your agent uses when changing runtime behavior, routing, provider integration, tool permissions, sidecar protocols, or vendor sync boundaries in WorkClaw before editing code.

    141 GitHub stars~575 tokensUpdated 4 mo ago
    Auto-check passed

Works with

Categories

Questions about Workclaw Release Readiness

What does Workclaw Release Readiness do?

A skill your agent uses when changes affect versioning, installer branding, release docs, packaging outputs, or vendor release lanes in WorkClaw before deciding a branch is ready to ship. Workclaw Release Readiness is an agent skill from haojing8312/WorkClaw. Use when changes affect versioning, installer branding, release docs, packaging outputs, or vendor release lanes in WorkClaw before deciding a branch is ready to ship.

When should I use Workclaw Release Readiness?

Workclaw Release Readiness fits situations like: changes affect versioning; installer branding; packaging outputs; vendor release lanes in WorkClaw before deciding a branch is ready to ship.

How do I install Workclaw Release Readiness in Claude Code?

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

How do I install Workclaw Release Readiness in Codex?

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

Can I use Workclaw Release Readiness 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 haojing8312/WorkClaw --skill workclaw-release-readiness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workclaw-release-readiness, .gemini/skills/workclaw-release-readiness, .github/skills/workclaw-release-readiness and .opencode/skills/workclaw-release-readiness in your project.

What does Workclaw Release Readiness need to run?

Going by SKILL.md and its folder, Workclaw Release Readiness needs the command-line tools its instructions call (pnpm).

Does Workclaw Release Readiness 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 Workclaw Release Readiness 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 Workclaw Release Readiness use?

Workclaw Release Readiness is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workclaw Release Readiness use?

About 559 tokens (SKILL.md is roughly 2.2k 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 Workclaw Release Readiness?

Skills that share tags, products or a category with Workclaw Release Readiness: .NET MAUI Release Readiness (dotnet/maui, 23k stars), Release Validation (Mesh-LLM/mesh-llm, 3.5k stars), Final Release Review (openai/openai-agents-python, 30k stars) and Final Release Review (openai/openai-agents-js, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workclaw Release Readiness?

haojing8312 (a GitHub user) maintains it in haojing8312/WorkClaw, which has 141 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on May 27, 2026.

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