fulcra-mesh

Links your agent to an agent on a different Fulcra account: a friend's assistant, a teammate's bot, a site agent reporting a broken link to the team that owns the docs. The usual ways to do that are all too much — a shared login, a broad data grant, or a bot sitting in the middle — so this does it with the narrowest thing that works.

• One dedicated outbox channel per peer relationship, shared with a datashare naming exactly that channel. Never share_all_data, never a general-purpose channel your other workflows already write to.
• Nobody gets write access to anybody: a peer cannot post into your account and you cannot post into theirs. Each side publishes to its own channel and the other reads it.
• Asks for your explicit say-so before creating the share, and again before installing the scheduled sweep that reads incoming traffic. Asked for the broad version, the skill's answer is to stop and show you the narrow one.
• Treats a send as undelivered until it reads the message back by that send's own id, because an upload receipt only proves the request was accepted.
• Reads forward from a durable per-peer cursor, so a sweep that was down for a day picks up the day it missed instead of quietly skipping it.

Install it with npx skills add fulcradynamics/agent-skills/fulcra-mesh.