dánwòdánwò

Coding agents

Set up your agent

Which files danwo writes for each coding agent, and how to add the skill and MCP server by hand.

danwo init sets up your agent for you. This page shows what it writes for each one, so you can check it, commit it, or do it by hand.

The quick way

Pass the agents you use to --skills, or pick them when danwo init asks:

npx @danwo/cli init --skills claude,cursor,codex,copilot

Each agent gets two things: the skill, a folder of instructions it reads, and the MCP server, an entry in its MCP config that starts npx @danwo/cli mcp. Running init again changes nothing, and your agents' other MCP servers are kept.

Each agent

Claude Code reads the skill from .claude/skills/danwo/ and the server from .mcp.json:

.mcp.json
{
  "mcpServers": {
    "danwo": { "command": "npx", "args": ["@danwo/cli", "mcp"] }
  }
}

danwo init --skills claude writes both. Open Claude Code in the project and approve the danwo server when it asks.

Where each file goes

AgentSkillMCP configWritten by init
Claude Code.claude/skills/danwo.mcp.jsonyes
Cursor.agents/skills/danwo.cursor/mcp.jsonyes
Codex.agents/skills/danwo.codex/config.tomlyes
GitHub Copilot (VS Code).agents/skills/danwo.vscode/mcp.jsonyes
Windsurf.agents/skills/danwo~/.codeium/windsurf/mcp_config.jsonskill only
Any other.agents/skills/danwoyour agent's MCP configskill only

Keep the skill current

The skill is copied from the @danwo/skill package. When you upgrade danwo, run danwo init again to refresh it.

If you've edited your copy of SKILL.md, init keeps your version and says so (kept). Delete it to take danwo's again.

Check it works

Ask your agent:

Use danwo to list this project's tests.

It should call the list_tests tool and answer with your test files. If it can't find the tool, restart the agent so it reloads its MCP config.

Next

On this page

Run it on every pull request

A GitHub check and one comment per pull request, with the flight records attached.

Set up CI