Agent skill

Desktop Release

Cut and publish ryOS Electron desktop releases on GitHub. An agent skill from ryokun6/ryos.

AGPL-3.0Auto-check: notes

Install Desktop Release

skills CLI

$ npx skills add ryokun6/ryos --skill desktop-release -a claude-code

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

GitHub CLI

$ gh skill install ryokun6/ryos desktop-release --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/ryokun6/ryos.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/desktop-release .claude/skills/desktop-release && 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/

Paste into Claude Code

Install the "desktop-release" agent skill from https://github.com/ryokun6/ryos/tree/main/.cursor/skills/desktop-release into .claude/skills/desktop-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "desktop-release", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/ryokun6/ryos/tree/main/.cursor/skills/desktop-release

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add ryokun6/ryos --skill desktop-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install ryokun6/ryos desktop-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ryokun6/ryos.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/desktop-release .agents/skills/desktop-release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "desktop-release" agent skill from https://github.com/ryokun6/ryos/tree/main/.cursor/skills/desktop-release into .agents/skills/desktop-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "desktop-release", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add ryokun6/ryos --skill desktop-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install ryokun6/ryos desktop-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ryokun6/ryos.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/desktop-release .cursor/skills/desktop-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "desktop-release" agent skill from https://github.com/ryokun6/ryos/tree/main/.cursor/skills/desktop-release into .cursor/skills/desktop-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "desktop-release", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/ryokun6/ryos.git --path .cursor/skills/desktop-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add ryokun6/ryos --skill desktop-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install ryokun6/ryos desktop-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ryokun6/ryos.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/desktop-release .gemini/skills/desktop-release && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "desktop-release" agent skill from https://github.com/ryokun6/ryos/tree/main/.cursor/skills/desktop-release into .gemini/skills/desktop-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "desktop-release", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install ryokun6/ryos desktop-release

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add ryokun6/ryos --skill desktop-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/ryokun6/ryos.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/desktop-release .github/skills/desktop-release && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "desktop-release" agent skill from https://github.com/ryokun6/ryos/tree/main/.cursor/skills/desktop-release into .github/skills/desktop-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "desktop-release", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add ryokun6/ryos --skill desktop-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install ryokun6/ryos desktop-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ryokun6/ryos.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/desktop-release .opencode/skills/desktop-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "desktop-release" agent skill from https://github.com/ryokun6/ryos/tree/main/.cursor/skills/desktop-release into .opencode/skills/desktop-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "desktop-release", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: desktop-release
GitHub stars: 1.3k
Token cost: ~1k tokens
SKILL.md length: 359 words
Files: 1
Skills in repo: 10
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Cut and publish ryOS Electron desktop releases on GitHub. An agent skill from ryokun6/ryos.

Works in 2 steps: Versioned release (preferred) — push a… → Manual / dev build — workflow_dispatch…
The user asks to release the desktop app
SKILL.md covers Workflow, Release checklist, Standard release commands and Verify CI, plus 6 more sections
Calls git, gh and bun

What it does

Desktop Release is an agent skill from ryokun6/ryos. Cut and publish ryOS Electron desktop releases on GitHub. Covers bumping package.json version, tagging v, triggering Build Electron, and verifying the GitHub release. Use when the user asks to release the desktop app, bump the desktop version, trigger an Electron build, or publish macOS/Windows installers.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with GitHub, npm and macOS. The repository describes itself as: ryOS, made with Cursor. The licence is AGPL-3.0.

When your agent uses it

The user asks to release the desktop app
Bump the desktop version
Trigger an Electron build
Publish macOS/Windows installers

Example prompts

“/desktop-release”

Workflow steps

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

Versioned release (preferred) — push a tag matching v* (e.g. v1.0.9)
Manual / dev build — workflow_dispatch on main

What it can do on your machine

Read from SKILL.md and the folder at commit d68b815. 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:
- git
- gh
- bun
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, 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

Desktop Release loads about 1k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 359 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:98

re tagging (requires signing secrets in `.env.local` for mac):

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 ryokun6/ryos at commit d68b815, republished under its AGPL-3.0 licence (© ryokun6). 359 words, ~1,012 tokens.

