メニュー
Install the local Smithers workflow pack into .smithers/. Pass an optional prompt to also launch the create-workflow builder after init. Run `smithers init --help` for usage details.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Drive Smithers, a durable control plane for long-running coding agents. Use when the user wants multi-step, long-running, crash-safe, or human-in-the-loop agent work: "orchestrate agents", "run a workflow", "implement this and review it", "keep iterating until tests pass", "plan then build", or anything that needs retries, approvals, replay, or evals across multiple AI steps. YOU (the agent) run Smithers on the user's behalf; it is not a GUI the human clicks. You are an ORCHESTRATOR: run long-running, multi-step, or background work *through* Smithers, not through your own ad-hoc subagents; spend your time observing the run and reporting.
Drive Smithers, a durable control plane for long-running coding agents. Use when the user wants multi-step, long-running, crash-safe, or human-in-the-loop agent work: "orchestrate agents", "run a workflow", "implement this and review it", "keep iterating until tests pass", "plan then build", or anything that needs retries, approvals, replay, or evals across multiple AI steps. YOU (the agent) run Smithers on the user's behalf; it is not a GUI the human clicks. You are an ORCHESTRATOR: run long-running, multi-step, or background work *through* Smithers, not through your own ad-hoc subagents; spend your time observing the run and reporting.
Query node/run lifecycle history by default; pass --raw for raw agent chunks and all event types. Run `smithers events --help` for usage details.
Output detailed run state. Structured output canonically uses nodes[].nodeId (legacy steps[].id remains for compatibility); --pool tallies attempt engine/model usage. Run `smithers inspect --help` for usage details.
Build a new Smithers workflow from a plain-English description. Dispatches to the create-workflow builder. Run `smithers init` first if the .smithers/ pack is not yet installed. Run `smithers make-workflow --help` for usage details.
Concise run health at a glance: verdict, node counts, agent/model mix, throughput, and the nodes gating progress. Run `smithers status --help` for usage details.
| name | smithers-init |
| description | Install the local Smithers workflow pack into .smithers/. Pass an optional prompt to also launch the create-workflow builder after init. Run `smithers init --help` for usage details. |
| requires_bin | smithers |
| command | smithers init |
Install the local Smithers workflow pack into .smithers/. Pass an optional prompt to also launch the create-workflow builder after init.
| Name | Type | Required | Description |
|---|---|---|---|
prompt | string | no | Optional plain-English task: after init, launch the create-workflow builder with this prompt pre-filled |
| Flag | Type | Default | Description |
|---|---|---|---|
--agent | string | Preferred coding agent id (e.g. claude, codex, pi). Skips the interactive agent question. | |
--tutorial | boolean | true | After install, open a hijacked tutorial session hosted by your preferred agent (interactive init only). Use --no-tutorial to skip. |
--force | boolean | false | Overwrite existing scaffold files |
--agentsOnly | boolean | false | Only create .smithers/agents/ and leave the rest of the workflow pack untouched |
--install | boolean | true | Run bun install inside .smithers/ after scaffolding (--no-install to skip) |
--addAgents | boolean | false | After scaffolding, launch the interactive agents add wizard to register one or more accounts. |
--skill | boolean | true | Install the curated smithers skill into your detected coding agents (Claude Code, Pi, Codex, OpenCode, Kimi, Amp, Antigravity) and, if a CLAUDE.md or AGENTS.md exists, append guidance on when to use smithers.sh workflows. Use --no-skill to skip. |
--global | boolean | false | Scaffold the global pack in ~/.smithers (honors SMITHERS_HOME) instead of ./.smithers. Global workflows run from any repo; a repo's local pack takes precedence. |
--updatePrompt | boolean | true | In an interactive terminal, when shipped pack files differ from the latest bundled version, ask which to update (warning when a shared component is selected). Use --no-update-prompt to skip the question. |
--template | unknown | Show next steps for a canonical starter template ID after init | |
--yes | boolean | false | Non-interactive: skip prompts and use defaults (safe for agents and CI). Alias: --non-interactive. |
--nonInteractive | boolean | false | Non-interactive: skip prompts and use defaults (safe for agents and CI). Alias: --yes. |
