chorus-docs

Answers Chorus product-usage questions by fetching live documentation from doc.chorus-ai.dev.

1.2k|104|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Chorus-AIDLC/Chorus --skill chorus-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chorus-docs
Source: https://github.com/Chorus-AIDLC/Chorus/tree/main/public/kiro-plugin/.kiro/skills/chorus-docs
Command: npx skills add https://github.com/Chorus-AIDLC/Chorus --skill chorus-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When users ask how to use, configure, deploy, or operate Chorus, AI agents often answer from stale memory. This Skill grounds every answer in the current published Chorus documentation by routing questions to the live docs site.

Core Features & Use Cases

  • Live Docs Routing: Fetches the machine-readable index at doc.chorus-ai.dev/llms.txt, then retrieves the relevant pages as raw Markdown by appending .md to page URLs.
  • Broad Coverage: Answers questions about UI workflow, agent and plugin setup (Claude Code, Codex, OpenClaw, Kiro, Pi), REST API and MCP surface, self-hosting deployment, and operations troubleshooting.
  • Localization Support: Serves docs in English, Chinese, Japanese, and Korean via path-prefixed pages, matching the user's language.
  • Use Case: A user asks how to create an API key and set agent permissions. The Skill fetches the index, pulls the agent-management guide as Markdown, and answers with a link to the human-facing page.

Quick Start

Ask how to set up a Chorus agent with specific permissions and have the answer grounded in the live Chorus documentation.

Frequently Asked Questions about chorus-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get accurate answers about Chorus setup and configuration?

Ask a product-usage question and the Skill fetches the live index at doc.chorus-ai.dev/llms.txt, then retrieves the matching page as raw Markdown. Answers are grounded in current published docs rather than model memory, with a link to the human-facing page.

What topics does Chorus documentation cover?

The docs cover UI workflow for the Idea to Proposal to Task pipeline, agent API keys and permissions, plugin setup for Claude Code, Codex, OpenClaw, Kiro, and Pi, the REST API and MCP tools, CDK-based deployment, and operations troubleshooting.

Does Chorus documentation support languages other than English?

Yes, pages are available in Chinese, Japanese, and Korean via path prefixes like /zh/, /ja/, and /ko/. The llms.txt index itself exists only at the root in English; locale prefixes apply to individual pages, and appending .md still works.

When should I use chorus-docs versus the Chorus workflow skills?

Use chorus-docs to learn how the product works or how to set it up. Use the workflow skills (chorus-idea, chorus-proposal, chorus-develop, chorus-review, chorus-yolo) to actually drive the AI-DLC pipeline such as claiming ideas or executing tasks.

Why does fetching zh/llms.txt return a 404 error?

The llms.txt index is a single unlocalized file that exists only at the root of doc.chorus-ai.dev. Localization applies to individual pages through path prefixes, not to the index, so always fetch the root index first.