Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →chorus-aidlc/chorus-cli
How to install, configure, and use the `chorus` CLI — install it, manage agents with `chorus agents` (add/remove/list), the connection environment variables, and MCP operations via `chorus mcp`. A concise shared reference for any flow that drives Chorus from the shell.
Passed 17 of 19 test cases with the skill, and 3 of 19 without it.
and 20 more in the full report
14 fixed3 passed either way2 still failing0 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
What is the recommended standard npm command to install or upgrade the global Chorus CLI package to ensure you always receive the newest available build?
| Checked | Without skill | With skill |
|---|---|---|
| The response provides npm install -g @chorus-aidlc/chorus as the installation command. | Missed | Passed |
| The response explains that installing without a version pin ensures the latest package version is retrieved. | Missed | Passed |
The instructions your model reads when the skill loads.
chorus CLIchorus (published as @chorus-aidlc/chorus) is the one command that configures this
machine's coding agents for Chorus and talks to the Chorus MCP endpoint from the shell.
This is a concise reference — run chorus --help and chorus <command> --help for the
full flag surface. On Hermes, run these commands with the terminal tool.
npm install -g @chorus-aidlc/chorus # unpinned — always installs the latest
chorus --version # must be >= 0.17.0 (provides `chorus agents` + `chorus mcp`)
chorus agentsAgent configuration lives in ~/.chorus/daemon.json; chorus agents is the CRUD group:
chorus agents (or chorus agents list) — list configured agents (name, UUID, backend).
The API key is never printed; the agent named by CHORUS_AGENT_PROFILE is marked.
chorus agents add [--agents <ids>] [--all] [--url <u>] [--api-key <cho_…>] [--yes] [--dsh-profile <name>]
— detect installed coding agents, install each one's Chorus plugin, and seed credentials
(this is the former chorus init). Idempotent; safe to re-run. --help lists every flag.
For Hermes, chorus agents add --agents hermes resolves the release tag to its commit SHA,
installs both Hermes plugin directories (chorus and chorus-mcp) pinned to it with
hermes plugins install … --ref <sha> --enable, and — when CHORUS_URL is not the loopback
default — writes the native mcp_servers.chorus entry into $HERMES_HOME/config.yaml
(literal <CHORUS_URL>/api/mcp URL, header kept as the Bearer ${CHORUS_API_KEY} placeholder).
A Hermes agent is stored as offline: its presence and wakes come from the plugin's own
hermes gateway connection, not the Chorus daemon.
chorus agents remove <name|uuid> — remove a configured agent from ~/.chorus/daemon.json
(matched by UUID or name; an ambiguous name → use the UUID).
chorus agents run --name <name|uuid> [--type <type>] [--] [agent args…] — launch a
configured agent's binary in the FOREGROUND with its Chorus connection injected into the
child only (CHORUS_URL / CHORUS_API_KEY / CHORUS_AGENT_PROFILE; nothing is exported to
the parent shell, and the key is never printed). Agent selection: single agent by default; else --name, else CHORUS_AGENT_PROFILE; ambiguous/none →
error. Backend defaults to the agent's stored agentType, overridable with --type.
Everything after -- is passed to the agent verbatim (never inspected). Type → binary:
claude-code/claude→claude, codex→codex, kiro→kiro-cli, pi→pi,
test cases passed, vs 3 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.