Productivity: Muse Skills

Chief of Staff Briefing

A morning brief with today's priorities, meeting prep, and inbox items to answer.

Uses

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.

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 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.

prompt

Type: prompt pack
Category: Productivity
Version: 1.0.0
Added: 9 Sep 2026
Author: Muse Skills editorsWritten for this directory
Includes: instructionsgoal-state-template

Save this as a reusable prompt pack named "Chief of Staff Briefing"
and confirm what it does.

--- SOURCE ---
# 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.

## 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 [path to 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.

Ready. Press Load to copy the install prompt.

Read the full source

Inbox Triage

Sorts new email into reply, delegate, archive, or later, then drafts your replies.

Uses

Inbox Triage runs on your connected email account every weekday morning and sorts what came in overnight. It splits new mail into four buckets: reply, delegate, archive, and later. For anything that needs a reply, it drafts one in your voice from the thread history, and for anything that needs someone else, it drafts a short forward note.

Nothing goes out on its own. Every draft, reply or forward, waits for your approval. You can approve a draft as written, edit it first, or discard it. Archive and later labels apply only after you have seen the batch.

The default run time is weekdays at 07:30 local. The assistant confirms that time with you before creating the recurring job, and asks again if you want to change it later.

What it includes

A cron-based recurring job, default weekdays 07:30 local
Four-way classification: reply, delegate, archive, later
Drafted replies for every message in the reply bucket
A per-message approval step before any send

Example

Input: 6 new messages overnight, including a client question about a due date and a newsletter.

Output: “3 reply, 1 delegate, 2 archive. Draft 1 (to client@example.com, re: ‘Due date?’): ‘Hi Sam, the report ships Friday, no change from last week. Let me know if that still works on your end.’ Approve, edit, or discard?” The two archive items and the newsletter are listed by subject line only, with no draft attached.

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 this one touches

Reads your connected email account only. Writes draft replies; it never sends a message without your approval on that message. Never delegates or forwards mail to a third party without you naming the delegate first. Never reads attachments beyond what the mail client already renders.

workflow

Type: workflow
Category: Productivity
Version: 1.0.0
Added: 9 Sep 2026
Author: Muse Skills editorsWritten for this directory
Includes: scheduleworkflowdraft repliesapproval step

Set up the "Inbox Triage" workflow. Its full source is below. Default schedule: weekdays
07:30 local time. Ask me to confirm or change this time before you create the recurring
job. Once I confirm, create the job, connect it to my email account, and run a first pass
now so I can see the classification and the draft replies before any run is unattended.
Tell me the job name and the confirmed schedule when it is set up.

--- SOURCE ---
name: inbox-triage
description: Scheduled email triage. Classifies new mail into reply, delegate, archive, or
  later, drafts replies for the reply set, and holds every draft for approval before send.
  Trigger phrases: triage my inbox, sort my email, draft my replies.

schedule: weekdays at 07:30 local time (cron: 30 7 * * 1-5). Confirm the time with the user
before the first scheduled run. A user change to the time takes effect on the next run.

trigger: the scheduled time, or a manual "run inbox triage now" request.

steps:
  1. Read all mail that arrived since the last successful run, using the user's own
     connected email account. Never sign in with credentials the user has not already
     connected.
  2. Classify each message into exactly one bucket:
     - reply: needs a response from the user.
     - delegate: needs action from someone else the user has already named as a delegate.
     - archive: no action needed (receipts, notifications, newsletters with no ask).
     - later: needs the user's attention but not a reply today (long threads, decisions
       that need more context).
  3. For every message in the reply bucket, draft a reply in the user's own voice, using
     the thread history for context. Keep each draft under 150 words unless the source
     message needs a longer answer.
  4. For every message in the delegate bucket, draft a one-line forward note to the named
     delegate. Never send it without approval.
  5. Present the full batch: bucket counts, then each reply and delegate draft in full,
     with the original message it answers.
  6. Wait for the user's decision on each draft: approve, edit, or discard. Send only the
     drafts marked approved, exactly as approved or as edited by the user.
  7. Apply the archive and later labels only after the user has seen the batch summary.
     Never archive a message the user has not at least seen listed.

