Turns trip details, weather, and activities into a checked packing list grouped by bag, so nothing important stays home.
skillinstructionsworkflowpacking-templatelast-check-list
by Muse Skills editors · Written for this directory
Chief of Staff Briefing
A morning brief with today's priorities, meeting prep, and inbox items to answer.
by Muse Skills editors · Written for this directory
Ready to copy.
Before you install
- A shared skill carries somebody else's instructions. Read the source before you install it.
- Never paste an API key, password, or token into anything a skill asks for. Legitimate skills use Muse's own secure flows.
- Installing copies the setup into your own environment. It gives the author nothing.
What it does
Chief of Staff Briefing turns your calendar, your inbox, and a goal file you maintain into one morning brief. It reads all three, never edits them, and reports back in a fixed order: priorities, meetings with prep notes, inbox items needing a reply, and one nudge toward a goal that’s gone quiet.
You keep a plain goal file with one line per active goal. The brief reads it each run to pick the single nudge; you update the file yourself as goals change.
Run it each morning, or put it on a schedule. It only reports; it never drafts a reply or touches your calendar.
What it includes
- The goal-state file template and how to maintain it
- The full brief prompt, with its four fixed sections in order
- Rules for what to say when a section has nothing to report
Example
Goal file:
- Ship irisfile beta: waiting on QA sign-off, no update in 6 days
- Close Northwind renewal: proposal sent, awaiting reply
Output brief:
Today's three priorities
1. Reply to Northwind before their 2pm call, proposal has been open 4 days
2. Prep for the 10am Atlas sync, QA sign-off still pending
3. Confirm irisfile QA status, no update in 6 days
Meetings with prep notes
10:00 Atlas sync, with Dana and Priya. Prep: get QA's blocker list before the call
2:00 Northwind renewal call, with Marcus. Prep: bring the revised proposal PDF
Inbox items needing a reply
- Marcus (Northwind), "Re: renewal terms": needs a yes/no on the discount ask
- Dana (Atlas), "QA blockers": needs a decision on whether to slip the date
One goal nudge
Ship irisfile beta: ping Dana today for the specific QA blockers before the 10am sync.
What this one touches
Reads your calendar and inbox through the assistant's own connected accounts, plus a goal file you maintain. Writes only the brief back to you. Never replies to an email or sends a calendar invite.
Install
Copy this block and paste it into your Muse chat. Muse does the install and confirms when it's done.
Install prompt
Full source
This is the exact text Muse installs. Read it. That's the whole trust model.
SKILL.md
# Chief of Staff Briefing
How to use: run this each morning, or on a schedule you set. Keep a
goal file up to date; the prompt reads it each run and does not
change it.
## Goal state file
Maintain a short file, for example `goals.md`, with one active goal
per line:
```
- [Goal name]: [current status in one line]
- [Goal name]: [current status in one line]
```
Update it yourself as goals change. The briefing reads this file; it
never edits it.
Trigger phrases: "prepare my morning briefing", "brief me on today", "run chief of staff briefing".
## The prompt
You are my chief of staff for this morning's brief. Read my calendar
for today, my inbox for unread and flagged messages from the last 24
hours, and my goal file at ~/workspace/goals.md. Use only what these
three sources contain. Do not invent a meeting, an email, or a goal
that is not in them.
Build the brief in this exact order:
1. **Today's three priorities.** Pick the three items that matter
most today, drawn from calendar commitments, time-sensitive
inbox items, and open goals. State each as one line: what it is
and why it made the cut.
2. **Meetings with prep notes.** List today's meetings in time
order. For each: time, title, attendees, and one prep note (the
open question, the decision needed, or the document to bring).
If a meeting needs no prep, say so in one line rather than
inventing a note.
3. **Inbox items needing a reply.** List unread or flagged messages
from the last 24 hours that need a response from me, oldest
first. For each: sender, subject, and what the reply needs to
resolve. Skip anything already answered or informational-only.
4. **One goal nudge.** Pick exactly one goal from the goal file and
name one concrete next action for it today. Pick the goal that
has gone longest without a status change, or the one closest to
a deadline if any goal states one.
Keep the whole brief scannable: short lines, no restating the
question, no summary at the end. If a section has nothing to
report (no meetings today, no inbox items needing reply), say so in
one line instead of skipping the heading silently.
Never draft or send a reply, never create or edit a calendar event,
and never edit the goal file. This is a read-and-report task only.
If ~/workspace/goals.md does not exist, ask the user where their goals file lives before the first run.
More in Productivity
Turns end-of-day notes into a structured journal entry in your notes system.
skillinstructionsworkflowtemplateby Muse Skills editors · Written for this directory
Gathers multi-source research into a structured brief with sources, key findings, and open questions.
skillinstructionsworkflowbrief-templateby Muse Skills editors · Written for this directory
Watches incoming reports against rules you set and flags anomalies while the day is still live.
skillinstructionsworkflowrulesby Muse Skills editors · Written for this directory