Agent Skills
› Chorus-AIDLC/Chorus
› chorus-cli
chorus-cli
GitHub提供 chorus CLI 的安装、配置及 MCP 操作指南，涵盖 agent 管理与环境连接，用于从 Shell 驱动 Chorus 服务。
Trigger Scenarios
需要安装或配置 chorus CLI
管理 coding agents 增删查改
通过命令行调用 Chorus MCP 工具
Install
npx skills add Chorus-AIDLC/Chorus --skill chorus-cli -g -y
SKILL.md
Frontmatter
{
"name": "chorus-cli",
"license": "AGPL-3.0",
"metadata": {
"author": "chorus",
"version": "0.17.0",
"category": "project-management",
"mcp_server": "chorus"
},
"description": "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."
}
chorus-cli — using the chorus CLI
chorus (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.
1. Install
npm install -g @chorus-aidlc/chorus # unpinned — always installs the latest
chorus --version # must be >= 0.17.0 (provides `chorus agents` + `chorus mcp`)
2. Configure agents — chorus agents
Agent configuration lives in ~/.chorus/daemon.json; chorus agents is the CRUD group:
chorus agents(orchorus agents list) — list configured agents (name, UUID, backend). The API key is never printed; the agent named byCHORUS_AGENT_PROFILEis 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 formerchorus init). Idempotent; safe to re-run.--helplists every flag.chorus agents remove <name|uuid>— remove a configured agent from~/.chorus/daemon.json(matched by UUID or name; an ambiguous name → use the UUID).
3. Connection environment variables
CHORUS_URL— the Chorus instance URL.CHORUS_API_KEY— an agent API key (cho_…).CHORUS_AGENT_PROFILE— optional name or UUID of the agent to act as. When set,chorus mcpresolves that agent's key from~/.chorus/daemon.json, so you need not exportCHORUS_API_KEYfor the CLI path. Daemon-woken sessions receive it automatically.
4. MCP operations — chorus mcp
Call any Chorus MCP tool from the shell — a byte-exact, token-free path for large content:
chorus mcp call <tool> ['<json>'] [--arg-file key=<file>] [--agent <name|uuid>]— call a tool.--arg-file content=<file>streams a file's raw bytes into the JSONcontentstring (no re-typing through the model). Identity resolves from--agent→CHORUS_AGENT_PROFILE→CHORUS_URL+CHORUS_API_KEY→ a single configured agent.chorus mcp whoami— print this agent's own UUID.chorus mcp list— list the tools this agent may call.
Requires chorus >= 0.17.0 (the chorus mcp subcommand). See chorus mcp --help.
Version History
- e147e86 Current 2026-09-03 10:41
