Agent skill · operations · sickn33
multi-agent-task-orchestrator
Route tasks to specialized AI agents with anti-duplication, quality gates, and 30-minute heartbeat monitoring
Why this skill is useful
Adds a complete orchestration framework with executable scripts for task routing, quality checks, and monitoring that fundamentally enhances multi-agent coordination capabilities.
What it needs
Requires sqlite3 installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Multi-Agent Task Orchestrator Overview A production-tested pattern for coordinating multiple AI agents through a single orchestrator. Instead of letting agents work independently (and conflict), one orchestrator decomposes tasks, routes them to specialists, prevents duplicate work, and verifies results before marking anything done. Battle-tested across 10,000+ tasks over 6 months. When to Use This Skill Use when you have 3+ specialized agents that need to coordinate on complex tasks Use when agents are doing duplicate or conflicting work Use when you need audit trails showing who did what and when Use when agent output quality is inconsistent and needs verification gates How It Works Step 1: Define the Orchestrator Identity The orchestrator must know what it IS and what it IS NOT. This prevents it from doing work instead of delegating: This "NOT-block" pattern reduces task drift by ~35% in production. Step 2: Build a Task Registry Before assigning work, check if anyone is already doing this task: Step 3: Route Tasks to Specialists Use keyword scoring to match tasks to the best agent: Step 4: Enforce Quality Gates Agent output is a CLAIM. Test output is EVIDENCE. Step 5: Run 30-Minute Heartbeats Examples Example 1: Delegating a Code Task Example 2: Handling a Duplicate Best Practices Always define NOT-blocks for every agent (what they must refuse to do) Use SQLite for the task registry (lightweight, no server needed) Set similarity threshold at 55% for anti-duplication (lower = too many false positives) Require evidence-based quality gates (not just agent claims) Log every delegation with: task ID, agent, scope, deadline, verification command Common Pitfalls Problem: Orchestrator starts doing work instead of delegating Solution: Add explicit NOT-blocks and role boundaries Problem: Two agents modify the same file simultaneously Solution: Task registry with file-level locking and queue system Problem: Agent claims "done" without actual changes Solution: Quality gate ch …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/multi-agent-task-orchestrator--fd7cb4