- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add JimLiu/baocut --skill bcut-release -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add JimLiu/baocut --skill bcut-release -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add JimLiu/baocut --skill bcut-release -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add JimLiu/baocut --skill bcut-release -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/JimLiu/baocut/tree/HEAD/.agents/skills/bcut-releaseFrom the publisher
This is the Electron v3 App (com.baocut.app). The older baocut-app skill is a
reference, not this checkout's executable workflow. Keep this developer skill
outside the App's craft skills/; do not invoke legacy GPUI/npm/Homebrew releases.
Load only the reference needed for the selected intent. Do not ask users to choose between the two release methods when they have not specified one: use tag release. Do not silently fall back to traditional packaging after an Actions failure. A specific local-only or platform-only instruction overrides the default all-platform scope; follow the user's explicit method and limits.
apps/desktop/package.json owns the App version. Synchronize root version and
lockfile through npm; do not bump Cargo or protocol versions for an App release.baocut.com/download/<id>, which follows GitHub Releases by itself. Do
not edit the READMEs or redeploy the site for a release; verify that baocut.com
serves the new build.After all selected platforms have published, public assets and feeds have passed read-back, and the consolidated release notes are verified, mark the newest stable desktop release Latest in GitHub's Releases tab:
gh release edit "$release_tag" --repo "$release_repo" --latest
gh api "repos/$release_repo/releases/latest" --jq '.tag_name'
Use the verified repository and tag for this task; the read-back must match that tag. Platform publishers preserve the previous Latest while validation and uploads are in progress, so this final step is required even when Actions succeeds. Local candidates, drafts and prereleases do not advance Latest. When continuing an older release, keep a newer published desktop version/build as Latest. Include the verified Latest tag in the completion report.
The desktop guide owns packaging mechanics; mode-specific references explain when to load it. Requests only to change release configuration must not create a release tag or publish.
Release BaoCut Electron desktop apps through GitHub Actions tags by default; use local/manual packaging only when explicitly requested. Also handles App version bumps, release continuation and portabl
---name: bcut-releasedescription: Release BaoCut Electron desktop apps through GitHub Actions tags by default; use local/manual packaging only…---# .agents/skills/bcut-release/SKILL.mdOverview
Release BaoCut Electron desktop apps through GitHub Actions tags by default; use local/manual packaging only when explicitly requested. Also handles App version bumps, release continuation and portable signing backups; excludes craft skills and legacy standalone CLI releases.
FAQ
Download .agents/skills/bcut-release/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/JimLiu/baocut.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.