Ask which of your past prompts should be routines

How this helps you

You find the jobs you do by hand that could run on their own, without guessing.

✦ Try it

Look through the prompts I've sent to my different Bots. Which of these should turn into a routine or its own Bot? For each one, say whether it's the same check every day or something that happens when an event occurs.

Fill in: No placeholders. Run it in your main or chief of staff Bot.

What they did

@GrokBotRadar points out that every prompt you keep retyping is a job a Bot could do on its own. They asked their Bots to look back through the prompts sent to them and say which should become a routine or its own Bot. It found seven: six belonged as routines on Bots they already had, and one needed its own Bot. The catch, from the post: not every repeat needs a clock. If it is the same check every day, make it a routine. If it is "when X happens", use a trigger instead, because a routine that fires too often eats your usage. They credit the idea to Friday's Grok Bot Q&A.

Who it's for: Anyone who has used Bots for a couple of weeks and keeps typing the same requests.

Before you start

A week or two of chats with your Bots, so there is history to read.

How to try it

Ask your main Bot the prompt below.
For each suggestion, check whether it is a daily check or a reaction to an event.
Make the daily ones routines on the Bot that already does that work.
Make the event ones triggers, or slower checks.
Only create a new Bot when nothing you have fits.

What to expect

A short list of repeat requests, each marked routine, trigger or new Bot, with the Bot it belongs on.

Common mistakes

Making every repeat a routine. Event-driven jobs should be triggers.
Setting a fast schedule "to be safe". It costs usage on every run.

Related tips

Create a routine by asking, then ask what else to schedule: Describe a schedule in one sentence to make a routine, then ask the Bot which routines it thinks you need.
Make routines cheaper: events, slow schedules, change checks: A 5-minute routine wakes 8,640 times a month. Use an event trigger, the slowest schedule that works, and a cheap change check.
Keep routines one line long: The schedule says when. The skill says how.
Find the tasks you repeat every week, ranked by time saved: One prompt makes your Bot read two weeks of your email, meetings, Slack and docs, list what you do over and over, and pick the top three to automate.