← ClaudeAtlas

wiro-workflowslisted

Design, save, run, test, repair and edit Wiro AI workflows, the saved chains of model steps with their own inputs and results, through the Wiro MCP tools or the REST API, alone or with the Workflow Agent. Use when the user wants a repeatable pipeline on Wiro (for example product photo to ad video, text to voice-over to captions), or asks to run, resume, clone, change or debug a Wiro workflow.
wiroai/Wiro-Plugin · ★ 0 · AI & Automation · score 72
Install: claude install-skill wiroai/Wiro-Plugin
# Wiro AI workflows A workflow is a saved graph of steps. Each step runs one Wiro model or one free built-in utility. The Start node holds the inputs people fill in, the End node lists the results, and the saved workflow runs again and again on new inputs. ## Choose the route first - One or two runs the user describes, such as an image and then a video of it: run the models one after the other with `run_model`, passing the first file URL to the next model. No workflow needed. - A chain the user will run again on new inputs: a workflow. Saving is free; each run pays for its model steps. - Let Wiro pick the models for a one-off creative job: Studio (`send_agent_message` with agent "studio"). - Work that should run by itself on a schedule or from a chat channel: a deployed agent (see the wiro-agents skill). - "Build me a workflow" means save it. Run it only when the user also asked for a run. With the Wiro MCP tools, read `get_playbook` with the topics "workflows" and "workflow-graph" before you build or edit, and "workflow-agent" before you message the Workflow Agent. They hold the full rules; this skill is the map. ## Find and read workflows - `list_workflows` with scope "mine" lists the workspace's workflows; scope "public" searches the gallery (by `search`, `tags` or `model`). - `get_workflow` returns one workflow: its Start fields (which ones a run must get), its End fields, the graph and its update time. - A workflow is named by its full slug: the slug plus a 5 chara