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.
curl -O https://raw.githubusercontent.com/haojing8312/WorkClaw/main/.agents/skills/workclaw-release-prep/SKILL.mdgit clone --depth 1 https://github.com/haojing8312/WorkClawWrote 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.
[](https://agentmods.dev/skills/haojing8312/workclaw/workclaw-release-prep)<a href="https://agentmods.dev/skills/haojing8312/workclaw/workclaw-release-prep"><img src="https://agentmods.dev/badge/skills/haojing8312/workclaw/workclaw-release-prep/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.
<a href="https://agentmods.dev/skills/haojing8312/workclaw/workclaw-release-prep"><img src="https://agentmods.dev/badge/skills/haojing8312/workclaw/workclaw-release-prep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00048 | $0.00854 |
| Opus 5.5 | $0.00019 | $0.00342 |
| Sonnet 5.5 | $0.00010 | $0.00171 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
workclaw-release-prep 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WorkClaw Release Prep
Overview
Use this skill before cutting a WorkClaw release. It recommends the next version, explains why, and drafts bilingual release notes. It does not publish anything.
When to Use
- The user wants a release recommendation
- The user wants AI to decide between
patch,minor, ormajor - The user wants bilingual Chinese + English release notes
- The user wants a confirmation-ready release package before tagging
Do not use this skill to push commits, create tags, or publish releases. Use workclaw-release-publish after confirmation.
Inspect First
git tag --sort=-creatordategit log <last-tag>..HEAD --onelinegit log <last-tag>..HEAD --format=%H%n%s%n%b%n==END==git diff --name-only <last-tag>..HEAD- For high-signal commits, inspect
git show --stat --summary <sha> apps/runtime/package.jsonapps/runtime/src-tauri/Cargo.tomlapps/runtime/src-tauri/tauri.conf.json.github/release-windows-notes.md- Any release-impacting docs or plans the user wants included
Before drafting release notes, build a short candidate user-visible changes list from:
- commit titles and commit bodies
- test names that describe user-facing behavior
- provider or model names mentioned explicitly, such as
Qwen,DeepSeek,OpenAI,Claude - compatibility, routing, transport, recovery, installer, branding, and skill/runtime keywords
Default rule: if a commit message or test name names a concrete model, provider, or desktop behavior, treat it as a release-note candidate unless there is strong evidence it is purely internal.
Version Recommendation Rules
- Recommend
patchfor bug fixes, stability hardening, recovery improvements, small UX polish, or non-breaking desktop flow fixes - Recommend
minorfor clear new user-facing capabilities, new workflows, new navigation models, or meaningful product surface expansion - Recommend
majoronly for breaking changes, migrations, compatibility breaks, or strong user behavior changes that require explicit upgrade communication
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.
- 1mo ago First seen · 96 lines · 48 tokens per session scan A adcfce7e91bd
workclaw-release-prep is a skill published in the GitHub repository haojing8312/WorkClaw (141 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 854 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.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.