multi-agent-orchestration-architect

Designs multi-agent AI orchestration systems with BullMQ job chains, LLM routing, and tool registries.

1|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/sabiscore/the-yap-engine --skill multi-agent-orchestration-architect-sabiscore
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: multi-agent-orchestration-architect
Source: https://github.com/sabiscore/the-yap-engine/tree/main/.ai/skills/multi-agent-orchestration-architect
Command: npx skills add https://github.com/sabiscore/the-yap-engine --skill multi-agent-orchestration-architect-sabiscore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bullmq, ioredis, effect.

What problem does it solve? Building systems where multiple AI agents coordinate is error-prone: routing correctness, state integrity, and failure isolation are hard to retrofit. This Skill provides architectural patterns for agent registries, job queues, LLM fallback routing, state machines, tool dispatch authorization, and prompt injection defenses so these problems are solved by design. ## Core Features & Use Cases - Agent Registry & Contracts: Define each agent role with an explicit model, fallback model, tool allowlist, timeout, and versioned system prompt before writing any code. - BullMQ Job Architecture: Structure stateless agent jobs with correlation IDs, retry policies, and separate Redis connections for queues, workers, and events. - LLM Router with Fallback: Wrap every model call with input sanitization, timeouts, and automatic fallback to a secondary model on rate limits or timeouts. - Use Case: When building a pipeline where an orchestrator decomposes a task, dispatches sub-tasks to coder and researcher agents, evaluates results, and synthesizes a final answer, use this Skill to design the state machine, queue topology, and observability spans before implementation. ## Quick Start Ask the AI to design the agent registry, BullMQ job chain, and LLM fallback routing for your multi-agent system before writing any agent code.

Frequently Asked Questions about multi-agent-orchestration-architect

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

FAQPage Schema
How do I design a multi-agent AI orchestration system?▼

Start by defining an agent registry where each role has an explicit contract: primary model, fallback model, tool allowlist, timeout, and versioned system prompt. Then let a central orchestrator handle routing while agents remain stateless, with all state in job payloads or a database.

How to implement LLM fallback routing with timeouts?▼

Wrap each LLM call with a hard timeout using the agent spec's timeoutMs, then catch timeout and rate-limit errors to retry against a configured fallback model. Add exponential backoff before the fallback call and emit token usage metrics for both attempts.

How do I use BullMQ for AI agent job chains?▼

Create a queue with retry attempts and exponential backoff, keep completed jobs for debugging and failed jobs for postmortems, and run one worker per agent role with limited concurrency. BullMQ requires separate ioredis connections for the Queue, Worker, and QueueEvents.

How do I prevent prompt injection in AI agents?▼

Treat all user input as untrusted: cap input length, strip system: prefixes, and remove Llama [INST] and ChatML im_start/im_end markers before the input enters any agent's context. Always place user input in the user turn, never in the system prompt.

Should agents route tasks to each other in a multi-agent system?▼

No. The orchestrator decides routing; agents do not route themselves. Each agent has one clearly defined role, and giving an agent routing responsibility makes routing correctness and failure isolation much harder to guarantee.

How do I add observability to an agent pipeline?▼

Emit an OpenTelemetry span for every agent invocation with attributes for role, task ID, and trace ID, and record exceptions on failure. Also create histograms for per-agent token usage and latency so you can monitor cost and performance per role.