dancer

This skill should be used when the user asks "who is Wings", "who is Zoe", "who is Neo", "who runs Kopi", "who runs Codex", "what is Arbiter", "fleet identity", "fleet mapping", "agent mapping", "identity map", "autonomous ai agent", "what agent is behind X", or needs to look up which runtime agent is behind a Discord/Telegram surface (or vice versa). Returns the canonical mapping from ~/Documents/Coordination/ without duplicating data. Covers PT/Neo, Hermes/Wings, OLIVIER_MBP/Zoe, KimiClaw/Mara/Kopi, GPT-5 Codex/Bean/Blue, Arbiter, fleet-alerts, and any future agents added to the coordination folder.

Generate visual topology diagrams from ratified agent matrices. Shows agent relationships, signed nodes, and misaligned edges. Use after fleet-ratify completes or when you need to visualize agent topology from a ratified-matrix.json or ratified-matrix.md.

Bridge athenaeum-audit divergence findings to Arbiter Zebu for human-in-the-loop decisions. Use when audit finds High Risk or Divergent risks that require human approval before ratification.

Two (or more) agents independently audit the SAME existing agent stack against the codebase, then reconcile via the peer-grill file-based protocol. Each agent walks the same 13-branch agent-stack audit (grill-me-with-agents) on its own, dumps a claims.yaml grounded in concrete file paths, and the disagreements get ratified or escalated. Use when the agent topology is already implemented and you need multi-agent triangulation on whether a *change* to it is sound — single-agent grilling has known blind spots, peer-grill alone has no code anchor, this combines them. Triggers — "peer-grill the agent stack", "two agents audit the topology", "stress-test our agents from two angles", "triangulate the agent design", "reconcile our reading of the stack". Do NOT use for greenfield design (use `grill-me-agents`), for single-agent code-aware grilling (use `grill-me-with-agents`), or for non-agent state reconciliation (use `peer-grill`).

High-fidelity code audit via 13-branch anchor triangulation.

Rigorous design grilling for agent stacks, architectures, and plans. Use when designing a multi-agent collaboration, subagent topology, fleet roster, or any complex plan that needs branch-by-branch resolution. Triggers — "design my agents", "grill this plan", "agent topology", "stress-test this architecture", "athenaeum design", "design grill".

Fleet-wide formal attestation of an immutable artifact with dissent recorded, not overruled. Use when a decision needs N-agent sign-off, when chaining ratification onto a converged grill result, or when an ADR/convention should not ship on one agent's say-so. Triggers — "fleet sign off", "ratify this", "N agents approve", "get the fleet's attestation", "athenaeum ratify", "fleet attestation".

Two or more agents reconcile divergent understanding through a structured file-based protocol. Use when parallel sessions disagree, when a non-Claude peer needs to converge with a Claude session, or when triangulating a design across model families. Triggers — "agents disagree", "reconcile state", "peer grill", "triangulate", "two agents audit this", "athenaeum reconcile", "converge state".