/workflow-run
Run a workflow — drive an MCP workflow lifecycle (execute/pause/resume/cancel) or invoke + resume a native .claude/workflows/*.js orchestration via the Workflow tool
$ npx -y skills add ruvnet/ruflo --skill workflow-run --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/workflow-run
Context preview
The summary Claude sees to decide when to auto-load this skill.
Run a workflow — drive an MCP workflow lifecycle (execute/pause/resume/cancel) or invoke + resume a native .claude/workflows/*.js orchestration via the Workflow tool
SKILL.md
workflow-run.SKILL.mdname: workflow-run
description: Run a workflow — drive an MCP workflow lifecycle (execute/pause/resume/cancel) or invoke + resume a native .claude/workflows/*.js orchestration via the Workflow tool
argument-hint: "<workflow-id-or-name>"
allowed-tools: mcp__plugin_ruflo-core_ruflo__workflow_execute mcp__plugin_ruflo-core_ruflo__workflow_run mcp__plugin_ruflo-core_ruflo__workflow_pause mcp__plugin_ruflo-core_ruflo__workflow_resume mcp__plugin_ruflo-core_ruflo__workflow_cancel mcp__plugin_ruflo-core_ruflo__workflow_status Workflow Read Bash
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__plugin_ruflo-core_ruflo__workflow_execute` or `mcp__plugin_ruflo-core_ruflo__workflow_run` with the workflow ID 2. **Monitor** — call `mcp__plugin_ruflo-core_ruflo__workflow_status` to check progress and step outcomes 3. **Pause** — call `mcp__plugin_ruflo-core_ruflo__workflow_pause` to halt at the current step 4. **Resume** — call `mcp__plugin_ruflo-core_ruflo__workflow_resume` to continue from where paused 5. **Cancel** — call `mcp__plugin_ruflo-core_ruflo__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 its `runId`.
- To author a new native workflow, use the `workflow-create` skill.
See [ADR-0002](../../docs/adrs/0002-native-workflow-orchestration.md).
Read more
name: workflow-run description: Run a workflow — drive an MCP workflow lifecycle (execute/pause/resume/cancel) or invoke + resume a native .claude/workflows/*.js orchestration via the Workflow tool argument-hint: "<workflow-id-or-name>" allowed-tools: mcp__plugin_ruflo-core_ruflo__workflow_execute mcp__plugin_ruflo-core_ruflo__workflow_run mcp__plugin_ruflo-core_ruflo__workflow_pause mcp__plugin_ruflo-core_ruflo__workflow_resume mcp__plugin_ruflo-core_ruflo__workflow_cancel mcp__plugin_ruflo-core_ruflo__workflow_status Workflow Read Bash
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__plugin_ruflo-core_ruflo__workflow_execute` or `mcp__plugin_ruflo-core_ruflo__workflow_run` with the workflow ID 2. **Monitor** — call `mcp__plugin_ruflo-core_ruflo__workflow_status` to check progress and step outcomes 3. **Pause** — call `mcp__plugin_ruflo-core_ruflo__workflow_pause` to halt at the current step 4. **Resume** — call `mcp__plugin_ruflo-core_ruflo__workflow_resume` to continue from where paused 5. **Cancel** — call `mcp__plugin_ruflo-core_ruflo__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 its `runId`.
- To author a new native workflow, use the `workflow-create` skill.
See [ADR-0002](../../docs/adrs/0002-native-workflow-orchestration.md).
An agent meta-harness for Claude Code and Codex. Agent = Model + Harness. The model writes; the harness gives it tools, memory, loops, sandboxes, and controls so it can actually work.
Repo: ruvnet/ruflo
Other skills on claude-flow.
- /agentdb-advanced
Master advanced AgentDB features including QUIC synchronization, multi-database management, custom distance metrics, hybrid search, and distributed systems integration. Use when building distributed AI systems, multi-agent coordination, or advanced vector search applications.
Open skill - /agentdb-learning
Create and train AI learning plugins with AgentDB's 9 reinforcement learning algorithms. Includes Decision Transformer, Q-Learning, SARSA, Actor-Critic, and more. Use when building self-learning agents, implementing RL, or optimizing agent behavior through experience.
Open skill - /agentdb-memory-patterns
Implement persistent memory patterns for AI agents using AgentDB. Includes session memory, long-term storage, pattern learning, and context management. Use when building stateful agents, chat systems, or intelligent assistants.
Open skill - /agentdb-optimization
Optimize AgentDB performance with quantization (4-32x memory reduction), HNSW indexing (150x faster search), caching, and batch operations. Use when optimizing memory usage, improving search speed, or scaling to millions of vectors.
Open skill - /agentdb-vector-search
Implement semantic vector search with AgentDB for intelligent document retrieval, similarity matching, and context-aware querying. Use when building RAG systems, semantic search engines, or intelligent knowledge bases.
Open skill - /agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination
Open skill

