Skip to main content
Claude Code extends through skills, MCP servers, and plugins; Smithers ships into all three. Fastest path:
Syncs generated Smithers CLI skill files to Claude’s skill location and registers the MCP server in ~/.claude.json. Restart Claude Code (or run /mcp) to list, run, watch, and approve workflows.

Curated onboarding skill

Teaches Claude the Smithers mental model and ships the full docs bundle next to it. init installs it automatically when Claude Code is detected:
Claude loads a skill when its description matches the request. Once installed, ask for the outcome, “orchestrate an agent to add rate limiting and keep iterating until the tests pass”, and Claude reaches for Smithers itself.

Generated CLI skills

skills add syncs generated skill files for Smithers CLI command groups:
Pass --no-global to scope skill files to the project.

Register the MCP server

mcp add writes this for you. By hand, register a server with the Claude CLI:
Or commit a project-scoped .mcp.json so the whole team gets it:
The server exposes list_workflows, run_workflow, watch_run, list_pending_approvals, resolve_approval, explain_run, and more. Full reference: MCP Server. Claude Code CLI and MCP launches automatically persist Claude harness/session attribution when its native session environment is present. Supply an explicit --started-by-prompt (or MCP startedBy.prompt) only for deliberate launch context; it is never inferred from workflow input.

Claude Code plugin

A plugin bundles skill and MCP server into one install, namespaced smithers:. Manifest lives at .claude-plugin/plugin.json:
A sibling .claude-plugin/.mcp.json wires the MCP server; the skill auto-discovers from the plugin’s skills/ directory. Neither is declared in plugin.json itself. Install from a marketplace and reload without restarting:
Worked examples: plugin (skill) and plugin (orchestrator).

Standing instructions

Add a line to CLAUDE.md noting Smithers handles durable, multi-step work:

Smithers runs Claude Code too

Smithers also spawns Claude Code as a worker inside a workflow via ClaudeCodeAgent, with native session hijack:
This bills your Claude Pro/Max subscription by default: ClaudeCodeAgent clears ANTHROPIC_API_KEY from the spawned process, so the CLI uses subscription auth with no API key. For side-by-side subscriptions, set one up with CLAUDE_CONFIG_DIR=<dir> claude plus /login, then pass configDir: "<dir>"; apiKey switches to Anthropic API billing instead. Call it once for a typed completion with no graph:
See CLI Agents → Claude Code and Subscription-mode structured completion.