Skip to content

overview.mdx

Latest commit

 

History

History
32 lines (23 loc) · 2.57 KB

overview.mdx

File metadata and controls

32 lines (23 loc) · 2.57 KB
Raw
title Curated Workflows
description The workflow pack scaffolded by bunx smthrs init.

bunx smthrs init creates a focused .smithers/workflows/ directory with create-workflow and create-skill; hidden system workflows support init, failure autopsies, packs, evals, and upgrades. Specialized and former starter workflows remain available from packs and the source repository; monitoring stays smithers monitor and Gateway /monitor.

Run any curated workflow by ID:

bunx smthrs workflow run WORKFLOW_ID --prompt "..."

Most prompt-driven workflows accept --prompt as shorthand for --input '{"prompt":"..."}'; workflows with structured inputs also take --input directly.

Writing your own workflow? Read Workflow Authoring Rules first: five rules (reserved output columns, no nested loops, loop output binding, the renderWorkflow test contract, and .smithers/package.json test registration) that otherwise get learned one runtime failure at a time.

Workflows

Workflow Use it for
create-workflow Build a new Smithers workflow from a plain-English ask.
create-skill Author a new agent skill from a plain-English ask.

Operational Notes

  • Curated workflow files are user-owned after scaffold: bunx smthrs init won't overwrite edited files without --force.
  • Agent pools live in .smithers/agents.ts; edit it to change which models each workflow uses.
  • Run bunx smthrs workflow list for repo workflows, bunx smthrs workflow inspect WORKFLOW_ID for metadata and the input schema, and bunx smthrs workflow skills to generate agent-facing docs under .smithers/skills/.
  • Workflows can carry optional metadata comments (smithers-display-name, smithers-description, smithers-tags, smithers-aliases) for display/discovery in workflow list and workflow-skill.
  • Workflows marked system: true (or // smithers-system: true) are internal plumbing for Smithers' own durable processes (e.g. the seeded init workflow, which installs/refreshes the pack). They're hidden by default from workflow list, the interactive picker, MCP list_workflows, and gateway listWorkflows; pass --system (CLI), includeSystem: true (MCP), or filter.includeSystem (gateway RPC) to see them, then run with workflow run <id>.
  • Inspect and resume runs with the normal CLI (inspect, logs, chat, events, why, approve, up --resume), or watch every run live in the browser with bunx smthrs monitor (the Smithers Monitor).