scenario-workflows
Use when a task involves running a Scenario workflow through MCP, including anything the user calls a Scenario app, a saved pipeline, or a multi-step generation graph.
Install / Use
npx skills add scenario-labs/skills --skill scenario-workflowsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of scenario-workflows
scenario-workflows scores 82/100 on our quality scale, 2319th of 2,790 Automation skills we index.
Its SKILL.md is 7.6 KB long, split into 7 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,048 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 29 days ago, so scenario-workflows is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-09. Automated pattern scan on 2026-11-09. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
scenario-workflows compared with similar skills
All 4 of these similar skills score higher than scenario-workflows; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| scenario-workflows (this skill)by scenario-labs | 82 | 1.0k | 29d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 48.0k | today | CLAUDE.md |
Frequently asked questions
- How do I install scenario-workflows?
- Run
npx skills add scenario-labs/skills --skill scenario-workflows. The install tabs above show the steps for each supported agent. - Which AI agents does scenario-workflows work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is scenario-workflows safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is scenario-workflows still maintained?
- The repository was last updated 29 days ago, so scenario-workflows is actively maintained.
Skill content
View source on GitHubname: scenario-workflows description: "Use when a task involves running a Scenario workflow through MCP, including anything the user calls a Scenario app, a saved pipeline, or a multi-step generation graph. Triggers include listing workflows, building workflow_run's inputs object, pricing a run with a dry run, approving or rejecting a stuck approval node, a run rejected for input length, or a workflows_list reply flooding the context. Creating or editing graphs is scenario-workflow-authoring. Keywords: workflow, app, approval gate." license: MIT
Scenario Workflows
Overview
A Scenario workflow is a saved node graph chaining several models into one call; users say "app" and
mean one whose status is ready. workflow_run returns a job tracked like any other generation.
Only workflows_list, workflow_get and workflow_run are listed by default; approve and reject
run through scenario_tools_search plus their executor lane. Connection and the core loop: the
scenario skill. Creating, editing and publishing graphs: the scenario-workflow-authoring skill.
If a sibling skill named here is missing from your available skills, load it with skill_get
(Scenario MCP) or ask the user to install it (https://github.com/scenario-labs/skills#install);
unattended, proceed from tool schemas and flag the gap.
Quick reference
| Step | Call | Notes |
| --------------------- | ------------------------------------------------- | ------------------------------ |
| 1. List | workflows_list status="ready" | Always cap limit |
| 2. Read the contract | list inputs[], get workflow.inputs_definition | name is the run key |
| 3. Price and validate | workflow_run with dry_run=true | Returns cost, creates no job |
| 4. Run | workflow_run with inputs | Returns a job |
| 5. Wait | jobs_wait | Re-call with pending_job_ids |
Ids are prefixed wflow_; copy them from workflows_list or search, never construct them. For a
named app or a public template, call search with target="workflows", a keyword query,
limit=3, and your scope; add public=true for the public catalog. Workflows support keyword text
and filters, not image or semantic search. To find ready apps, add the raw
filter: 'status = "ready"' (not filters.status). Read hits from workflows, then call
workflow_get on the chosen id and read the contract from workflow.inputs_definition: search
summaries contain neither the run inputs nor the editable graph. Search uses offset, not
page_token; heed any _hint on an empty page instead of repeating the same search.
Cap every list call
Each record carries the compiled flow and the whole editorInfo node graph, and the tool exposes
no compact flag: the two fields made up three quarters of the bytes in live records, which ran from
about 1,900 to 22,000 characters, and a draft with flow: [] still ships its editorInfo. Cap
limit at 3 or fewer, read only id, name, hasFlow and inputs, and page with page_token
set to the previous reply's nextPaginationToken, absent on the last page. The tool schema
advertised a ceiling of 200 at authoring time while the API rejects anything past 100 with a 400
naming pageSize and the range [1; 100], so the schema's maximum is not a value to send.
Only draft and ready filter server-side; other statuses filter each page client-side (flagged
_workflowListStatusFilter); there an empty page beside a nextPaginationToken means keep paging.
The input contract
workflow_run's inputs object is keyed by inputs[].name, taken verbatim from the record. Each
name is the id of the node behind it, so names can be positional (text2, text3), neither
contiguous nor ordered.
labelanddescriptioncarry the human intent, not the key.- Never harvest keys from
editorInfo.nodes[].data.name; node names go stale. requiredis an object: testrequired.always === true, a truthiness check reads{"always": false}as required too.- Inputs are typed:
string,file,file_array,string_array, more.filetakes an asset id (upload first). Match the type: the API drops scalar-for-array mismatches silently and still charges;workflow_runwraps simple scalars into arrays, but only simple ones. inputs[]is not the whole contract: a string input inherits the length ceiling of the node behind it (a model's own prompt cap, observed as low as 4000 characters), which the record never lists and which surfaces only at run time as a 400 quoting the cap but not the input key. The dry run enforces the same validator at zero cost: route long texts throughdry_run=trueand shorten to fit rather than retrying verbatim, and with several string inputs bisect with dry runs to find the offender.workflow_getwrapsinputs_definition/editor_infoinworkflow;workflows_listwrapsinputs/editorInfoinworkflows.
Worked example: run a saved app
workflows_listwithstatus="ready",limit=3, plusteam_idandproject_id. Readid,nameandinputsoff each record; ignoreflowandeditorInfo.- An
inputs[]entry{"name": "text1", "required": {"always": false}}runs with{"text1": "..."}. workflow_runwithworkflow_id,dry_run=true, and the fullinputsobject. The reply iscreativeUnitsCost,creativeUnitsDiscountand an emptyjob; quote the cost first. It also runs the real validator.- Repeat without
dry_run, thenjobs_waiton the returned job, re-calling withpending_job_idswhile it runs. asset_displayeach output asset, one per id.
Common mistakes
- Guessing input keys from labels or the node graph instead of reading
inputs[]. - Skipping the dry run: two of three ready workflows failed its validation with correctly named inputs; report that error, not the payload.
- Reading cost or attribution off the parent job: a finished workflow job bills
cuCost: 0and listsassetIdswith no per-model attribution. Every node ran as its own child job carrying the realcuCost(together they equal the dry-run quote, except inside aforEachloop, whose dry run prices one iteration), andjob_getverbose=trueon the workflow job returnsmetadata.flowmapping each node to its childjobId,modelIdand output asset ids. - Sending a batch through a
file_arrayinput and expecting one output per item: whether the app loops is in its graph, not its inputs. Look for aforEachnode ahead of the model ineditorInfo(for-eachin the compiledflow; theworkflows_listrecord carries both, orworkflow_get); without one, the app makes one generation from all the items, so callworkflow_runonce per item (each its own dry run and job). A looping app's dry run prices one iteration, so multiply its quote by the item count. - Running a draft:
flow: []andhasFlow: falsewhileinputslooks complete. Publishing: seescenario-workflow-authoring. - Calling
workflow_approveorworkflow_rejectwithout all three ofworkflow_id,workflow_job_idandnode_id: the gate is per node; a parked run never finishes on its own. Find the run withjobs_list, read it withjob_getverbose=true(compact replies omitmetadata):metadata.flowlists per-node statuses, the pending approval node's id isnode_id, the job's id isworkflow_job_id, itsworkflowIdtheworkflow_id. Reject cancels the run.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
48.0kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
