extract-skill is an archived example, not installed by init. Copy it from examples/init-pack/ with its dependency closure, or ask create-workflow to build an equivalent.
extract-skill looks back at a run (or a pattern you describe) and harvests the
durable, reusable part: an agent skill doc, a sketch for a new workflow, and
memory facts worth keeping. Reach for it right after a run, when you notice
yourself doing the same thing again.
targetRunId to let the analysis read the real run state (bunx smithers-orchestrator inspect,
events, node); leave it null to harvest purely from the prompt and
context.
Stages
- analyze: read the run (if given) and decide what’s worth harvesting: the repeated pattern, whether it’s skill- and/or workflow-shaped, and any durable memory facts.
- propose: draft concrete proposals: a skill (name, description, body), a workflow sketch (id, sketch), and memory facts to persist.
- scaffold-skill: when the pattern is reusable as a skill, write the proposed skill doc to
.smithers/skills/<name>.md.