hermesone
Install, update, and manage the Hermes One desktop app via the `hermesone` npm package
Install / Use
npx skills add BankrBot/skills --skill hermesoneInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of hermesone
hermesone scores 90/100 on our quality scale, 1389th of 4,698 Development & Engineering skills we index (top 30%).
Its SKILL.md is 12 KB long, well organised into 17 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.
With 1,201 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so hermesone is actively maintained.
- Our last check on 2026-10-30 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
hermesone compared with similar skills
All 4 of these similar skills score higher than hermesone; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| hermesone (this skill)by BankrBot | 90 | 1.2k | 54d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
Frequently asked questions
- How do I install hermesone?
- Run
npx skills add BankrBot/skills --skill hermesone. The install tabs above show the steps for each supported agent. - Which AI agents does hermesone work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is hermesone safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is hermesone still maintained?
- The repository was last updated about 2 months ago, so hermesone is actively maintained.
Skill content
View source on GitHubname: hermesone
description: Install, update, and manage the Hermes One desktop app via the hermesone npm package. Use when a user wants to set up Hermes One, install or upgrade it from the command line, check the installed version, preview a release before installing, pin a specific version, or drive the installer programmatically from Node. Triggers on mentions of hermesone, Hermes One, Hermes Desktop (the former name), or installing/updating the Hermes app.
license: ISC
compatibility: Requires Node.js 18+ (built-in fetch) and network access to GitHub. Cross-platform — macOS (signed app, arm64/x64), Windows (setup.exe), Linux (.AppImage). The interactive UI needs a TTY; in non-interactive contexts it falls back to plain output. Works in Claude Code and any environment with a shell and npm.
metadata:
author: fathah
version: "0.2.0"
Hermesone: Install & Update Hermes One
hermesone (v0.2.0) is the npm package that installs and updates the Hermes One desktop app. It detects the host OS/arch, downloads the matching GitHub release, verifies its sha512 checksum, and installs it — on macOS the signed app goes straight into /Applications, ready to launch (no drag step). It ships a CLI and a programmatic API.
⚠️ This installs and runs third-party native code on the user's machine. The package mitigates this — it verifies every download against the publisher's sha512 manifest (and refuses to run an unverified build), and in an interactive terminal it asks for confirmation first — but installing software is still a host-level action. See Safety & approval.
- Homepage: https://hermesone.org
- Package repository: https://github.com/hermesonehq/hermesonejs
- App releases pulled from:
fathah/hermes-desktop(GitHub releases)
Naming: the app is Hermes One (formerly "Hermes Desktop"). The GitHub repo it's released from is still named
fathah/hermes-desktop, and the installed macOS bundle isHermes One.app— so you'll see both names. Use "Hermes One" with users; thehermes-desktopslug is just where the release assets live.
Why this lives in Bankr Skills. Hermes One is building toward an agent economy, with Bankr as the primary transaction layer for agent payments. This skill is the entry point: it gets Hermes One installed and current on the host so an agent can participate. Today the package does install/update/version only — no accounts, keys, or onchain actions. Bankr-settled transactions and agent-economy hooks are on the roadmap and will be documented here as they ship.
Safety & approval
Installing or updating Hermes One modifies the host. The package enforces two guardrails for you: it verifies sha512 before installing (fail-closed — it refuses if no published checksum is found), and on an interactive terminal it shows a confirmation prompt with the release, size, and checksum status. Still follow these rules:
- Require explicit user approval before any install or update. Never trigger one as a silent side effect of another task or an autonomous workflow.
- In non-interactive/agent contexts the confirm prompt is skipped (and
--yesdoes the same). There, you are the approval gate: runhermesone planfirst, show the user the resolved release/asset/size/sha512, get a yes, then runinstall. - Don't override verification. Only set
HERMESONE_ALLOW_UNVERIFIED=1if the user explicitly accepts installing a build with no published checksum. - Pin what you install (
@0.2.0for the package; a release tag for the app) when reproducibility matters — see Pinning.
Recommended flow
Installing the npm package no longer installs the app as a side effect (see Postinstall behavior). The clean path is: install the CLI, preview, then install on confirmation.
# 1. Install the CLI (no host change — the app is not installed yet).
npm install -g hermesone@0.2.0
# 2. Preview the exact release that would be installed.
hermesone plan
# 3. Install. Interactive terminals show a confirmation prompt + live progress;
# non-interactive contexts proceed (add --yes to be explicit) and print plain lines.
hermesone install
hermesone update is safe to run repeatedly — it no-ops when already current and only downloads when a newer release exists.
Preview a release
hermesone plan [tag] resolves and prints what would be installed — release tag, asset, size, and the expected sha512 — without downloading or installing anything. Use it to show the user before asking them to approve an install.
CLI reference
hermesone <command> [tag]
| Command | Description |
| ---------------- | ------------------------------------------------------------------------------------ |
| install [tag] | Download, verify (sha512), and install Hermes One — latest, or a pinned release tag. |
| update [tag] | Update Hermes One if a newer release is available (no-op when current). |
| plan [tag] | Show what would be downloaded (tag, asset, size, expected checksum). No changes. |
| version | Print the installed Hermes One version, or a "not installed" message. |
| help | Show usage. |
| Flag / Env | Effect |
| ------------------------------ | ---------------------------------------------------------------------------- |
| -y, --yes | Skip the confirmation prompt (for non-interactive/scripted installs). |
| HERMESONE_VERSION=<tag> | Pin the release tag (same as the [tag] argument). |
| HERMESONE_ALLOW_UNVERIFIED=1 | Proceed even if no published checksum is found. Not recommended. |
In an interactive terminal, install renders a confirmation box, a live download progress bar, and per-step status (resolve → download → verify → install). In a non-interactive context it prints plain status lines and never blocks. Color honors NO_COLOR.
What gets installed per OS
| OS | Artifact | Behavior |
| ------- | -------------------- | ------------------------------------------------------------------------------------------------- |
| macOS | *-mac.zip (signed) | Verified, unzipped, installed into /Applications (or ~/Applications), then launched — no drag. Updates replace in place. |
| Windows | *-setup.exe | Verified, then the installer is launched. |
| Linux | *.AppImage | Verified, marked executable, then launched. |
Pin a specific release
install/update use the latest release by default. To install a known build, pass a tag or set the env var:
hermesone install v0.6.35
HERMESONE_VERSION=v0.6.35 hermesone install
Checksum verification (built in)
Each download is verified against the base64 sha512 published in the release's electron-builder manifest (latest-mac.yml / latest.yml / latest-linux.yml). On mismatch the file is deleted and nothing is installed. If a release publishes no checksum for the asset, install refuses unless HERMESONE_ALLOW_UNVERIFIED=1 is set. You do not need to verify manually — surface the result from plan to the user and let the package enforce it.
Programmatic API
import { plan, install, update, getInstalledVersion } from "hermesone";
// Preview without downloading — show this to the user for approval.
const p = await plan(); // { tag, asset, url, size, sha512 }
// Install (verifies sha512 before installing). Optionally pin a tag, and/or
// subscribe to progress events to render your own UI.
await install({
tag: "v0.6.35",
onProgress: (e) => console.log(e.phase), // resolve|download|verify|extract|launch|installed...
});
await update(); // no-op if already current
const current = await getInstalledVersion(); // e.g. "0.6.35", or null
Also exported: fetchRelease, parseChecksums, selectAsset, getTarget, isNewer, and types Release, ReleaseAsset, State, Target, InstallOptions, InstallPlan, ProgressEvent. The library prints nothing on its own — all output is driven by your onProgress handler.
Version tracking
- The installed version is detected from the app on disk first. On macOS this reads
CFBundleShortVersionStringfromHermes One.app/Contents/Info.plist(/Applicationsand~/Applications), so manual installs are recognized too. - Otherwise it falls back to
~/.hermesone/state.json, written after each install/update done through this tool. versionreturnsnull(CLI prints "Hermes One is not installed.") when neither source yields a version.
Postinstall behavior
npm install hermesone does not download or launch the app — running an installer as a silent side effect of npm install is surprising, so it's opt-in. After installing the package it prints the next step (npx hermesone install). Controls:
| Env (set before npm install) | Effect |
| ------------------------------ | ---------------------------------------------------------------- |
| (none) | Prints guidance; does not install the app. |
| HERMESONE_AUTO_INSTALL=1 | Runs the install automatically during postinstall. |
| HERMESONE_SKIP_INSTALL=1 | Silences the postinstall notice entirely. |
Troubleshooting
| Symptom | Cause / fix |
| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| No published checksum found for <asset> | The release has no sha512 manifest entry for this asset. Prefer a release that does; only override with HERMESONE_ALLOW_UNVERIFIED=1 if the user accepts it. |
| Checksum mismatch for <asset> | The download didn't match the published sha512 — the file was deleted and nothing installed. Retry; if it persists, the release/asset may be compromised or corrupted. |
| Failed to fetch release ...: 403 | GitHub API rate limit (unauthenticated). Wait and retry. |
| No Hermes One build available for <platform>/<arch> | The release has no asset for this OS/arch. Check the releases page. |
| Prompt didn't appear / it just proceeded | Not a TTY (CI, pipe, agent). That's expected — it runs non-interactively. Use plan first to gate, or --yes to be explicit. |
| version says not installed after a manual install | Only macOS auto-detects from disk. On Windows/Linux, install once via this tool so ~/.hermesone/state.json is written. |
Notes & guardrails
- Host-level code execution. Install/update download a native build from
fathah/hermes-desktopand run it. The package verifies sha512 and (interactively) prompts, but only run it on explicit user intent — never automatically from an agent workflow. -
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