output: a batch report per run: counts by bucket, then the full text of every reply and
delegate draft awaiting approval. If no new mail arrived, or every new message fell into
archive or later, the report says so in one line and includes no drafts.

stop_conditions:
  - Stop and ask the user if a message looks like it needs a password, payment, or legal
    commitment. Never draft a reply that commits money or signs an agreement.
  - Stop the whole run and report the error if the mail account disconnects mid-run.
  - Never retry a send. A failed send is reported, not resent automatically.

operating_rules:
  - Never send a message without per-message approval, every run, no exceptions.
  - Never delegate mail to anyone not already named by the user as a delegate.
  - Never ask the user for their email password or any credential. Use only the account
    they already connected.
  - Never forward or quote a message to a third party outside delegation the user set up.
  - A quiet run (no reply or delegate drafts) sends nothing beyond the one-line summary.

Ready. Press Load to copy the install prompt.

Read the full source

Meeting Notes Polisher

Turns raw meeting notes into decisions, owned action items, and a three-line summary.

Uses

This prompt pack turns a messy dump of meeting notes into a record you can act on. It pulls out decisions, action items with an owner and a deadline, and any question the meeting left open. It ends with a three-line summary you can forward on its own.

It runs once, on demand, whenever you paste notes into the chat. It never touches a calendar or a task tracker; you copy the output where it needs to go.

An action item with no named owner does not disappear or get a guessed name. It stays in the list, marked “No owner assigned”, so you catch it before the meeting’s decisions go untracked.

What it includes

A fill-in prompt template with a [Paste raw meeting notes here] slot.
A fixed output format: decisions, action items, open questions, three-line summary.
A rule against inventing an owner, deadline, or decision the notes do not state.

Example

Input (excerpt):

Standup 9/8. Discussed the Q3 report delay. Sarah will pull the numbers by Friday.
Someone needs to email the client about the timeline. Still unclear if we're
using the old template or the new one.

Output (excerpt):

## Decisions
- The Q3 report is delayed.

## Action items
- Pull the Q3 numbers | Owner: Sarah | Deadline: Friday
- Email the client about the timeline | Owner: No owner assigned | Deadline: No deadline set

## Open questions
- Are we using the old report template or the new one?

## Summary
The Q3 report is delayed and Sarah owns the numbers by Friday.
No one is assigned to email the client about the new timeline.
The report template to use is still undecided.

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 this one touches

Reads only the notes you paste into the chat. Writes nothing on its own; it returns text for you to copy. Never contacts a calendar, task tracker, or any other person. Flags a missing owner instead of guessing one.

prompt

Type: prompt pack
Category: Productivity
Version: 1.0.0
Added: 9 Sep 2026
Author: Muse Skills editorsWritten for this directory
Includes: prompt

Save this as a reusable prompt pack named "Meeting Notes Polisher" and confirm what it does.

--- SOURCE ---
# Meeting Notes Polisher

Paste raw meeting notes below the line. Turn them into a structured record.

Rules:
1. Read the notes once. List every decision made in the meeting.
2. List every action item. For each one, give the task, the owner, and the deadline.
3. If an action item has no named owner, write "No owner assigned" next to it instead of
   guessing a name.
4. If an action item has no deadline, write "No deadline set" next to it.
5. List every open question the notes raise but do not answer.
6. Write a three-line summary of the meeting. Each line covers one idea.
7. Do not add a decision, action item, or question that the notes do not state.
8. Do not invent an owner, a deadline, or a next step.

Output format:

## Decisions
- [Decision 1]
- [Decision 2]

## Action items
- [Task] | Owner: [Name or "No owner assigned"] | Deadline: [Date or "No deadline set"]

## Open questions
- [Question 1]

## Summary
[Line 1]
[Line 2]
[Line 3]

--- NOTES ---
[Paste raw meeting notes here]

Ready. Press Load to copy the install prompt.

Read the full source

Weekly Feed Brief

