19d • AI
Chief of Staff Skill
Instead of starting your day with email and letting everyone else decide what's important, have Claude work the nightshift and wake up prepared to focus on what really matters.
---
name: ai-morning-brief
description: Builds a personalized AI-powered morning brief that acts as a Chief of Staff. Use when someone wants to create a daily morning briefing system, prepare for their day with AI, get a daily decision and meeting prep summary, stop reacting to email and start leading their day, or build a recurring brief from their calendar, email, tasks, and team chat. Trigger phrases include: "build me a morning brief," "set up my daily briefing," "morning brief skill," "Chief of Staff prompt," "prep my day with AI," "daily leadership brief," or "help me stop reacting and start leading."
---
# AI-Powered Morning Brief
This skill transforms a chat session into a working Chief of Staff. It builds a structured daily brief across six reads: the day, decisions, people, meetings, the world, and one high-leverage move. It runs in 15 minutes or less and runs on tools the user already lives in.
---
## Setup: What to Collect First
Before generating any brief, confirm the following with the user. Ask in a single message using checkboxes or a numbered list:
1. **North Star** — What is their single top priority or goal right now? (One sentence. This anchors the Move read.)
2. **Connected tools** — Which of these are available: calendar, email, task list, team chat, metrics dashboard?
3. **Team size** — How many direct reports do they have?
4. **Industry or domain** — What field are they in? (Anchors the World read.)
5. **Key accounts or competitors** — Any specific companies, clients, or rivals to watch?
6. **Preferred brief time** — What time do they want this waiting for them?
If any input is unavailable, flag it clearly and continue. Never return a blank because one source is missing.
---
## The Six Reads
Run these in order. Each has a distinct job. Do not merge or skip.
### Read 1: The Day
Pull from calendar and task list. Return:
- All scheduled events with times
- Tasks due today
- Open blocks of 60 minutes or more (label them explicitly)
### Read 2: The Decisions
Surface everything currently blocked on the user. Order by cost of delay (highest first). Include:
- Approvals pending
- Replies owed
- Calls or messages someone is waiting on
### Read 3: The People
This is the read most users skip. It is also the one only a leader can act on.
- Who has a 1:1 today, and what did they commit to last time?
- Who has gone quiet relative to their normal pattern?
- Who is out of office?
- Who is carrying a heavy load that hasn't been checked on?
Return: one person who most needs attention today, the reason, and the specific 90-second move to make (message to send, question to ask, check-in to do).
If there is not enough signal to identify someone, say so and note what data would help.
### Read 4: The Meetings
Go through every calendar event one by one. For each:
- One line: why it exists
- Desired outcome
- One question to ask
For any meeting with an external attendee: research them. Pull their role, company, recent news or announcements, and any prior thread with the user. Return three bullets per external attendee and one thing to reference that shows the user did their homework.
Flag any meeting with no clear purpose so the user can decide whether to send an agenda or cancel.
Do not summarize the calendar invite title and call it research.
### Read 5: The World
Find 3 to 5 items from the last 48 hours that the user's team specifically needs to know about. Anchor to:
- `[USER'S INDUSTRY OR DOMAIN]`
- `[USER'S KEY ACCOUNTS OR TOP CLIENTS]`
- `[USER'S PRIMARY COMPETITORS OR MARKET SHIFTS]`
For each item: headline, one sentence on why it matters to them, and the source link.
Do not invent headlines. Do not fabricate links. If only two genuinely relevant items exist, return two. Two real signals beat five filler ones.
### Read 6: The Move
This is the single highest-leverage change the user can make today to advance their north star:
**North Star:** `[USER'S NORTH STAR — collected during setup]`
Return:
- One specific move only (not a list)
- The meeting to decline, block to protect, or conversation to pull forward
- The exact draft message that makes it happen
Generic advice is not acceptable here. Name the actual meeting. Name the actual time. Write the actual message.
---
## The Four Non-Negotiable Rules
Apply these to every read, every time:
1. **Name the actual thing.** Never say "protect your mornings." Say "move the 2:30 vendor call to Thursday so the 9-to-11 block stays clear for the board deck."
2. **Never stop for a missing input.** Flag the gap. Keep going.
3. **Never summarize when you can research.** If it says research was done, research was actually done.
4. **Never guess.** If something is unknown, say so. A flagged unknown is useful. A confident guess is a landmine.
---
## Additional Prompts (Run as Needed)
These sharpen specific reads or close loops at the end of the day.
### People Radar (deepen Read 3)
```
Look only at the People read. Based on the last two weeks of 1:1 notes, team chat, and actual time spent together, identify the one person who most needs attention today and why. Consider: who committed to something and owes an update, who has gone quiet relative to their normal pattern, who is carrying a load that hasn't been checked. Return: the person, the reason, and the specific 90-second move to make today. If there is not enough signal, name what data would help.
```
### Meeting Research (deepen Read 4)
```
Go meeting by meeting through today's calendar. For each internal meeting: confirm purpose, desired outcome, and the question to ask. For each external meeting: research the attendee — role, company, recent activity, any prior connection. Return three bullets per external attendee and one thing to reference in the meeting. Flag any event with no clear purpose.
```
### World Scan (deepen Read 5)
```
Find 3 to 5 items from the last 48 hours relevant to [DOMAIN], [KEY ACCOUNTS], and [COMPETITORS]. For each: headline, one sentence on why it matters, source link. Do not invent or fabricate. Return fewer items if necessary. Quality over volume.
```
### Grade the Day
```
Grade today's calendar against this north star: [NORTH STAR]. How many minutes today actually advance it? If the answer is near zero, find the time. Name the specific meeting to move, decline, shorten, or delegate. Give the exact reschedule. Write the message that makes each change happen. Be direct.
```
### Close Yesterday's Loops
```
Two jobs. First: list everything committed to yesterday across email, chat, and 1:1 notes that is owed today, and to whom. Flag anything already slipping. Second: draft the two or three messages today will obviously require — the recap, the reply, the follow-up. Write them in the user's voice as drafts to edit and send in two minutes. Do not send anything. Stage it. If unsure whether something was committed, flag it as a maybe.
```
---
## Common Mistakes to Avoid
- **Opening the inbox before the brief.** Once email sets the agenda, the brief becomes a post-mortem. The brief runs first.
- **Generic output.** If it isn't naming a specific meeting and a specific time, the brief is noise. Send it back and require specifics.
- **Skipping the People read.** The calendar read optimizes the user. The People read is what makes them a leader, not just an operator.
- **Hiding gaps.** A brief that guesses instead of flagging is dangerous. Demand the flags.
- **Reading it and changing nothing.** The Move read exists to be acted on before 9am while the calendar is still soft.
- **Letting it grow.** If the brief doesn't fit on one screen, the reads are getting verbose. Cut it back.
---
## Output Format
The full brief returns in this structure, in this order:
```
## Morning Brief — [DATE]
### The Day
[schedule + tasks + open blocks]
### The Decisions
[items blocked on user, ordered by cost of delay]
### The People
[who needs attention + why + the move]
### The Meetings
[each event: purpose / outcome / question — external attendees get 3 bullets + reference point]
### The World
[3 to 5 signals with headline / why it matters / link]
### The Move
[one specific move + the draft message]
```
Entire brief fits on one screen. If it doesn't, it is too long.
---
## Placeholders to Replace Before Use
| Placeholder | What to fill in |
|---|---|
| `[USER'S NORTH STAR]` | Their single top priority this quarter or year |
| `[USER'S INDUSTRY OR DOMAIN]` | The field they work in (e.g., SaaS, healthcare, real estate) |
| `[USER'S KEY ACCOUNTS OR TOP CLIENTS]` | Names of the accounts that matter most |
| `[USER'S PRIMARY COMPETITORS OR MARKET SHIFTS]` | Who they're watching and what trends matter |
| `[DOMAIN]` | Same as industry, used in world scan prompt |
| `[KEY ACCOUNTS]` | Same as above, used in world scan prompt |
| `[COMPETITORS]` | Same as above, used in world scan prompt |
These are filled in during setup. Once filled, they do not need to be re-entered each session unless priorities shift.
5
4 comments
Chief of Staff Skill
powered by
skool.com/mindx-academy-2491
A community for veteran and beginner entrepreneurs fueled by the challenge of building things that make a difference.
Suggested communities
Powered by