domains / families / agent-tooling / scenario-workflows

scenario-workflows

separate

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.

When to use

• listing workflows
• building workflow_run's inputs object
• pricing a run with a dry run
• approving or rejecting a stuck approval node
• handling runs rejected for input length
• managing workflows_list context flooding

When not to use

• creating or editing graphs

Skill page

Source