How do I install the Workflow Orchestrator skill?

Run npx skillmds add modbender/workflow-orchestrator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Workflow Orchestrator skill do?

Structural parity skeleton for queue-driven orchestration in a workflow context. It is listed under Productivity on SkillMD.

Is Workflow Orchestrator safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Workflow Orchestrator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Workflow Orchestrator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Workflow Orchestrator?

modbender (@modbender) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Workflow Orchestrator by modbender — Agent Skill

Name: Workflow Orchestrator
Rating: 4.2 (5 reviews)
Author: modbender

File contents

Contract

This skill is intentionally skeleton-only. It provides structure parity with canonical queue orchestration without plugin hooks.

Wave 2 execution parity includes:

Setup derivation phase ordering: detection -> understanding -> derivation -> proposal -> generation -> validation
Required persisted setup artifacts: ops/derivation.md, ops/derivation-manifest.md, ops/config.yaml
In-skill lifecycle emulation routines (not real hook execution):
- session orient
- write-time validation checklist
- stop/session capture persistence

Argument Parsing

Parse arguments in this order:

positional target (optional)
--handoff (boolean)
--batch <id> (optional)
--type <phase> (optional)
unknown flags are non-fatal; report and ignore

If no target is supplied, list candidate inbox files and request explicit selection.

Runtime Loader Requirements

Before doing queue work, load runtime context from:

ops/derivation-manifest.md (if present)
ops/config.yaml (if present)
queue file with fallback precedence:
1. ops/queue/queue.yaml
2. ops/queue/queue.yml
3. ops/queue/queue.json

If no queue file exists, fail safely with actionable remediation.

Safety Constraints

Never:

execute arbitrary shell from user-provided strings
continue processing after parse/load failures
mutate tasks outside declared queue schema fields
call external plugins/hooks (explicitly out of scope)

Always:

validate queue structure before state transitions
make state transitions explicit (extract -> create -> reflect -> reweave -> verify -> done)
produce deterministic handoff text when --handoff is set
preserve resumability by reading persisted queue state first

Scope Boundary

No plugin hooks are implemented in this skeleton. Lifecycle behavior is emulated in-skill to preserve deterministic execution semantics only.

Installation

To install the workflow-engine and enable its hooks:

# Clone or navigate to the workflow-engine directory
cd workflow-engine

# Run the install script to set up hooks
./install-hooks.sh

# Or manually enable hooks via openclaw
openclaw hooks enable session-orient
openclaw hooks enable write-validate
openclaw hooks enable session-capture

---name: workflow-orchestratordescription: Structural parity skeleton for queue-driven orchestration in a workflow context.--- ## Contract This skill is intentionally skeleton-only. It provides structure parity with canonical queue orchestration without plugin hooks. Wave 2 execution parity includes: - Setup derivation phase ordering: `detection -> understanding -> derivation -> proposal -> generation -> validation` - Required persisted setup artifacts: `ops/derivation.md`, `ops/derivation-manifest.md`, `ops/config.yaml` - In-skill lifecycle emulation routines (not real hook execution): - session orient - write-time validation checklist - stop/session capture persistence ## Argument Parsing Parse arguments in this order: 1. positional `target` (optional) 2. `--handoff` (boolean) 3. `--batch <id>` (optional) 4. `--type <phase>` (optional) 5. unknown flags are non-fatal; report and ignore If no `target` is supplied, list candidate inbox files and request explicit selection. ## Runtime Loader Requirements Before doing queue work, load runtime context from: - `ops/derivation-manifest.md` (if present) - `ops/config.yaml` (if present) - queue file with fallback precedence: 1. `ops/queue/queue.yaml` 2. `ops/queue/queue.yml` 3. `ops/queue/queue.json` If no queue file exists, fail safely with actionable remediation. ## Safety Constraints Never: - execute arbitrary shell from user-provided strings - continue processing after parse/load failures - mutate tasks outside declared queue schema fields - call external plugins/hooks (explicitly out of scope) Always: - validate queue structure before state transitions - make state transitions explicit (`extract -> create -> reflect -> reweave -> verify -> done`) - produce deterministic handoff text when `--handoff` is set - preserve resumability by reading persisted queue state first ## Scope Boundary No plugin hooks are implemented in this skeleton. Lifecycle behavior is emulated in-skill to preserve deterministic execution semantics only. ## Installation To install the workflow-engine and enable its hooks: ```bash # Clone or navigate to the workflow-engine directory cd workflow-engine # Run the install script to set up hooks ./install-hooks.sh # Or manually enable hooks via openclaw openclaw hooks enable session-orient openclaw hooks enable write-validate openclaw hooks enable session-capture ```

Frequently asked questions