# The `smithers` agent skill

A drop-in [skill](https://docs.claude.com/en/docs/claude-code/skills) that teaches
your coding agent how to drive **Smithers** — the durable control plane for
long-running coding agents — without making it read the whole docs site first.

It exists to shorten the path to the aha moment: install it, ask your agent for
some multi-step or long-running work, and it reaches for Smithers on its own.

> **Your agent uses Smithers, not you.** Smithers is operated by an AI agent (Claude
> Code, Codex, …) on your behalf — it is not a GUI you click. This skill is what
> makes your agent fluent in it.

## What's in here

| File | Purpose |
|---|---|
| `SKILL.md` | The on-ramp the agent loads — what Smithers is, the 60-second loop, the mental model, how to operate runs. |
| `llms-full.txt` | The complete Smithers docs bundle, sitting next to `SKILL.md` so the agent can read the exact API on demand. Generated from the docs — do not edit by hand. |

## Install

`smithers init` auto-installs the curated onboarding skill into detected agents
whose skill directory Smithers can write directly today: Claude Code and Pi. To
sync the generated Smithers CLI skill set manually:

```bash
bunx smithers-orchestrator skills add
```

Use `--no-global` to scope the skill to the current project instead of the global
agent directory. `skills add` has no supported `--agent` target filter; use
`mcp add --agent <name>` when targeting one MCP integration.

For agents without a skills directory, point them at
`bunx smithers-orchestrator docs-full` (prints the same `llms-full.txt`), or
`bunx smithers-orchestrator ask "<question>"`.

## Keeping it fresh

`llms-full.txt` is generated by the repo root docs script, which writes
`docs/llms-full.txt`, optimizes it, and mirrors this bundled copy. Run
`pnpm docs:llms` after editing the docs so the bundles never drift.
