What problem does it solve? Coordinating multiple AI agent sessions is messy: finding the right peer, avoiding stale rosters, and preventing runaway message loops all cost tokens and attention. This Skill routes a single message to exactly one peer agent with strict budget and loop-guard rules. ## Core Features & Use Cases - Paseo-first routing: Resolves Paseo agents by id prefix, name, or working directory using the bundled peer-resolve.mjs script, then delivers via paseo send --no-wait. - Terminal pi fallback: Reaches bare pi sessions through the pi-peer registry when Paseo cannot, with presence detection (live, stalled, offline) and mail counts. - Auto-call governance: Permits unsolicited peer calls only under a concrete trigger, a Higgins vault search for routing, a strict token budget, and one-call-per-turn guardrails. - Use Case: After discovering that a shared config changed, an agent runs one Higgins search to find the owning project, resolves the peer by cwd, and sends a two-sentence summary with a file pointer prefixed by a [call:from=...] marker. ## Quick Start Ask the agent to call the pi session working in the project directory and tell it that the build is now green.