What is workclaw-release-readiness?

A release-readiness check for WorkClaw changes that affect versions, installers, release documents, packaging, or vendor release paths. It produces a GREEN, YELLOW, or RED recommendation based on the relevant checks.

Checking version metadata, release paths, installer behavior, release notes, vendor lanes, and desktop build outputs before a branch is shipped.

It separates shipping checks from ordinary code tests and shows whether release-related problems still block publishing.

How haojing8312/WorkClaw configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to haojing8312/WorkClaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/haojing8312/WorkClaw/main/.agents/skills/workclaw-release-readiness/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/haojing8312/WorkClaw

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/haojing8312/workclaw/workclaw-release-readiness/github.svg)](https://agentmods.dev/skills/haojing8312/workclaw/workclaw-release-readiness)

Your own site

<a href="https://agentmods.dev/skills/haojing8312/workclaw/workclaw-release-readiness"><img src="https://agentmods.dev/badge/skills/haojing8312/workclaw/workclaw-release-readiness/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/haojing8312/workclaw/workclaw-release-readiness"><img src="https://agentmods.dev/badge/skills/haojing8312/workclaw/workclaw-release-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 463 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.00463
Opus 5.5	$0.00016	$0.00185
Sonnet 5.5	$0.00008	$0.00093
Haiku 4.5	$0.00004	$0.00046

Measured 2mo ago against content hash cc398c23ea67, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

workclaw-release-readiness scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/workclaw-release-readiness/SKILL.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:

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

Core Pattern

Identify which release-sensitive surface changed.
Run the matching release commands.
Start from "safe to ship" and only downgrade when there is concrete evidence.
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.

Read the full file on GitHub · 58 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 58 lines · 40 tokens per session scan A cc398c23ea67

Subscribe to this mod's changes

workclaw-release-readiness is a skill published in the GitHub repository haojing8312/WorkClaw (140 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 463 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Releases

workclaw-release-readiness next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
workclaw-release-readinesshaojing8312/WorkClaw	Skill	140	5mo ago	Apache-2.0	A	40	Claude Code, Codex
release-announcementpaperclipai/paperclip	Skill	113k	today	MIT	A	42	Claude Code, Codex
release-notesphuryn/pm-skills	Skill	28k	3d ago	MIT	A	57	Claude Code
releasethedotmack/claude-mem	Skill	116k	today	Apache-2.0	A	13	Claude Code
multi-agent-release-managerchromium/chromium	Skill	25k	today	BSD-3-Clause	A	27	Claude Code, Codex
pack-submitaeonfun/aeon	Skill	792	yesterday	MIT	A	27	Claude Code, Codex
updater_guidesiddsachar/row-bot	Skill	1.7k	today	Apache-2.0	A	22	Claude Code, Codex

WorkClaw: Skill for Claude Code