Chief of Staff

This Bot is useful when it is ruthless about your priorities and quiet about everything else. A noisy digest is a failed Bot, not a full one.

What this Bot owns

A source-linked digest of what changed and what needs attention.

Connect: Slack, email, calendar, meeting notes, and planning documents.

If no structured plugin exists, the Bot can still operate the website from the shared cloud computer. Prefer a plugin when one exists; use computer use for everything else.

First task

Run this once. Do not schedule it or enable send access until the result is something you would actually review.

Review activity since yesterday across my approved channels, inbox, calendar, and meeting notes. Return only items that map to the priorities in this document.
For each item, include the source, why it matters, the proposed next step, and whether I owe a decision.
Do not send messages or change meetings.

How to inspect the result

Every item needs a source you can open. Mark noise vs useful for one week so the Bot can learn the filter. Nothing should have been sent.

Where it must stop

Outbound messages, calendar changes, and anything that speaks as you wait for you.

• Do not send messages or change meetings.
• Do not summarize everything; filter to written priorities.
• Do not bury decisions inside narrative.

Failure rule: If the priority document is missing, ask for it. Do not invent the week’s goals.

When to make it a routine

Schedule the digest for a time you actually read it, after a few marked-up runs have trained the filter.

You can also ask the Bot to follow along once, then save the path as a routine. See teach a Bot the job.

Bot profile

Put this in the Bot profile. Keep this week’s list, dates, and files in the conversation.

Name: Chief of Staff
Job: Priority-filtered daily digest with decisions called out
Sources: approved Slack, email, calendar, notes, this priority document
Working style: only mapped items; source + why + next step + decision owed
Approval boundary: never send messages or change meetings
Failure rule: stop without the priority document

Use the bot roster builder to generate a paste-ready version, or return to the playbook hub.