Workflow Run
- 648 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
workflow-run is a claude-flow workflow orchestration skill that executes, pauses, resumes, and cancels multi-step agent workflows for developers who need one-command MCP and native workflow lifecycle control.
About
workflow-run is a ruvnet/ruflo skill for running and managing workflows on two surfaces: claude-flow MCP persisted definitions and native .claude/workflows/*.js orchestrations via the Workflow tool. It calls workflow_execute, workflow_run, workflow_pause, workflow_resume, workflow_cancel, and workflow_status MCP tools, plus Read and Bash. Developers pass a workflow-id-or-name argument to trigger execution, monitor progress, and control lifecycle states. Use workflow-run when multi-step agent pipelines need pause/resume/cancel semantics instead of fire-and-forget single prompts. The skill unifies MCP workflow lifecycle management with Claude native JS workflow invocation in one entry point.
- Execute named workflows from any directory
- Supports sequential, parallel, and conditional execution patterns
- Integrates directly with Claude Code, Cursor, and other agent runtimes
- Real-time status tracking and error reporting
- Reusable workflow definitions stored as YAML or JSON
Workflow Run by the numbers
- 648 all-time installs (skills.sh)
- +10 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #369 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill workflow-runAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 648 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you run and pause claude-flow agent workflows?
Trigger, monitor, and orchestrate multi-step agent workflows with one command.
Who is it for?
Developers orchestrating multi-step claude-flow or native Claude JS workflows who need execute, pause, resume, and cancel from one skill.
Skip if: Developers running a single agent prompt without persisted workflow definitions or .claude/workflows/*.js orchestration files.
When should I use this skill?
User asks to run, pause, resume, cancel, or check status of an MCP workflow or .claude/workflows/*.js orchestration.
What you get
Executed workflow run, lifecycle status updates, and resumed or cancelled orchestration state
- workflow execution result
- lifecycle status report
By the numbers
- Controls 6 claude-flow workflow MCP actions: execute, run, pause, resume, cancel, status
Files
Workflow Run
Run and manage a workflow on either surface.
A — MCP workflow lifecycle
When you need to run a persisted definition and control its lifecycle (pause/resume/cancel):
1. Execute — call mcp__claude-flow__workflow_execute or mcp__claude-flow__workflow_run with the workflow ID 2. Monitor — call mcp__claude-flow__workflow_status to check progress and step outcomes 3. Pause — call mcp__claude-flow__workflow_pause to halt at the current step 4. Resume — call mcp__claude-flow__workflow_resume to continue from where paused 5. Cancel — call mcp__claude-flow__workflow_cancel to abort the workflow
Execution modes: sequential, parallel (independent steps), conditional (branch on outcome), manual gate (pause for human approval).
B — Native .claude/workflows/*.js
When you need a deterministic subagent fan-out, run a named native workflow with the Workflow tool. The named workflows are the meta.name of each .claude/workflows/*.js file (list them with /workflow or ls .claude/workflows/).
Workflow({ name: 'plugin-contract-audit' }) // run a named workflow
Workflow({ name: 'plugin-contract-audit', args: 'ruflo-agentdb' }) // pass args → the script's `args` global
Workflow({ scriptPath: '.claude/workflows/foo.js' }) // run a script by path
Workflow({ scriptPath, resumeFromRunId: 'wf_…' }) // resume — unchanged agent() calls return cachedNotes:
- A native workflow runs in the background; you are notified on completion (don't poll). Watch live progress with
/workflows. - Pause/resume here is journal-based (
resumeFromRunId), not the MCP state machine. Stop a run first, then resume from itsrunId. - To author a new native workflow, use the
workflow-createskill.
See ADR-0002.
Related skills
Agent BrowserGive their coding agent reliable, high-fidelity control over any website or Electron desktop app.591k39.6k
Lark ApprovalLet their AI coding agent create, read, update, and approve items in Lark (Feishu) approval workflows without leaving the coding environment.494kLark EventHandle Feishu/Lark bot events, webhooks, and subscription callbacks in agent-driven backend code.493kLark Workflow Meeting SummaryAutomatically generate structured meeting summaries and action items from Lark/Feishu calls without manual note-taking.492kLark Workflow Standup ReportAutomatically generate and post daily standup reports in Lark/Feishu from their workflow and activity data.492k
Twitter AutomationAutomate X/Twitter posts, scheduling, and engagement via X API integration441k669How it compares
Use workflow-run for persisted multi-step lifecycle control; single-shot agent prompts do not need workflow_execute or pause/resume tooling.
FAQ
What workflow surfaces does workflow-run support?
workflow-run manages claude-flow MCP persisted workflow lifecycles and invokes native .claude/workflows/*.js orchestrations via the Workflow tool. Both paths support execute and status monitoring.
Which lifecycle actions can workflow-run perform?
workflow-run calls claude-flow MCP tools for execute, run, pause, resume, cancel, and status. Developers pass a workflow ID or name to drive the full lifecycle from one skill.