Skip to main content
workflow-skill reads local Smithers workflow metadata and asks an agent to write concise skill documentation for selected workflows. It passes each workflow’s ID, display name, source type, entry file path, and full source to the agent. The agent infers descriptions, inputs, and other workflow-specific fields directly from the source. For deterministic, no-agent generation, use the CLI command. The generated skill includes the workflow’s real input schema: field names, types, required/default status, enum values, and descriptions when the Zod schema provides them. 
bunx smithers-orchestrator workflow skills
Inspect the same machine-readable contract without writing files: 
bunx smithers-orchestrator workflow inspect mission --format json
To generate skill docs through the agent (with prompt-driven customization), use: 
bunx smithers-orchestrator workflow run workflow-skill --input '{"workflow":"mission"}'

​
Inputs

InputTypeDefault
workflowstring"all"
outputstring or nullnull
promptstring""

​
Output Rules

  • workflow: "all" scans every local workflow except workflow-skill.
  • If output is omitted, skills are written under .smithers/skills/.
  • If workflow is one workflow ID and output is provided, the agent writes exactly that file path.
  • If workflow is "all" and output is provided, the agent treats it as a directory and writes one skill per workflow.

​
Examples

Generate one skill: 
bunx smithers-orchestrator workflow run workflow-skill \
  --input '{"workflow":"mission","output":".smithers/skills/mission.md"}'
Generate skills for every local workflow: 
bunx smithers-orchestrator workflow run workflow-skill \
  --input '{"workflow":"all","output":".smithers/skills"}'
Use this when you want coding agents to discover and operate project-specific Smithers workflows without reading each workflow source file first.