Download SKILL.mdSave it as .claude/skills/desktop-release/SKILL.md (or your agent's skills folder).

name: desktop-release
description: Cut and publish ryOS Electron desktop releases on GitHub. Covers bumping package.json version, tagging v*, triggering Build Electron, and verifying the GitHub release. Use when the user asks to release the desktop app, bump the desktop version, trigger an Electron build, or publish macOS/Windows installers.

Desktop Release (Electron)

ryOS desktop builds are Electron artifacts published by GitHub Actions. The desktop app version lives in package.json (version field). Do not confuse it with the web app version in scripts/generate-build-version.ts / public/version.json — those are separate.

Workflow

Item	Location
CI workflow	`.github/workflows/build-electron.yml`
Builder config	`electron-builder.yml`
Build scripts	`bun run electron:build:mac`, `bun run electron:build:windows`
Output artifacts	`release/` (DMG, ZIP, NSIS, `latest-mac.yml`, `latest.yml`)

Triggers

Versioned release (preferred) — push a tag matching v* (e.g. v1.0.9)
- Builds macOS + Windows
- Publishes GitHub release ryOS v1.0.9 (tag = version)
- Sets release as latest
Manual / dev build — workflow_dispatch on main
- Republishes to the desktop tag (overwrites assets)
- Use for unsigned test builds, not semver releases

Release checklist

- [ ] 1. Confirm main is clean and up to date
- [ ] 2. Bump package.json version (semver, e.g. 1.0.8 → 1.0.9)
- [ ] 3. Commit and push to main
- [ ] 4. Create and push tag v{version} (must match package.json)
- [ ] 5. Verify Build Electron workflow started
- [ ] 6. Confirm GitHub release assets when CI completes

Standard release commands

Replace 1.0.9 with the target version.

bash

# 1. Bump version in package.json, then:
git add package.json
git commit -m "$(cat <<'EOF'
Bump desktop app version to 1.0.9.

EOF
)"
git push origin main

git tag v1.0.9
git push origin v1.0.9

Verify CI

bash

gh run list --workflow=build-electron.yml --limit 3
gh run watch   # optional: pass run ID from list output

When the run succeeds, check:

https://github.com/ryokun6/ryos/releases/tag/v1.0.9

Expected assets:

macOS: ryOS_{version}_aarch64.dmg, .zip, .zip.blockmap, latest-mac.yml
Windows: ryOS_{version}_x64.exe, .exe.blockmap, latest.yml

Manual workflow dispatch (no new tag)

Only when the user explicitly wants a desktop channel rebuild, not a semver release:

bash

gh workflow run build-electron.yml --ref main

This does not bump version. Artifacts land on the desktop release with overwrite.

Version rules

Bump only package.json version for desktop releases.
Tag name must be v + that version (1.0.9 → v1.0.9).
Check existing tags before choosing a version: git tag -l 'v1.0.*' and gh release list --limit 5.
Do not re-tag an existing release unless the user explicitly requests a rebuild of that version (requires deleting/moving the old tag — ask first).

Show full SKILL.md (128 more words)Show less

Git safety

Never force-push main or tags unless the user explicitly asks.
Do not commit unrelated files with the version bump.
Do not amend pushed commits.

Local builds (optional)

For local verification before tagging (requires signing secrets in .env.local for mac):

bash

bun run electron:build:mac      # signed + notarized when Apple env is set
bun run electron:build:windows

Local builds do not publish to GitHub. Production releases should go through the CI workflow.

CI secrets (reference)

macOS signed builds need GitHub Actions secrets documented in .github/workflows/build-electron.yml (APPLE_*, EVS_*). If CI fails on signing, inspect the workflow log — do not paste secret values.

When the user asks to "trigger a desktop build"

Ask for the target version if not stated (suggest next patch bump from latest tag).
Bump package.json, commit, push, tag, push tag.
Report the Actions run URL and expected release tag.

Files

Just SKILL.md in .cursor/skills/desktop-release of ryokun6/ryos.

Open the folder on GitHubat commit d68b815

Compare with similar skills

Desktop Release 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.

Desktop Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Desktop Release this skillryokun6/ryos	1.3k	—	~1k	Automated safety check: Notes	AGPL-3.0	today
OpenGUI Installer for DSHCore-Mate/OpenGUI	1.8k	—	~1.1k	Automated safety check: Pass	Custom licence	today
Release Allpaperboytm/spool	592	—	~1.1k	Automated safety check: Pass	Custom licence	2 mo ago
Releasemicrosoft/Huabu	157	—	~1.1k	Automated safety check: Pass	MIT	today
Deploykangraemin/claude-inspector	131	—	~739	Automated safety check: Notes	MIT	yesterday
Package Patch Releaseswjybky/deepwrite	586	—	~1.2k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

