release
Skill33 starsChanged 34 days agoMITView on GitHub
Prepare, authorize, publish, troubleshoot, and verify Cursor BYOK desktop GitHub Releases. Use for version bumps, release tags, GitHub Actions release runs, updater manifests, signing, or release-readiness checks.
193 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- yicheng47/runnertheir own version, first seen Nov 13, 2026
- eugene1g/agent-safehousetheir own version, first seen Nov 12, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Nov 11, 2026
- cubeplexai/cubeplextheir own version, first seen Nov 10, 2026
- bex-co/bextheir own version, first seen Nov 10, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
rivet-devSkilllaunch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- leookun/cursor-byok★ 3.2k89% same
Wrote their own version · 192
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- AmruthPillai/Reactive-Resume★ 45ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
182 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cursor-prefix-stabilitySkill
- database-schemaSkill
- floating-uiSkill
- frontendSkill
- i18nSkill
- model-selectionSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 4 are distinctive, and 14 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Only the repository author, GitHub user haxsd, may authorize a live release.
- Very specific: line 13
Before any live mutation, require an explicit release instruction from the author in the current task and verify the authenticated GitHub …
- Very specific: line 14
Treat all of these as publication actions: pushing a v* tag, rerunning the release workflow, and publishing or editing a GitHub Release.
- Very specific: line 16
Never print, commit, or upload .tauri/cursor-byok.key anywhere except the repository's TAURI_SIGNING_PRIVATE_KEY Actions Secret when the …
- Distinctive: line 17
Never delete, replace, or move an existing tag or published Release without separate explicit authorization.
- Very specific: line 21
Do not use GitHub prereleases.
- Very specific: line 22
Use haxsd-byok-vMAJOR.MINOR.PATCH for a stable tag, for example haxsd-byok-v0.1.0.
- Very specific: line 23
Use standard SemVer haxsd-byok-vMAJOR.MINOR.PATCH-beta.N for a test tag, for example haxsd-byok-v0.1.0-beta.1.
- Very specific: line 27
Keep ordinary main pushes and manual workflow dispatch disabled as release triggers.
- Distinctive: line 28
Never republish an already published version.
- Distinctive: line 32
Keep the desktop version identical in the manifests and their locks:
- Very specific: line 66
Use the tauri-action@v1 input uploadUpdaterJson: true.
- Distinctive: line 70
After the author explicitly authorizes publication:
- Very specific: line 72
Commit only the reviewed release set and push it to main.
- Very specific: line 73
Create the matching tag on that commit, for example haxsd-byok-v0.1.0-beta.1, and push only that tag.
- Very specific: line 74
Follow the triggered Release desktop app run through completion.
- Very specific: line 75
Verify haxsd-byok-v<version> exists, is published rather than draft, has prerelease: false, and is the repository's Latest release.
- Very specific: line 76
Verify the Release contains the signed NSIS installer, its .sig, and latest.json (three assets, matching v1.1.0 onwards).
“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Desktop release
Release through .github/workflows/release.yml. The pipeline ships one updater format: Tauri's latest.json (the legacy update.json is no longer produced).
Publication authority
- Only the repository author, GitHub user
haxsd, may authorize a live release. - Before any live mutation, require an explicit release instruction from the author in the current task and verify the authenticated GitHub identity is
haxsd(the release workflow re-checksGITHUB_ACTOR == github.repository_owner, so a wrong account cannot publish). - Treat all of these as publication actions: pushing a
v*tag, rerunning the release workflow, and publishing or editing a GitHub Release. Pushing a release commit tomainonly prepares the release and must never trigger publication by itself. - Without that authorization, restrict work to inspection, local edits, validation, and a release-ready commit or branch. Do not infer publication permission from requests such as “prepare”, “check”, or “ready to release”.
- Never print, commit, or upload
.tauri/cursor-byok.keyanywhere except the repository'sTAURI_SIGNING_PRIVATE_KEYActions Secret when the author explicitly requests that secret configuration. - Never delete, replace, or move an existing tag or published Release without separate explicit authorization.
Version and GitHub Release policy
- Do not use GitHub prereleases. Keep
prerelease: falsefor every release and publish the completed release as Latest. - Use
haxsd-byok-vMAJOR.MINOR.PATCHfor a stable tag, for examplehaxsd-byok-v0.1.0. - Use standard SemVer
haxsd-byok-vMAJOR.MINOR.PATCH-beta.Nfor a test tag, for examplehaxsd-byok-v0.1.0-beta.1. A beta is still a normal GitHub Release, not a GitHub prerelease. Make its title or body visibly say Beta. - This normal-Release rule is required because both installed update clients resolve assets through GitHub's
/releases/latest/download/path, which excludes GitHub prereleases. - Windows beta builds must use the NSIS bundle. WiX/MSI rejects nonnumeric prerelease identifiers such as
beta.1; do not weaken the SemVer tag to accommodate MSI. - Release only from a
haxsd-byok-v*tag whose commit is contained inorigin/main. The tag must equalhaxsd-byok-v<version>from the desktop manifests. - Keep ordinary
mainpushes and manual workflow dispatch disabled as release triggers. The author pushes the matching tag only after the release commit is present onorigin/main. - Never republish an already published version. Select a new version instead.
Release sources
Keep the desktop version identical in the manifests and their locks:
cursor-byok/
├── Cargo.lock
├── apps/desktop/
│ ├── package.json
│ ├── package-lock.json
│ └── src-tauri/
│ ├── Cargo.toml
│ └── tauri.conf.json
├── scripts/cursor-proto/proto/
│ ├── agent_v1.proto
│ └── aiserver_v1.proto
└── .github/workflows/release.ymlThe two listed Proto files are required build inputs and must be committed. Keep the other locally extracted Proto files ignored unless the build starts depending on them.
Prepare and validate
- Inspect
git status, fetchorigin/main, and preserve unrelated user changes. Confirm the release commit is based on the current remote head. - Choose stable or beta numbering explicitly. Update the desktop version in both manifests and lockfiles; do not change the independent
cursor-serverversion merely to release the desktop app. - Confirm the updater public key in
tauri.conf.jsonmatches.tauri/cursor-byok.key.pubwithout exposing the private key. - Confirm
TAURI_SIGNING_PRIVATE_KEYexists in GitHub Actions.TAURI_SIGNING_PRIVATE_KEY_PASSWORDmust be absent when the local key has no password. - Confirm neither the intended tag nor Release already exists.
From
apps/desktop, run:npm run check npm run tauri:build -- --debug --no-bundle- Validate the workflow YAML and inspect the staged diff. Ensure
.tauri/, unrelated local files, and unrelated user changes are not staged. - Use the
tauri-action@v1inputuploadUpdaterJson: true;includeUpdaterJsonis not a valid v1 input.
Publish and verify
After the author explicitly authorizes publication:
- Commit only the reviewed release set and push it to
main. Confirm the release commit is present inorigin/main; this push must not start the release workflow. - Create the matching tag on that commit, for example
haxsd-byok-v0.1.0-beta.1, and push only that tag. This tag push is the publication trigger. - Follow the triggered
Release desktop apprun through completion. Report the run URL and stop on failure; diagnose locally before asking the author to authorize another live attempt. - Verify
haxsd-byok-v<version>exists, is published rather than draft, hasprerelease: false, and is the repository's Latest release. - Verify the Release contains the signed NSIS installer, its
.sig, andlatest.json(three assets, matching v1.1.0 onwards). - For a beta, report clearly that it is a test version even though GitHub represents it as a normal Latest Release.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

