scenario-workflow-authoring SKILL.md skillA
scenario-workflow-authoring from scenario-labs/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add scenario-labs/skills/scenario-workflow-authoring@git:20261003.c80bae9Pins git:20261003.c80bae9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- scenario-labs/skills
- Path
skills/scenario-workflow-authoring/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261003.c80bae9, committed Oct 3, 2026
- First version recorded
- Aug 16, 2026
- Size
- 7,692 bytes
- Repository stars
- 1,063
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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, copy and delete live in the tool catalog (`scenario_tools_search` plus the matching executor, see the `scenario` skill). `workflows_list`, `workflow_get` and `workflow_run` are direct tools: scope and `dry_run` go in their top-level arguments, never an executor wrapper. Running and pricing: the… …
Read the whole file at its exact version.
How to install
mdr add scenario-labs/skills/scenario-workflow-authoring@sha256:c19930327fef4304The line at the top of this page pins the label git:20261003.c80bae9, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5nrmltkq2afkxxkv)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 16, 2026 and Oct 3, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261003.c80bae9 latest | 2026-10-03 | c80bae9 | 7,692 B | A | view · diff |
| git:20260924.7c0355f | 2026-09-24 | 7c0355f | 6,482 B | A | view · diff |
| git:20260924.1bf9582 | 2026-09-24 | 1bf9582 | 6,198 B | A | view · diff |
| git:20260917.e79a388 | 2026-09-17 | e79a388 | 5,897 B | A | view · diff |
| git:20260816.cc146d8 | 2026-08-16 | cc146d8 | 5,005 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7692 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
scenario-labs/skills · 1,063 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5nrmltkq2afkxxkv GET https://markdownregistry.com/api/v1/resolve?ref=scenario-labs/skills/scenario-workflow-authoring GET https://markdownregistry.com/api/v1/blob/c19930327fef43047a636071ef3fe225ddbd4c4c27e1bf6fa84bafe64f90608f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.