GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
Use only for stable/public Hermes Agent CN Desktop releases that should be visible to all users.
Install Desktop Release Sync Landing
$ npx skills add Eynzof/Hermes-CN-Desktop --skill desktop-release-sync-landing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Eynzof/Hermes-CN-Desktop desktop-release-sync-landing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Eynzof/Hermes-CN-Desktop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/desktop-release-sync-landing .claude/skills/desktop-release-sync-landing && rm -rf skills-srcUse ~/.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/
Install the "desktop-release-sync-landing" agent skill from https://github.com/Eynzof/Hermes-CN-Desktop/tree/main/.codex/skills/desktop-release-sync-landing into .claude/skills/desktop-release-sync-landing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "desktop-release-sync-landing", 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 install https://github.com/Eynzof/Hermes-CN-Desktop/tree/main/.codex/skills/desktop-release-sync-landingType 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.
$ npx skills add Eynzof/Hermes-CN-Desktop --skill desktop-release-sync-landing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Eynzof/Hermes-CN-Desktop desktop-release-sync-landing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Eynzof/Hermes-CN-Desktop.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/desktop-release-sync-landing .agents/skills/desktop-release-sync-landing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "desktop-release-sync-landing" agent skill from https://github.com/Eynzof/Hermes-CN-Desktop/tree/main/.codex/skills/desktop-release-sync-landing into .agents/skills/desktop-release-sync-landing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "desktop-release-sync-landing", 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.
$ npx skills add Eynzof/Hermes-CN-Desktop --skill desktop-release-sync-landing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Eynzof/Hermes-CN-Desktop desktop-release-sync-landing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Eynzof/Hermes-CN-Desktop.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/desktop-release-sync-landing .cursor/skills/desktop-release-sync-landing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "desktop-release-sync-landing" agent skill from https://github.com/Eynzof/Hermes-CN-Desktop/tree/main/.codex/skills/desktop-release-sync-landing into .cursor/skills/desktop-release-sync-landing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "desktop-release-sync-landing", 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 https://github.com/Eynzof/Hermes-CN-Desktop.git --path .codex/skills/desktop-release-sync-landing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Eynzof/Hermes-CN-Desktop --skill desktop-release-sync-landing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Eynzof/Hermes-CN-Desktop desktop-release-sync-landing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Eynzof/Hermes-CN-Desktop.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/desktop-release-sync-landing .gemini/skills/desktop-release-sync-landing && rm -rf skills-srcUse ~/.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/
Install the "desktop-release-sync-landing" agent skill from https://github.com/Eynzof/Hermes-CN-Desktop/tree/main/.codex/skills/desktop-release-sync-landing into .gemini/skills/desktop-release-sync-landing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "desktop-release-sync-landing", 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.
$ gh skill install Eynzof/Hermes-CN-Desktop desktop-release-sync-landingInstalls 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).
$ npx skills add Eynzof/Hermes-CN-Desktop --skill desktop-release-sync-landing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Eynzof/Hermes-CN-Desktop.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/desktop-release-sync-landing .github/skills/desktop-release-sync-landing && rm -rf skills-srcUse ~/.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/
Install the "desktop-release-sync-landing" agent skill from https://github.com/Eynzof/Hermes-CN-Desktop/tree/main/.codex/skills/desktop-release-sync-landing into .github/skills/desktop-release-sync-landing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "desktop-release-sync-landing", 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.
$ npx skills add Eynzof/Hermes-CN-Desktop --skill desktop-release-sync-landing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Eynzof/Hermes-CN-Desktop desktop-release-sync-landing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Eynzof/Hermes-CN-Desktop.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/desktop-release-sync-landing .opencode/skills/desktop-release-sync-landing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "desktop-release-sync-landing" agent skill from https://github.com/Eynzof/Hermes-CN-Desktop/tree/main/.codex/skills/desktop-release-sync-landing into .opencode/skills/desktop-release-sync-landing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "desktop-release-sync-landing", 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-sync-landing- GitHub stars
- 1.8k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 586 words
- Files
- 2
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Use only for stable/public Hermes Agent CN Desktop releases that should be visible to all users.
- Works in 7 steps: Treat package.json in this repository as… → Run the desktop checks that match the… → After the GitHub Release exists, get the… → …
- Other internal prereleases
- SKILL.md covers Overview, Prerelease Rule, Release workflow and Guardrails
- Calls pnpm, cargo and gh
What it does
Desktop Release Sync Landing is an agent skill from Eynzof/Hermes-CN-Desktop. Use only for stable/public Hermes Agent CN Desktop releases that should be visible to all users. Ensures the desktop repo version is synchronized and the separate landing repository updates its website version and https://desktop.hermesagent.org.cn/latest.json manifest for the same stable release. Do not use for rc, beta, alpha, canary, or other internal prereleases.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in DevOps & Cloud, covering Deployment. It works with Tauri, Rust and pnpm. The repository describes itself as: Hermes Agent CN desktop app, Windows-First, built with Tauri, Typescript and Rust. Isolated Hermes Agent core insides.
When your agent uses it
- Other internal prereleases
- Tasks that involve Deployment
Example prompts
- “/desktop-release-sync-landing”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Treat package.json in this repository as the desktop version source of truth. After changing it, run pnpm run version:sync and verify…
- Run the desktop checks that match the change, at minimum pnpm typecheck, pnpm test:unit, and cargo check. For release PRs also run cargo…
- After the GitHub Release exists, get the authoritative release and asset metadata with
- The human opens a separate branch for Eynzof/hermes-agent-cn-desktop-landing, for example codex/update-desktop-latest-json. The coding…
- In the landing repo, update the public release state for the same desktop version
- Validate the landing change with pnpm build. Also directly exercise the worker manifest path when possible
- The human commits and opens PRs for both repositories when both changed (the coding agent must not do this). Mention the landing PR from…
What it can do on your machine
Read from SKILL.md and the folder at commit 06e15d0. 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:
pnpmcargoghnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm 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 Sync Landing loads about 1.3k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 586 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 586 words (~1,276 tokens).
“Use this skill only when a stable/public desktop release is prepared, published, fixed, or documented. A stable release is not complete until the landing repository has been updated so /latest.json points at the same version and users can download the…”
- name
- desktop-release-sync-landing
Files
SKILL.md and 1 other file in .codex/skills/desktop-release-sync-landing of Eynzof/Hermes-CN-Desktop.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 06e15d0
Compare with similar skills
Desktop Release Sync Landing 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Desktop Release Sync Landing this skillEynzof/Hermes-CN-Desktop | 1.8k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Veloxdb Scalable Performanceveloxbase/veloxdb | 652 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Multi-AI Chat Launcherteddashh/multi-ai-chat-desktop | 152 | — | ~536 | Automated safety check: Pass | MIT | |
| Temps Plugingotempsh/temps | 831 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Deploy Release Testvercel/next.js | 143k | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Veloxdb Scalable Performance
veloxbase/veloxdb
Guides scalability and performance work for VeloxDB's Tauri + Rust PostgreSQL backend and React + TanStack frontend.
Multi-AI Chat Launcher
teddashh/multi-ai-chat-desktop
Audits, launches, checks and stops the Multi-AI Chat Tauri desktop app from a local source checkout, only when you explicitly ask.
Temps Plugin
gotempsh/temps
Design, build, test, and distribute external Temps plugins with TypeScript/Bun; provide development and local-testing guidance for existing Rust plugins.
- Official
Deploy Release Test
vercel/next.js
Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the teste2edeployrelease.yml GitHub Actions workflow.
Svelte Deployment
spences10/svelte-claude-skills
Svelte deployment guidance. An agent skill from spences10/svelte-claude-skills.
More from Eynzof/Hermes-CN-Desktop
Desktop Dual Repo Test
Eynzof/Hermes-CN-Desktop
A skill your agent uses when starting or verifying Hermes Agent CN Desktop with the latest Hermes-CN-Desktop and Hermes-CN-Core branches — dev smoke test (pnpm tauri:dev), packaged beta/release…
Project Structure
Eynzof/Hermes-CN-Desktop
A skill your agent uses when orienting within the Hermes Agent CN Desktop codebase, locating source files, understanding the Tauri+React architecture, finding Rust commands or frontend modules, or…
Desktop Release Preflight
Eynzof/Hermes-CN-Desktop
Use BEFORE preparing or publishing any Hermes Agent CN Desktop release (new installer, version bump, GitHub Release, or publishing a new build to users).
Related
Categories
Questions about Desktop Release Sync Landing
What does Desktop Release Sync Landing do?
Use only for stable/public Hermes Agent CN Desktop releases that should be visible to all users. Desktop Release Sync Landing is an agent skill from Eynzof/Hermes-CN-Desktop. Use only for stable/public Hermes Agent CN Desktop releases that should be visible to all users.
When should I use Desktop Release Sync Landing?
Desktop Release Sync Landing fits situations like: other internal prereleases; tasks that involve Deployment.
How do I install Desktop Release Sync Landing in Claude Code?
Run `npx skills add Eynzof/Hermes-CN-Desktop --skill desktop-release-sync-landing -a claude-code`. Or copy the skill folder (.codex/skills/desktop-release-sync-landing in Eynzof/Hermes-CN-Desktop) into .claude/skills/desktop-release-sync-landing in your project. Claude Code loads it when a task matches its description.
How do I install Desktop Release Sync Landing in Codex?
Run `npx skills add Eynzof/Hermes-CN-Desktop --skill desktop-release-sync-landing -a codex`. Or copy the skill folder (.codex/skills/desktop-release-sync-landing in Eynzof/Hermes-CN-Desktop) into .agents/skills/desktop-release-sync-landing in your project. Codex loads it when a task matches its description.
Can I use Desktop Release Sync Landing 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 Eynzof/Hermes-CN-Desktop --skill desktop-release-sync-landing -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-sync-landing, .gemini/skills/desktop-release-sync-landing, .github/skills/desktop-release-sync-landing and .opencode/skills/desktop-release-sync-landing in your project.
What does Desktop Release Sync Landing need to run?
Going by SKILL.md and its folder, Desktop Release Sync Landing needs the command-line tools its instructions call (pnpm, cargo, gh and node).
Does Desktop Release Sync Landing access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Desktop Release Sync Landing 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 Desktop Release Sync Landing use?
Desktop Release Sync Landing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Desktop Release Sync Landing use?
About 1.3k tokens (SKILL.md is roughly 5.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 Desktop Release Sync Landing?
Skills that share tags, products or a category with Desktop Release Sync Landing: GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Veloxdb Scalable Performance (veloxbase/veloxdb, 652 stars), Multi-AI Chat Launcher (teddashh/multi-ai-chat-desktop, 152 stars) and Temps Plugin (gotempsh/temps, 831 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Desktop Release Sync Landing?
Eynzof (a GitHub user) maintains it in Eynzof/Hermes-CN-Desktop, which has 1,750 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 21, 2026.
Source: Eynzof/Hermes-CN-Desktop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.