workflow-runner

To run multi-role YAML workflows inside your chat session, provide a .yaml workflow file or inline workflow definition, and the active LLM executes it as the engine for multi-role collaboration without requiring an API key.

Topological scheduling for multi-role agent coordination is an automated workflow planning mechanism that sequences layered prompts to ensure correct execution order across multiple roles defined in your YAML workflow.

No, you do not need an API key to execute agency-orchestrator YAML workflows because the skill uses the active LLM in your current chat session as the execution engine for all multi-role agent prompts.

The skill discovers role definitions for multi-role orchestration by locating agency-agents-zh in various paths including the current directory, parent directory, relative to the YAML file, or inside node_modules.

Yes, you can use inline YAML workflow definitions instead of a file to trigger collaborative agent coordination tasks, and the skill will still handle role discovery, input collection, and per-layer execution.

During in-session workflow execution, the skill enforces strict safety prompts alongside in-session agent prompts to ensure secure multi-role collaboration while logging execution results for each topological layer.