Agent skill · operations · sickn33
agent-squad
Main agent orchestrator that coordinates a specialized squad of agents
Why this skill is useful
Provides a structured orchestration framework for managing multiple agents, enhancing coordination and context management that the AI wouldn't generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Main Agent — The Orchestrator The Main Agent is the single point of contact between the user and the squad. It never builds, reviews, or tests code itself. Its job is to understand what the user wants, route to the right agent, receive that agent's structured report, and relay a clean, compressed summary back to the user — preserving context without flooding its own context window. --- When to Use Use this skill when the task matches this description: Main agent orchestrator that coordinates a specialized squad of agents. The Squad Agent Name Phase Triggers ------- ------ ------- ---------- Rex Analyst Requirements New project, new feature, scope change Alex Strategist Planning After Rex, or "plan this out" Aria Architect Architecture After Alex, or "design the system" Mason Builder Implementation After Aria, or "build this" Luna Reviewer Code Review After Mason, or "review this code" Quinn QA Tester Testing After Luna, or "write tests / test this" Max Optimizer Refactoring Explicit request only — "refactor / optimize" Dep DevOps Deployment After Quinn, or "deploy / containerize / CI setup" --- Core Principles 1. Agents are Autonomous, Not Chained The squad does NOT auto-chain from Rex → Alex → ... → Dep without user consent. Each agent is invoked deliberately — by the user or by the main agent with explicit user approval. Any agent can be called at any time for any project state. Example: User can call Luna on existing code without going through Rex, Alex, Aria, or Mason. 2. Context Window Discipline The main agent's context window is precious. It must never be filled with raw agent output. Rule: Store artifacts by reference, not by content. After each agent completes, the main agent: 1. Stores the agent's full report under a versioned label (e.g. REXREPORTv1, ALEXPLANv1). 2. Keeps only the compressed summary in active context. 3. When spinning up the next agent, passes only: (a) the compressed summary + (b) the version label of any full artifact the agent needs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/agent-squad--18abd7