create-skill turns a plain-English description into a real, agent-facing
SKILL.md (plus any supporting files). It is the skill-authoring counterpart to
create-workflow: instead of hand-writing skill
docs, you describe what the skill should equip an agent to do and the workflow
clarifies it, designs the structure, scaffolds the files, and documents the result.
bunx smithers-orchestrator approve RUN_ID --node approve-design, or run
autonomously with --input '{"review":false}'.
Stages
- clarify: turn the freeform ask into a structured skill spec (purpose, when-to-use, capabilities, inputs).
- design: produce the concrete
SKILL.mdblueprint (frontmatter, body sections, supporting files). - approve-design: durable human approval gate (skippable via
review: false). - scaffold: write
SKILL.md(and any supporting files) under.smithers/skills/. - document: summarize what was created and where.
Inputs
| Input | Type | Default |
|---|---|---|
prompt | string | "Describe the agent skill you want to create, in plain English." |
name | string or null | null (the clarify/design steps choose a kebab-case id) |
review | boolean | true (pause for design approval before writing files) |
SKILL.md structure yourself.