agenticnotetaking/skills/message

/eidos:message

Write a message into another repo's agent-inbox/. The recipient is a peer repo, addressed by its registered name.

See [[spec - agent communication - cross repo inboxes with append only messages and registry resolution]].

Usage

/eidos:message [recipient repo] [what to say]

Instructions

1. Resolve the recipient

• Identify the recipient repo name. Ask if not given.
• Resolve its path:

  python3 ${CLAUDE_PLUGIN_ROOT}/scripts/resolve.py <recipient>
  

• On unknown repo or missing registry:
  • Offer to register the peer in agent-inbox/repo-registry.yaml.
  • Scaffold the file if absent, following [[spec - agent communication - cross repo inboxes with append only messages and registry resolution]].
  • Ask for the peer's path on this machine and an optional description.
  • Default the registry key to the path's basename (the repo's on-disk name). Confirm or override.
    • One name per repo. Don't invent a second spelling that differs from the directory.
  • Quote the description value. A bare : inside it breaks parsing.

2. Identify yourself

• from: this repo's registered name (how the recipient knows you).
  • Default to this repo's directory basename. Confirm or override.
• from-branch: the current branch (git rev-parse --abbrev-ref HEAD). Metadata.

3. Gather the message

• subject: one line.
• # Context: shared framing.
• One or more # sections, each a thing you want or need:
  • requests are - [ ] items with plain input bullets before (input context).
  • leave the => output bullets for the recipient.
  • a section with no checkboxes is pure FYI.
• Author per the writing style. See [[reference - writing style - one fact per line and decomposed bullets over dense prose]].

4. Write the file (append-only)

• Timestamp: date '+%y%m%d%H%M%S' (seconds).
• Name: message - <yymmddhhmmss> - <tldr>.md.
• Build it from [[template - message - cross repo request or notification with checkable items]].
• Write into <recipientRoot>/agent-inbox/. Create that directory if missing.
• Never edit an existing file in a peer's inbox. You may only create.
  • See [[c - foreign agents append to an inbox - only the owner edits in place]].

5. Amendments

• To change a message you already sent, write a new file.
  • Frontmatter amends: [[original-message]] plus a one-line note.
• Do not edit the original.

6. Record that you sent it

• A sent message lives in the peer's inbox, not yours.
  • You no longer own it. You can't check it off or edit it.
  • A ::repo wikilink is the only handle you keep on it.
• Record it in whatever flow you were in when you sent it.
  • Mid-plan: add a => note on the action with [[message - <ts> - <tldr>::<recipient>]].
  • Same for a todo, experiment, or any local file tracking the work.
• If no flow was active, ask the user whether to log the send somewhere.
• This link is how you find the peer's reply later.

7. Confirm

• Report the written path.
• Do not commit in the peer's repo. Delivery is the file. The recipient owns its inbox.

Output

• Creates: <recipientRoot>/agent-inbox/message - <yymmddhhmmss> - <tldr>.md
• Records a ::repo wikilink to the sent message in the active flow (plan, todo, etc.).