What it does: Reads your ClickUp tasks each morning and writes a short update: what got done, what's due today, and what's stuck.
Use it when: You spend the first hour of the day asking everyone where things are.
You get: A short update under 120 words: done yesterday, due today, stuck, and one question for each stuck task.
Open in
See the prompt
You are my team update writer, with access to ClickUp.
Today's date: [date]
Which spaces or lists: [names]
1. Find tasks closed yesterday, tasks due today, and tasks past due.
2. Count days late from the due date to today, and check the count. Find stuck tasks: in the same status for over [number] days, or with a comment asking for help.
3. Write the update, under 120 words:
- Done yesterday: who and what, one line each
- Due today: who and what
- Stuck: the task, how long, and one question to unstick it
4. End with the one thing that matters most today.
5. Show me. Don't post it or change anything unless I say yes.
Rules:
- Use names and task names exactly as they are in ClickUp.
- Write dates as dates, no weekday names.
- Only tasks from the lists I named.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
Last, save these steps as a skill called 'Daily Team Update' so you do it this way each time I start the work day.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 10: Leading Up and Down the Chain of Command
What it does: Turns the way you do a job into a clean ClickUp task with a checklist, so anyone on the team can do it the same way.
Use it when: The how-to for a job lives in your head and new people do it differently.
You get: A task with a checklist in order, the why for the tricky steps, and how to save it as a template.
Open in
See the prompt
You are my process writer, with access to ClickUp.
The job: [for example: closing up a job site]
How I do it, rough: [type it out, in any order]
Who does it: [role]
1. Put the steps in order. Each step starts with a verb and is under 12 words.
2. Mark the steps that are easy to skip but matter, and add why in under 10 words.
3. Add the check at the end: how they know it's done right.
4. Show me. After I say yes, make a ClickUp task named "[job] checklist" in the list I name: [list name], with the steps as a checklist.
5. Tell me how to save it as a template in ClickUp so we can reuse it.
Rules:
- Only my steps. If one seems missing, ask, don't add it.
- Under 20 steps.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
Last, save these steps as a skill called 'Checklist From Steps' so you do it this way each time I write down how we do a job.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: The E-Myth Revisited, Michael E. Gerber, Chapter 18: Your Systems Strategy
What it does: Plans and builds a sales list in ClickUp with the stages, fields and views you need, so leads stop living in your head.
Use it when: You use ClickUp for jobs and track leads on sticky notes.
You get: Stages, a short set of custom fields, 3 views, and the list built in ClickUp after you say yes.
Open in
See the prompt
You are my pipeline builder, with access to ClickUp.
What I sell: [service]
How a sale goes now: [rough steps from first call to a yes]
How many leads a month: [number]
1. Turn my steps into 5 to 7 statuses, in order, plus Won and Lost.
2. Pick custom fields, no more than 6: for example, deal size, source, next step, next step date, phone.
3. Plan 3 views: board by status, a list of next steps due this week, and Lost with the reason.
4. Write the rule for each status: what must be true for a lead to move into it.
5. Show me. After I say yes, set up the list in the space I name: [space name]. Tell me anything the connector can't set up, so I do it by hand.
Rules:
- Keep it simple enough to update in 30 seconds after a call.
- If you have to pick something I didn't give you (a name, a time, a setting, a day), mark it (suggested).
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.
Last, save these steps as a skill called 'Sales List Setup' so you do it this way each time I set up a sales list.
Connect first: your files. The steps for each AI are on one page. Then the prompt reads it for you. It ends by saving itself as a skill.
Built from: Gap Selling, Keenan, Chapter 18: Manage the Pipeline
Simple AI
+1Team and officeRun the business