Loading...
Loading...
Found 254 Skills
Execute tasks through competitive multi-agent generation, multi-judge evaluation, and evidence-based synthesis
Coordinate Claude Code Agent Teams through filesystem-based protocol. Use when orchestrating multiple Claude agents on parallel tasks, need task dependency management, multi-agent code review or implementation. Do not use when single-agent work suffices, task is not parallelizable.
Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.
Orchestrate parallel scientist agents for comprehensive analysis with AUTO mode
Team-orchestrated implement → verify → fix → archive cycle
This skill should be used when the user asks to "wrap up session", "end session", "session wrap", "/wrap", "document learnings", "what should I commit", or wants to analyze completed work before ending a coding session.
Bootstrap a Memory Bank for a new or existing repository, then route into PRD-driven or brownfield workflows.
Universal Assistant — Automatically analyzes scenarios, takes inventory of ECC resources, intelligently routes to the optimal agent pipeline, and completes complex workflows with one click.
Orchestrate multi-service AWS workflows with autonomous agents. Coordinates across compute, storage, identity, and observability services for intelligent cloud automation.
Orchestration workflow for orchestrator role ONLY. Use when: - Agent's role name (tmux pane title) is "orchestrator"
Complete virtual board of directors — 28 skills covering 10 C-level roles, orchestration, cross-cutting capabilities, and culture frameworks. Features internal quality loop, two-layer memory, board meeting protocol with Phase 2 isolation, proactive triggers, and structured communication standard.
Multi-agent coordination discipline: one-message-then-wait (send complete context, wait for reply before sending again), idle notifications are heartbeats (no action unless extended + blocking + user asked), no polling loops (event-driven only), never fabricate agent responses (wait for real system events), sequential agent spawning (acknowledge between each), and proper shutdown protocol (request, wait, respect rejection). Activate when orchestrating multiple agents, managing agent teams, coordinating handoffs between agents, spawning subagents, or building multi-agent workflows. Triggers on: "coordinate agents", "spawn multiple agents", "manage agent team", "agent keeps sending messages", "polling loop", "agent idle", "shut down agent", "multi-agent workflow", "agent handoff", "coordinate parallel work", "stop bothering the other agent". Also relevant when an agent is fabricating responses, sending follow-up messages before replies arrive, or reacting to idle notifications unnecessarily.