What problem does it solve? In multi-session Claude Code environments using CALM, an AI session may need to directly contact another live session via SendMessage, but doing so without checking the session ledger can cause mistaken identity, redundant questions, or interruptions of busy peers. This Skill enforces the correct etiquette before any synchronous peer contact. ## Core Features & Use Cases - Trigger Discipline: Activates only when a "📮 [宛先候補]" destination candidate appears in a tool response or the user explicitly instructs synchronous outreach, and refuses to fire for asynchronous opinion gathering or simple progress reports. - Ledger-First Verification: Requires checking the peer's responsibility scope with get_sessions before asking directly, preventing mix-ups between sessions. - Non-Intrusive Messaging: Guides writing concise requests that reference the relevant activity/topic, avoid assuming immediate replies, and fall back to the board Skill or human escalation when no response arrives. - Use Case: A judgment-pending goal surfaces a related session as a destination candidate; before sending a SendMessage asking about responsibility, the Skill ensures the ledger is consulted first and the message is phrased considerately. ## Quick Start When a destination candidate appears in a tool response, use the peer-nudge skill to verify the peer's scope with get_sessions and then send a concise SendMessage.