What problem does it solve? When multiple AI sessions work on different repositories, messages between them often contain unverifiable claims, misattributed statements, or procedures that fail outside their original context. This Skill defines how to assemble and send inter-session messages so the receiving session can verify facts, trace attribution, and act on shared procedures correctly. ## Core Features & Use Cases - Verifiable fact delivery: Distinguishes facts the peer can confirm (pushed commits, PRs, CI results) from local-only observations, and requires commit SHAs when reporting on moving branches. - Attribution discipline: Prevents mixing your own observations with the peer's words by checking original messages before quoting or thanking, including checking the from field when multiple sessions reply. - Scoped procedure handoff: Requires attaching applicability conditions and tested environments when passing commands or recovery steps to another session. - Use Case: After finishing a cross-repository change, you notify the session owning the dependent repository with the merged commit SHA, a 3-5 line status summary, and a query about their merge timeline using SendMessage. ## Quick Start Ask the agent to notify the peer session responsible for the other repository about the completed change, including the commit SHA and current status.
