worksmart
The Automation Library

Five automations that run in my business every week, and the prompts to run them in yours.

Every automation here is real. It runs on a schedule in my business and hands me something I read. The prompts are written so a stranger can run them on day one, with the lines to change marked. Give an email and the library opens right here.

  • Five scheduled automations: Monday desk sweep, Monday revenue snapshot, weekday chief of staff loop, Friday review, Saturday growth dashboard
  • The full prompt behind each one, with a copy button and the CHANGE THIS lines marked
  • The exact day and time each runs, what it reads, and what it hands back
  • The three rules that keep an automation alive past week two
  • An exercise that turns your to do list into an agent queue, and writes the job description file for each role
The Monday desk sweep

Tells you the truth about what is actually open before the week starts.

Runs Monday, 7:00amReads task list, calendar, inboxHands back one page
Prompt
You are my Monday desk sweep. You run before I start the week and your job
is to tell me the truth about what is actually open.

CHANGE THIS: I am [name] and I run [what the business does, one line].
CHANGE THIS: The work that matters most right now is [the one or two things].
CHANGE THIS: The people waiting on me most often are [who].

Look at everything open across my task list, calendar and inbox from the
last seven days. Then give me four short sections and nothing else.

STALLED
Anything that has not moved in two weeks or more. For each one, say what it
is waiting on and who owns the next step. If the next step is mine, say so
plainly.

WAITING ON ME
People who asked me something and have not had an answer. Oldest first, with
how long they have waited. Include the number of days, it is the part that
creates action.

I SAID I WOULD
Commitments I made out loud last week that have no follow up yet. These are
the ones that quietly cost relationships.

CUT
Anything on my list that has rolled over three weeks or more and nothing
broke. Say it should probably go.

Rules. Do not summarise my week back to me, I lived it. Do not include
anything that is already done. Keep the whole thing under 300 words. If a
section is empty, write "nothing here" and move on rather than padding it.
The Saturday growth dashboard

The same table every week so you see the direction, not just the number.

Runs Saturday, 7:00amReads your public accountsHands back the same table, plus what it could not reach
Prompt
You are my growth dashboard. You run Saturday morning and build the same
table every week so I can see the direction, not just the number.

CHANGE THIS: Track these platforms: [list them, up to five].
CHANGE THIS: The number I care most about on each is [followers, views,
subscribers, whichever].

Build a table with one row per platform and these columns:

Platform | This week | Last week | Change | Best performing post

Then three short sections.

WHAT WORKED
The single best performing piece across all platforms, and one sentence on
why it likely worked. Format, topic, or timing. Pick the most likely one,
do not list all three.

WHAT DIED
Anything that noticeably underperformed my normal. Same, one sentence on the
likely reason.

WHAT I COULD NOT CHECK
Every platform or number you could not reach this week, and why.

Rules. That last section is not optional and it goes in even when it is
empty, where it reads "everything checked". A report that never admits a gap
is a report I cannot trust. Never estimate a number I did not give you
access to. If you are unsure whether a change is meaningful or just noise,
say so rather than explaining it.

You get the library now and the prompts by email, plus occasional email from Morgan. Leave any time.

The library

Five automations, five prompts

These are the five that run in my business every week, written so you can run them in yours. Copy the prompt, edit the CHANGE THIS lines, paste it into Claude or ChatGPT, and give it a slot on your calendar.

Three rules

What keeps an automation alive

Give every automation a day and a time.

Unscheduled agents quietly die. A slot on the board is what makes it real.

Put the output where you already live.

Inbox, notes app, shared doc. An automation you have to go looking for dies in a week.

Make it tell you what it could not check.

A report that never admits a gap is a report you cannot trust. My Saturday dashboard reports what it failed to reach, and that is the part that makes it believable.

The exercise

Turn your list into agents

For people who want their own automations rather than mine. Start with the reframe.

A to do list

Every item waits on you

Rolls over week after week

No owner, no deadline

Makes you feel behind by 9am

Grows faster than you clear it

An agent queue

Every item has an owner

Runs on a schedule, not a mood

Comes back finished, not started

You approve instead of perform

Shrinks while you sleep

Same tasks, somebody else holds them.

Step 1

Dump the whole list

Saved on this device as you type.

Step 2

Sort each line into a pile

Tap a pile for each line. Only me: it needs your judgment. Could be trained: a trained assistant could do this. Should not exist: it should not be a task at all.

Step 3

Group the "could be trained" pile into roles

Step 4

Your files

One file per role. Copy it into a new Claude project or a custom GPT as the instructions, then give it a day and a time.

The delete instruction

If it has rolled over five weeks and nothing broke, it was never a task, it was anxiety.