Menu

Individual skill

scenario-workflow-authoring

0upvotes

Use when a task involves creating or editing a Scenario workflow graph through MCP: building an app from a brief, adding or rewiring nodes (models, prompts, approval gates, loops), authoring editor_info, publishing, unpublishing or renaming, importing an exported workflow JSON, migrating a graph built in Weavy, ComfyUI, or another node tool, copying a workflow, or turning a prompt chain into an app. Running or pricing a workflow is scenario-workflows. Keywords: node graph, editor_info, CEL.

skills/scenario-workflow-authoring/SKILL.md

Read pinned source

Source commit f29bf06ab89088695ed3431ac99d20a090441a2f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
3,675
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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](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,
Back to top