workflow-runner

Execute agency-orchestrator YAML workflows within Claude Code sessions.

2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/FelixBitSoul/contentCrew-AI --skill workflow-runner-felixbitsoul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-runner
Source: https://github.com/FelixBitSoul/contentCrew-AI/tree/main/.trae/skills/workflow-runner
Command: npx skills add https://github.com/FelixBitSoul/contentCrew-AI --skill workflow-runner-felixbitsoul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables executing agency-orchestrator YAML workflows directly inside Claude Code / OpenClaw / Cursor without requiring an API key, using the current LLM session as the execution engine.

Core Features & Use Cases

  • Orchestrates multi-role workflows by parsing a YAML workflow file and resolving role directories on demand.
  • Performs topological scheduling of steps, grouping steps into layers to enable safe, staged execution.
  • Supports per-step context passing by saving outputs into variables for downstream steps and providing robust error handling.
  • Suitable for automating complex product requirements, PRD reviews, and multi-agent content creation pipelines.

Quick Start

Provide a YAML workflow file and I will execute it step by step within the current session.

Frequently Asked Questions about workflow-runner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run multi-agent YAML workflows inside Claude Code or Cursor?

Run multi-agent YAML workflows inside Claude Code or Cursor by providing the YAML file to the session. The tool parses the file, resolves role directories, and uses the current LLM session as the execution engine without requiring an API key.

Do I need an API key to orchestrate multi-role workflows in my AI tool?

No API key is needed to orchestrate multi-role workflows. The system uses your current LLM session directly as the execution engine, parsing YAML inputs and resolving agent directories on demand to coordinate automated steps.

How does topological scheduling work for multi-agent workflow execution?

Topological scheduling groups workflow steps into sequential layers for safe, staged execution. This ensures dependencies are resolved correctly before downstream steps run, enabling per-layer execution and context-based variable passing.

What is the best way to automate complex PRD reviews using multi-agent collaboration?

Automate complex PRD reviews by defining a multi-agent YAML workflow with specific roles and steps. The orchestrator executes the pipeline topologically, passing context and outputs between agents to complete the review.

Can I pass context and variables between steps in an automated YAML workflow?

Yes, you can pass context and variables between steps in an automated YAML workflow. The system saves outputs from each step into variables, making them available for downstream steps while providing robust error handling.