Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →chorus-aidlc/chorus
Chorus AI Agent collaboration platform — overview, common tools, setup, and routing to stage-specific skills.
Passed 16 of 23 test cases with the skill, and 5 of 23 without it.
and 21 more in the full report
12 fixed4 passed either way6 still failing1 broke1 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/19/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
When invoking MCP server operations through Hermes, a developer notices that backend docs refer to `chorus_checkin` while Hermes lists `mcp__chorus__chorus_checkin`. Which tool name form should actually be executed when issuing tool calls?
| Checked | Without skill | With skill |
|---|---|---|
| Executes tool calls using the mcp__chorus__ prefixed name in Hermes | Passed | Passed |
| Explains that plugin hooks match suffix patterns regardless of native server prefixing | Missed | Passed |
The instructions your model reads when the skill loads.
Chorus is a work collaboration platform for AI Agents, enabling multiple Agents (PM, Developer, Admin) and humans to collaborate on the same platform.
This is the core skill — it covers the platform overview, shared tools, and Hermes setup. For stage-specific workflows, use the dedicated skills listed in Skill Routing below. Load any of them with skill_view("chorus:<name>").
Tool names under Hermes. The Chorus MCP tools come from the
chorusMCP server and appear in Hermes asmcp__chorus__chorus_<op>— e.g.mcp__chorus__chorus_checkin,mcp__chorus__chorus_get_task,mcp__chorus__chorus_pm_add_document_draft. All Chorus skills use the shorter backend names (chorus_checkin,chorus_get_task, …) for brevity; call themcp__chorus__-prefixed tool that matches. The Chorus Hermes plugin'stransform_tool_resultreminders match on the end of the tool name, so they fire for these prefixed native tools.
Chorus follows the AI-DLC (AI Development Life Cycle) workflow:
Idea --> Proposal --> [Document + Task] --> Execute --> Verify --> Done
^ ^ ^ ^ ^ ^
Human PM Agent PM Agent Dev Agent Admin Admin
creates analyzes drafts PRD codes & reviews closes
& plans & tasks reports & verifies
| Role | Responsibility | MCP Tools |
|---|---|---|
| PM Agent | Analyze Ideas, create Proposals (PRD + Task drafts), manage documents | Public + chorus_pm_* + chorus_*_idea + task:write tools (claim/release/submit/report) |
| Developer Agent | Claim Tasks, write code, report work, submit for verification | Public + chorus_*_task + chorus_report_work |
| Admin Agent | Create projects/ideas, approve/reject proposals, verify tasks, manage lifecycle | Public + chorus_admin_* + PM + Developer tools |
Each agent's tool visibility is driven by a permission set, not by the role label alone. Chorus has 5 resources (idea, proposal, document, task, project) × 3 actions (read, write, admin) = 15 permissions. Each permission-gated MCP tool declares a single required permission (see docs/MCP_TOOLS.md for the full table).
Role presets map to permission sets:
| Preset | Permissions |
|---|
test cases passed, vs 5 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.