dancer-a2a

Code-aware agent-stack audit + reconcile in one pass. Use when auditing an existing agent topology, reviewing a fleet setup, or triangulating understanding of a codebase's agent architecture across model families. Triggers — "audit the stack", "agent topology review", "fleet audit", "review agent architecture", "triangulate agent state".

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".

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".

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".

Ratify the NxN relationship matrix of a fleet — for every ordered pair of agents, confirm what each expects from and provides to the other, and write the result to structured JSON + markdown with an n8n webhook payload for immutable custody. Use when onboarding a new agent into a fleet, when agent roles change, when handoff protocols need explicit confirmation, or when the user says "permutation", "fleet topology", "relationship matrix", "who does what for whom", "ratify fleet relationships", or "NxN agent mapping".

Use when the fleet must formally sign off on an artifact — a converged grill result, a vault doc, an ADR, a convention, or a proposition — and one agent's or a pair's approval is not enough and you need fleet-wide consensus. Use when chaining ratification onto a finished grill, or when a decision needs N-agent attestation or approval with dissent recorded rather than overruled.

Two (or more) agents — Claude sessions, other LLMs, or mixed — interrogate each other through a structured file-based protocol to converge on shared project state. Each agent independently dumps its model, the disagreements get grilled until convergence or surfaced as unresolved, and both sign off on a merged ground truth. Use when parallel sessions have diverged, when reconciling state across machines, or when the user mentions "have the agents grill each other", "peer-grill", "reconcile state", or "two agents agree on X".

This skill should be used when the user asks "who is Wings", "who is Zoe", "who runs Kopi", "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 Hermes/Wings, OLIVIER_MBP/Zoe, KimiClaw/Mara/Kopi, and any future agents added to the coordination folder.

Use when Claude Code needs to catch up on messages that landed on Jack's Telegram/Discord/Slack/WhatsApp/Signal/Matrix while the session was heads-down, respond via the Hermes messaging bridge, read incoming attachments, or approve/deny Hermes-queued tool calls. Triggers on "check hermes", "catch me up", "what came in while I was working", "any pending approvals", "what's on telegram", "reply via hermes", "wings says", "messages waiting". Complements hermes-cli (which handles delegation via `hermes chat -Q -q`); does NOT replace it.

This skill should be used when the user asks to "check zoe", "what did zoe say", "ask zoe", "zoe handoff", "openclaw message", "openclaw events", "any pending openclaw approvals", "klawz room", "what's in

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`).

Each agent in a local fleet — Claude sessions on different machines, mixed-model agents, or whatever's in play — independently writes a short "what I know and what I'm working on" report to a shared directory. One reader collates them into a roundup. No grilling, no consensus, no merging. Use when you want visibility across a multi-agent fleet, or the user mentions "fleet show and tell", "agent roundup", "what does each agent know", or "round-robin status from the agents".

Reference for the scholastic + Greek vocabulary used in peer-grill and grill-me-agents protocols. Use when an agent needs to know what ELENCHOS, QUAESTIO, SED-CONTRA, RESPONDEO, or ALETHEIA mean as grill-log tags, or when authoring a structured disputation.

Encode or decode mirror-scripted "protected" strings wrapped in the `__protected__:<reversed>:__end__` sentinel and emit a Discord audit signal (tattle) to Jack on every operation. Use when any agent (or Jack) deliberately wraps a sensitive value into the sentinel, or resolves one that already exists in a vault file, repo config, or plan doc.