A feed-prompt template that turns your weekly briefing into topics you chose.

Uses

This config turns the assistant’s feed prompt setting into a briefing you control. You name the topics to follow, the sources you trust, and the sources or angles to skip. You also set how long a briefing runs and which day it arrives.

It lives in one place: the feed prompt field in your assistant settings. The install prompt shows you the filled-in snippet and waits for your confirmation before it writes anything there.

A week with no genuine update on any of your topics sends nothing. The config states that rule directly, so a quiet week doesn’t turn into a briefing padded with old news.

What it includes

A YAML-style snippet with topics_follow, sources_prefer, sources_skip, output_length, and delivery_day fields.
A stated location: the assistant’s feed prompt setting.
A confirm-before-write step, and a quiet-week rule that suppresses empty briefings.

Example

Filled-in config:

topics_follow:
  - "Federal Reserve rate decisions"
  - "Changes to Section 8 housing subsidy rules"
  - "Blackstone real estate moves"

sources_prefer:
  - "The Real Deal"
  - "Bisnow"

sources_skip:
  - "general stock market commentary"

output_length: "short: 3-5 bullets"
delivery_day: "Monday morning"

A week’s briefing:

- The Fed held rates steady this week, citing housing-sector softness (Bisnow).
- No Section 8 rule changes this week.
- Blackstone announced a $2B acquisition of a logistics REIT (The Real Deal).

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 this one touches

Writes only to the assistant's own feed prompt setting, and only after you confirm the change. Never reads a file outside that setting. Never sends a topic, source, or preference to any third party. A week with nothing to report sends nothing.

config

Type: config
Category: Productivity
Version: 1.0.0
Added: 9 Sep 2026
Author: Muse Skills editorsWritten for this directory
Includes: configfeed-prompt

This config lives in the assistant's feed prompt setting, the field that controls what
your weekly briefing covers. Show me the filled-in snippet below with your topics,
sources, and preferences, and wait for me to confirm it before you write anything to the
feed prompt setting.

--- SOURCE ---
# Weekly Feed Brief config

## Where this lives
Assistant settings → Feed → Feed prompt. This snippet replaces or extends the text in
that field. Ask the user to confirm before writing.

## Config snippet

```
topics_follow:
  - "[Topic 1, e.g. commercial real estate financing]"
  - "[Topic 2, e.g. changes to a named regulation]"
  - "[Topic 3, e.g. a competitor or company name]"

sources_prefer:
  - "[Source 1, e.g. a named trade publication]"
  - "[Source 2, e.g. a named analyst or outlet]"

sources_skip:
  - "[Source to exclude, e.g. a low-quality aggregator]"
  - "[Topic to exclude, e.g. general market commentary with no new fact]"

output_length: "[short: 3-5 bullets | medium: one paragraph per topic | long: full
  briefing with links]"

delivery_day: "[day of week, e.g. Monday morning]"

quiet_rule: "If no topic has a genuine update this week, send nothing rather than a
  briefing with no news."
```

## What to change
- `topics_follow`: name specific topics, not broad categories. "Fed rate decisions"
  beats "the economy."
- `sources_prefer`: name outlets or people, not "reputable sources."
- `sources_skip`: name what to exclude, whether a source or a category of story.
- `output_length`: pick one of the three named lengths.
- `delivery_day`: one day and a rough time of day.

## Install steps
1. Ask the user to fill in each bracketed field above, or fill them in from what they
   tell you in chat.
2. Show the completed snippet back to the user.
3. Wait for explicit confirmation.
4. Write the confirmed snippet to the assistant's feed prompt setting.
5. Confirm the write succeeded and tell the user which day the first briefing arrives.

Ready. Press Load to copy the install prompt.

Read the full source

Productivity

Skill bank

Chief of Staff Briefing

Uses

What it includes

Example

Before you install

What this one touches

Inbox Triage

Uses

What it includes

Example

Before you install

What this one touches

Meeting Notes Polisher

Uses

What it includes

Example

Before you install

What this one touches

Weekly Feed Brief

Uses

What it includes

Example

Before you install

What this one touches