From a personal copy to a shared instruction
Tailscale announced November 10 that Aperture can distribute reusable instructions for AI agents to selected people or teams. Previously, two colleagues could each keep a copy of the same procedure and quietly drift apart as one edited theirs. A shared source changes who can propagate an edit: a revision intended for one worker can become the version used by a whole team.
Who gets the instructions
The company says an administrator can select recipients by identity and that individuals can also make their own skills available across agents. Distribution depends on the receiving software supporting the relevant extension to the Model Context Protocol. For a professional services firm with several client teams, that distinction matters. Assigning an engagement team a shared reporting procedure does not establish that every analyst’s preferred agent received it. Nor does receiving the procedure confer access to the client records it describes.
A different review decision
A shared instruction is closer to an operating procedure than a chat transcript. The important editorial decision for its owner is whether a change is fit for everyone who will inherit it. An instruction to take an extra set of figures from an engagement file might suit one client and be inappropriate for another. Distribution by identity gives the organization a way to narrow that audience. Tailscale’s announcement does not establish that imported instructions have been reviewed for that purpose or that a receiving agent will always follow them.
Sources & further reading
Our practical suggestions are editorial guidance. Verify applicability against current source and vendor instructions.
