scenario-workflow-authoring
Scenario Workflow Authoring
Overview
A workflow has two representations: editor_info (the editable node graph: nodes, edges, inputKeys) and flow (the compiled runnable form). Authoring through MCP means writing the whole editor_info document: there are no per-node editing tools; every change is a read, modify, write of the full graph through workflow_create or workflow_update. Never hand-write flow: workflow_publish compiles editor_info into it and flips status to ready. Editing a ready workflow's editor_info leaves the stale flow running until you publish again.
Read references/editor-info.md before writing any graph: it holds the node type vocabulary, the node choice doctrine (when an llm node is legitimate), the edge direction rule, per-node data contracts, and a validated minimal example. Create, update, publish, copy and delete live in the tool catalog (scenario_tools_search plus the matching executor, see the scenario skill). Running and pricing: the scenario-workflows skill. If a sibling skill named here is missing from your available skills, ask the user to install it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and flag the gap.
Quick reference
| Step | Call | Notes |
|---|---|---|
| 1. Study a graph | workflow_get on a working workflow |
Copy the shape, never ids |
| 2. Model contract | model_schema_get |
Handle names and required inputs |
| 3. Author | editor_info + inputs_definition |
Per the reference file |
| 4. Create | workflow_create |
Non-atomic, see below |
| 5. Publish | workflow_publish |
Compiles flow, needs input+output pins |
| 6. Validate | workflow_run with dry_run=true |
Prices and runs the real validator |