Agent skill

Workclaw Release Publish

by haojing8312 in haojing8312/WorkClaw

A skill your agent uses when publishing a confirmed WorkClaw desktop release after the version number and bilingual Chinese plus English release notes have already been reviewed and approved by a…

Apache-2.0Auto-check passedDevelopment

Install Workclaw Release Publish

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

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

GitHub CLI
$ gh skill install haojing8312/WorkClaw workclaw-release-publish --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-publish .claude/skills/workclaw-release-publish && 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-publish
GitHub stars
141
Token cost
~786 tokens
SKILL.md length
350 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when publishing a confirmed WorkClaw desktop release after the version number and bilingual Chinese plus English release notes have already been reviewed and approved by a…

  • Works in 10 steps: Verify the requested tag format and… → Re-read the approved release notes and… → Update the release notes template with… → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers Overview, When to Use, Required Inputs and Files To Update, plus 4 more sections
  • Calls pnpm

What it does

Workclaw Release Publish is an agent skill from haojing8312/WorkClaw. Use when publishing a confirmed WorkClaw desktop release after the version number and bilingual Chinese plus English release notes have already been reviewed and approved by a human.

Its SKILL.md is about 790 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 Development, covering Changelog and release notes and Translation. It works with pnpm, Tauri and GitHub. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Changelog and release notes
  • Tasks that involve Translation

Example prompts

  • “/workclaw-release-publish”

Workflow steps

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

  1. Verify the requested tag format and confirm the version files match the intended release
  2. Re-read the approved release notes and sanity-check that they still cover the major user-visible outcomes discovered during release prep
  3. Update the release notes template with the approved bilingual content
  4. If an important user-facing outcome is missing, stop and ask for note confirmation again instead of publishing a partial summary
  5. Run release checks
  6. Run user-flow or packaging verification when release surface changed
  7. Commit the release changes
  8. Push main
  9. Create and push the tag
  10. Report local installer paths and note that the remote tag triggers .github/workflows/release-windows.yml

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 Publish loads about 786 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 350 words of instructions outside code blocks.

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

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). 350 words, ~786 tokens.

