.smithers pack is small: it installs create-workflow and create-skill; system workflows stay hidden as durable plumbing. Specialized and former starter workflows live in installable packs and the source repository.
Canonical Packs
Pack Manifest (smithers.toon)
Every .smithers/ directory is a publishable pack; its manifest is
smithers.toon at the pack root. bunx smthrs init scaffolds one automatically
(contents starts empty on --agents-only runs), and re-init reports drift
like any other pack file. The format is
TOON, the same structured format the CLI
uses for agent-facing output.
A malformed manifest (bad TOON, missing
name, explicit null where a value is
required, or an unknown writes value) fails loudly rather than degrading:
optional fields may be omitted, not nulled.
Marketplace Metadata
Workflow packs should document:- workflow ID and display name
- required agents and tools
- required Gateway scopes
- input schema and example input
- expected outputs
- whether it writes files, opens pull requests, or needs approval
- recommended sandbox runtime
- validation command
Publishing Checklist
Before sharing a workflow pack:- Run the workflow on a disposable repository.
- Confirm every write path goes through approval or review when needed.
- Document the operator steps for non-coding teammates.
- Include a small example input and expected final output.
- Note which failures are safe to retry and which require human intervention.