---
name: patchcord-inbox
description: >
  Check and process Patchcord messages for this Grok project. Use when the
  user asks to check inbox, mentions Patchcord or another agent, or a monitor
  notification reports a new message.
user-invocable: true
---

# Patchcord inbox for Grok

Use this skill only when the Patchcord MCP tools are loaded in the current
Grok session. If they are not loaded, do not read `.grok/config.toml`, scrape a
token, or call Patchcord over HTTP; report that the MCP is unavailable.

The Grok MCP server namespaces its tools as `patchcord__*`:

- `patchcord__inbox` — read pending messages and presence
- `patchcord__send_message` — send to one or more agents
- `patchcord__reply` — reply to a received message
- `patchcord__wait_for_message` — wait for a response
- `patchcord__attachment`, `patchcord__recall`, `patchcord__unsend`

## Intake

1. Call `patchcord__inbox` first.
2. For every actionable message, do the requested work before replying.
3. Reply with concrete files, changes, and verification; never send an ack-only
   response. Close an ack-only thread silently when needed.
4. If a request is destructive or needs credentials, stop and ask the user.
5. Do not reply to conversation-ending acks such as “ok”, “thanks”, or
   “noted”.

## Sending

### Write about the subject, not about your day

The recipient does not share your context and cannot use it. They do not know
what you were doing before this, what your human just said to you, or what
else is broken on your machine.

1. Write only about the subject of the message in front of you. No unrequested
   status report.
2. Mention your own circumstances ONLY when the recipient needs them to act,
   and then give the consequence, not the story: "I cannot push until
   tomorrow", never fifteen minutes of what went wrong.

Test before sending: would the recipient act differently if this sentence were
missing? If not, cut it. Pressure makes the urge to narrate stronger and the
other team's ability to use it no greater.


Call `patchcord__inbox` before sending. Use `patchcord__send_message` with the
agent name and a specific, complete message. Use named threads for multi-turn
work. If the recipient is not actively listening, the message is still queued;
do not retry in a loop.

## Message classification

For each new message, classify it as ACK, BLOCKED, ACTIONABLE, or FYI. For
ACTIONABLE work, implement and verify it, then report `DONE` or `BLOCKED` with
the evidence. Never claim a test or fix without running it in this checkout.