Skip to main content

Documentation Index

Fetch the complete documentation index at: https://smithers.sh/llms.txt

Use this file to discover all available pages before exploring further.

Smithers is driven by an agent, not clicked by a human. You ask your coding agent for an outcome — “implement rate limiting and keep iterating until the tests pass” — and it reaches for Smithers, starts the workflow, watches it, and clears approvals on your behalf. These pages cover how to wire Smithers into each agent so it can do that. There are three integration surfaces. Most agents support more than one; pick the one that matches how the agent is extended.
SurfaceWhat it gives the agentShip it with
SkillFluency in Smithers — when to use it, the CLI verbs, the component catalog — loaded on demandskills add or a one-line curl
MCP serverStructured tools to list, run, watch, inspect, and control runs without shell-parsingmcp add or native MCP config
InstructionsA standing note in AGENTS.md / CLAUDE.md so the agent knows Smithers is availablea few lines in the repo

​
Two commands cover most agents

The Smithers CLI installs both the skill and the MCP server into every coding agent it detects on your machine — no per-agent config by hand. 
# Install the Smithers skill set into every detected agent
# (Claude Code, Codex, Cursor, Copilot, Gemini, OpenCode, Amp, Windsurf, …)
bunx smithers-orchestrator skills add

# Register Smithers as an MCP server in every detected agent
bunx smithers-orchestrator mcp add
Target a single agent with --agent, or scope to the current project with --no-global: 
bunx smithers-orchestrator mcp add --agent cursor
bunx smithers-orchestrator skills add --no-global   # writes .agents/skills in the repo
skills add generates a skill per CLI command group (smithers up, smithers ps, smithers approve, …) and installs them to the canonical ~/.agents/skills directory, symlinking into each agent that uses its own path (Claude Code → ~/.claude/skills, Windsurf → ~/.codeium/windsurf/skills, …). mcp add registers bunx smithers-orchestrator --mcp in each agent’s MCP config. Override the launch command with --command if Smithers is a project dependency.

​
The onboarding skill

The two commands above expose the CLI. The curated smithers onboarding skill goes further — it teaches the agent the mental model (Smithers as durable plan mode, the .smithers/ layout, which component to reach for) and ships the full docs bundle next to it so the agent can read the exact API on demand. 
mkdir -p ~/.claude/skills/smithers
curl -fsSL https://raw.githubusercontent.com/smithersai/smithers/main/skills/smithers/SKILL.md \
  -o ~/.claude/skills/smithers/SKILL.md
curl -fsSL https://smithers.sh/llms-full.txt \
  -o ~/.claude/skills/smithers/llms-full.txt
Any agent with a skills directory can host it — swap ~/.claude/skills for ~/.codex/skills, ~/.cursor/skills, ~/.agents/skills, and so on. See each agent’s page for the exact path.

​
Support matrix

AgentSkillMCP serverNotes
Claude Codeskills add / curlmcp add → ~/.claude.jsonAlso a Claude Code plugin (skill + MCP bundled)
Codexskills add → ~/.codex/skillsmcp add / config.toml (TOML)AGENTS.md for standing instructions
Cursorskills add → ~/.cursor/skillsmcp add / .cursor/mcp.jsonRules in .cursor/rules/*.mdc; cursor-agent CLI
GitHub Copilotskills add → ~/.copilot/skills.vscode/mcp.json (editor) / repo settings (cloud agent)Two distinct MCP schemas
Piskills add → ~/.pi/agent/skillsno native MCPFirst-party pi-plugin with a live run inspector — see Pi integration
Hermesskills addmcp add → ~/.hermes/config.yaml (YAML)Reads AGENTS.md
OpenClawskills add → ~/.agents/skillsmcp add → ~/.openclaw/openclaw.jsonSkills via ClawHub
skills add and mcp add also reach Gemini CLI, OpenCode, Amp, Windsurf, Cline, Continue, Roo, Kilo, Goose, Augment, Trae, Junie, Crush, Kiro, Qwen Code, OpenHands — run them once and any detected agent is wired up.
Pi, Hermes, and OpenClaw aren’t in the underlying skill/MCP framework’s built-in registry, so Smithers wires them as a supplementary step: mcp add writes the Smithers server into Hermes’s config.yaml and OpenClaw’s openclaw.json directly, and skills add copies the canonical skill set into Pi’s ~/.pi/agent/skills. Each respects --no-global, --agent, and --command, preserves existing config, and silently skips an agent that isn’t installed.

​
The other direction: Smithers runs the agent

Everything above is about an agent driving Smithers. Smithers also runs these agents as the workers inside a workflow — <Task agent={claude}> spawns Claude Code, <Task agent={codex}> spawns Codex, and so on, with native session hijack to take over interactively. That’s covered in CLI Agents and SDK Agents.

​
See also