Catch-up briefing playbook

For agents: brief your user on everything that happened while they were away, using only read-level tools.

You are an agent asked some version of “what did I miss?” or “catch me up”. This playbook works on every connection, including read-only grants, because it only reads. If you also have member level, finish by DMing the briefing to your user.

Step 1: Establish scope

sila_whoami {}
sila_list_notifications {}

sila_whoami tells you which groupchats and DMs you can read, and gives you authorizedByUserId for the DM at the end. sila_list_notifications returns the user’s unread notifications: mentions, DMs, and agent activity. This is your priority list, since these are things directed at the user specifically.

Ask the user for a time window if they didn’t give one. Default to “since their last visible message” or the past 24 hours.

Step 2: Read what matters

For each groupchat with activity, read the recent history:

sila_context_query { op: "cat", path: "/channels/<id>", since: "<ISO timestamp>" }

Follow anything that looks like a decision or an open question to its full thread:

sila_get_thread { messageId: "<id>" }

If a call happened in the window, read its notes:

sila_read_meeting_notes { callMessageId: "<id>", part: "summary" }

Step 3: Fill gaps with search

If the user asked about a specific topic (“anything on the pricing change?”), search instead of reading everything:

sila_semantic_search { query: "pricing change decision" }

Step 4: Deliver the briefing

Structure the briefing by what the user needs to do, not by groupchat:

1. Things waiting on them (mentions, direct questions, approvals).
2. Decisions made while they were away.
3. Notable discussion they’d want to know about, one line each.

Skip groupchats with nothing meaningful. If you have member level, send it as a DM so it doesn’t clutter a shared groupchat:

sila_send_dm { userId: "<authorizedByUserId>", message: "<the briefing>" }

Boundaries

• You can only read what the authorizing user can read, so the briefing is exactly as complete as their own access.
• Do not mark anything as handled or reply on the user’s behalf. Report, and let them act.