workflow-runner

Execute agency-orchestrator YAML workflows in-session without an API key.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/zhuyingcoder/cc-demo --skill workflow-runner-zhuyingcoder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-runner
Source: https://github.com/zhuyingcoder/cc-demo/tree/main/.claude/skills/workflow-runner
Command: npx skills add https://github.com/zhuyingcoder/cc-demo --skill workflow-runner-zhuyingcoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Directly executing agency-orchestrator YAML workflows inside Claude Code / OpenClaw / Cursor without relying on an external API key, enabling seamless multi-role collaboration within a single conversation.

Core Features & Use Cases

  • Directly run agency-orchestrator YAML workflows in the current session using the LLM as the execution engine, eliminating API key setup and external tooling.
  • Supports multi-role collaboration by orchestrating roles defined in agency agents, reading role prompts, and assembling topological execution plans.
  • Automatically parses YAML workflows, resolves agent directories, collects required inputs, and preserves outputs for downstream steps across layers.

Quick Start

Provide a YAML workflow file to trigger the in-session workflow runner and obtain multi-role execution results.

Frequently Asked Questions about workflow-runner

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

FAQPage Schema
How do I run YAML workflows in Claude Code without an API key?

You can run YAML workflows in Claude Code without an API key by using an in-session runner that parses the YAML, resolves agent directories, and uses the LLM directly as the execution engine for multi-role collaboration.

What is multi-role orchestration and how does it work with YAML workflows?

Multi-role orchestration in YAML workflows involves parsing defined agent roles, building a topological execution plan by DAG layers, rendering role prompts, and executing steps sequentially while preserving outputs for downstream layers.

How do I trigger multi-role collaboration from a YAML workflow file?

To trigger multi-role collaboration, simply provide a YAML workflow file in your current session. The runner automatically parses the workflow, locates role directories, gathers required inputs, and assembles the execution plan.

Can I execute agency-orchestrator workflows inside Cursor or OpenClaw?

Yes, you can execute agency-orchestrator workflows inside Cursor or OpenClaw. The runner operates entirely in-session without external tooling, enabling seamless multi-role collaboration within a single conversation.

Do I need external tools or API keys to parse and execute YAML agent workflows?

No, you do not need external tools or API keys to parse and execute YAML agent workflows. The runner uses the current session's LLM to parse YAML, render role prompts, and execute DAG layers without any external dependencies.

How are inputs gathered and outputs saved across DAG layers in YAML workflow execution?

During YAML workflow execution, the runner collects required inputs before starting and automatically preserves outputs from each step, passing them downstream across DAG layers to ensure sequential multi-role tasks receive the correct data.