OpenGUI Installer for DSH
Core-Mate/OpenGUI
Installs and verifies the latest stable OpenGUI release in a DeepSeek Harness web profile on macOS without disturbing existing plugins or settings.
1.8k GitHub stars~1.1k tokensUpdated today
Agent WorkflowsAuto-check passed
Release All
paperboytm/spool
Publish the complete Spool CLI release train: synchronized versions, npm packages, the GitHub release, and the matching production web deployment.
592 GitHub stars~1.1k tokensUpdated 2 mo ago
DevOps & CloudAuto-check passed
Release
microsoft/Huabu
Official
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version.
157 GitHub stars~1.1k tokensUpdated today
DevOps & CloudAuto-check passed
Deploy
kangraemin/claude-inspector
Claude Inspector macOS 배포 스킬. An agent skill from kangraemin/claude-inspector.
131 GitHub stars~739 tokensUpdated yesterday
AI & LLM EngineeringAuto-check: notes
Package Patch Release
swjybky/deepwrite
为 DeepWrite 桌面端递增一个 SemVer 补丁版本，安全清理上一个版本的测试打包残留，使用项目规定的 pnpm pack:test 命令构建并验证新安装包，按用户要求决定是否创建并发布 GitHub Release；Release 完整可下载后更新根目录 update.json，并通过路径限定提交和推送，保证该提交只包含…
586 GitHub stars~1.2k tokensUpdated yesterday
DevelopmentAuto-check passed
Electron Builder
pedronauck/skills
Comprehensive guide for electron-builder (v26.x) packaging, code signing, auto-updates, and release workflows.
634 GitHub stars~2.7k tokensUpdated 24 days ago
MobileAuto-check passed

Questions about Desktop Release

What does Desktop Release do?

Cut and publish ryOS Electron desktop releases on GitHub. An agent skill from ryokun6/ryos. Desktop Release is an agent skill from ryokun6/ryos. Cut and publish ryOS Electron desktop releases on GitHub.

When should I use Desktop Release?

Desktop Release fits situations like: the user asks to release the desktop app; bump the desktop version; trigger an Electron build; publish macOS/Windows installers.

How do I install Desktop Release in Claude Code?

Run `npx skills add ryokun6/ryos --skill desktop-release -a claude-code`. Or copy the skill folder (.cursor/skills/desktop-release in ryokun6/ryos) into .claude/skills/desktop-release in your project. Claude Code loads it when a task matches its description.

How do I install Desktop Release in Codex?

Run `npx skills add ryokun6/ryos --skill desktop-release -a codex`. Or copy the skill folder (.cursor/skills/desktop-release in ryokun6/ryos) into .agents/skills/desktop-release in your project. Codex loads it when a task matches its description.

Can I use Desktop Release 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 ryokun6/ryos --skill desktop-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/desktop-release, .gemini/skills/desktop-release, .github/skills/desktop-release and .opencode/skills/desktop-release in your project.

What does Desktop Release need to run?

Going by SKILL.md and its folder, Desktop Release needs the command-line tools its instructions call (git, gh and bun).

Does Desktop Release access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Desktop Release safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Desktop Release use?

Desktop Release is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Desktop Release use?

About 1k tokens (SKILL.md is roughly 4k 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 Desktop Release?

Skills that share tags, products or a category with Desktop Release: OpenGUI Installer for DSH (Core-Mate/OpenGUI, 1.8k stars), Release All (paperboytm/spool, 592 stars), Release (microsoft/Huabu, 157 stars) and Deploy (kangraemin/claude-inspector, 131 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Desktop Release?

ryokun6 (a GitHub user) maintains it in ryokun6/ryos, which has 1,264 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 9, 2026.

Source: ryokun6/ryos on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Desktop Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Desktop Release (Electron)

Workflow

Triggers

Release checklist

Standard release commands

Verify CI

Manual workflow dispatch (no new tag)

Version rules

Git safety

Local builds (optional)

CI secrets (reference)

When the user asks to "trigger a desktop build"

Files

Compare with similar skills

Similar skills

More from ryokun6/ryos

Related

Questions about Desktop Release