Download SKILL.mdSave it as .claude/skills/workclaw-release-publish/SKILL.md (or your agent's skills folder).
name
workclaw-release-publish
description
Use when publishing a confirmed WorkClaw desktop release after the version number and bilingual Chinese plus English release notes have already been reviewed and approved by a human.

WorkClaw Release Publish

Overview

Use this skill only after the release version and bilingual release notes are confirmed. It updates release metadata, commits the release, pushes the branch, creates and pushes the tag, and produces a local Windows package.

When to Use

  • The user has already confirmed the target version
  • The user has already confirmed the Chinese + English release notes
  • The user wants the tag pushed to trigger the GitHub Windows release workflow
  • The user wants a local .exe or .msi generated as part of the release

If the version or release notes are not yet confirmed, stop and use workclaw-release-prep.

Required Inputs

  • Confirmed version in vX.Y.Z format
  • Confirmed bilingual release notes content

Files To Update

  • apps/runtime/package.json
  • apps/runtime/src-tauri/Cargo.toml
  • apps/runtime/src-tauri/tauri.conf.json
  • .github/release-windows-notes.md
  • apps/runtime/src-tauri/Cargo.lock when refreshed by build tooling

Execution Order

  1. Verify the requested tag format and confirm the version files match the intended release
  2. Re-read the approved release notes and sanity-check that they still cover the major user-visible outcomes discovered during release prep
  3. Update the release notes template with the approved bilingual content
  4. If an important user-facing outcome is missing, stop and ask for note confirmation again instead of publishing a partial summary
  5. Run release checks:
    • pnpm release:check-version <tag>
    • pnpm test:release
    • pnpm test:installer
    • pnpm test:release-docs
  6. Run user-flow or packaging verification when release surface changed:
    • pnpm test:e2e:runtime
    • pnpm build:runtime
  7. Commit the release changes
  8. Push main
  9. Create and push the tag
  10. Report local installer paths and note that the remote tag triggers .github/workflows/release-windows.yml
Show full SKILL.md (101 more words)Show less

Required Output

Use this shape:

md
## Publish Summary
- Version:
- Commit:
- Tag:
- Commands run:
- Local artifacts:
- Remote trigger:

## Verification Summary
- Changed surface:
- Results:
- Still unverified:
- Verification verdict:

## Release Readiness
- Verdict:
- Blocking issues:
- Ship recommendation:

Guardrails

  • Never auto-publish based only on AI-generated version suggestions
  • Never create a release tag before release checks pass
  • Never claim GitHub release completion unless the tag push succeeded
  • If packaging fails, report the failure and do not describe the release as complete
  • Never silently publish if the approved notes are missing a major provider/model compatibility fix or other concrete user-facing outcome discovered during prep

Common Mistakes

  • Publishing from an unconfirmed draft
  • Forgetting to update all three runtime version files
  • Pushing a tag that does not match app versions
  • Reporting only local packaging while skipping release checks

© 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-publish of haojing8312/WorkClaw.

Open the folder on GitHubat commit 81ae074

Compare with similar skills

Workclaw Release Publish 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 Publish compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workclaw Release Publish this skillhaojing8312/WorkClaw141—~786Automated safety check: PassApache-2.0
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Yaak Changelogmountain-loop/yaak19k—~1.6kAutomated safety check: PassMIT
Store Submitzhitongblog/solomd1.2k—~1.7kAutomated safety check: NotesMIT
Pre ReleaseZhuoZhuoCrayon/throttled-py651—~1.1kAutomated safety check: PassMIT
ZCF Release AutomationUfoMiao/zcf6.1k—~3.4kAutomated safety check: PassMIT

Similar skills

  • Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Yaak Changelog

    mountain-loop/yaak

    Create or edit Yaak changelogs. An agent skill from mountain-loop/yaak.

    19k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Store Submit

    zhitongblog/solomd

    Publish a SoloMD release to the stores that have no usable submission API — Google Play Console and Microsoft Partner Center — by driving them through the local Unzoo Browser REST API.

    1.2k GitHub stars~1.7k tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • Pre Release

    ZhuoZhuoCrayon/throttled-py

    Automates release preparation for throttled-py. An agent skill from ZhuoZhuoCrayon/throttled-py.

    651 GitHub stars~1.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.

    6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Release Workflow

    Caldis/react-zmage

    A skill your agent uses when the user wants to ship a new version of react-zmage to npm.

    945 GitHub stars~3.6k tokensUpdated 4 mo ago
    DevelopmentAuto-check: notes

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
  • 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 Publish

What does Workclaw Release Publish do?

A skill your agent uses when publishing a confirmed WorkClaw desktop release after the version number and bilingual Chinese plus English release notes have already been reviewed and approved by a…. Workclaw Release Publish is an agent skill from haojing8312/WorkClaw. Use when publishing a confirmed WorkClaw desktop release after the version number and bilingual Chinese plus English release notes have already been reviewed and approved by a human.

When should I use Workclaw Release Publish?

Workclaw Release Publish fits situations like: tasks that involve Changelog and release notes; tasks that involve Translation.

How do I install Workclaw Release Publish in Claude Code?

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

How do I install Workclaw Release Publish in Codex?

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

Can I use Workclaw Release Publish 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-publish -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-publish, .gemini/skills/workclaw-release-publish, .github/skills/workclaw-release-publish and .opencode/skills/workclaw-release-publish in your project.

What does Workclaw Release Publish need to run?

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

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

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

About 786 tokens (SKILL.md is roughly 3.1k 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 Publish?

Skills that share tags, products or a category with Workclaw Release Publish: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Yaak Changelog (mountain-loop/yaak, 19k stars), Store Submit (zhitongblog/solomd, 1.2k stars) and Pre Release (ZhuoZhuoCrayon/throttled-py, 651 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workclaw Release Publish?

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.