Grok Bot routines

Run a read-only usage efficiency audit across my entire Grok Bot team. 1. Routine inventory: ask every Bot, including hidden Bots, to report its active routines, schedules, triggers, purpose and recent runs. Tell me anything you cannot inspect. 2. Frequency: flag hourly routines, short intervals and jobs that run more often than their results are needed. Recommend longer intervals or on-demand runs. 3. Triggers: find routines watching broad events such as every Slack message or every email, and recommend specific channels, keywords or conditions. 4. Duplicate work: find Bots checking the same sources or producing overlapping reports, and recommend one owner. 5. Task scope: find recurring jobs with vague or broad instructions and recommend tighter inputs, clear completion conditions and shorter outputs. 6. Workflow: find repeat tasks that could use an existing skill or connected app instead of navigating websites. Don't claim savings without measurements. 7. Usage review: check the usage information you can see, separate estimates from measured usage, and rank changes by expected impact. Give me one report: routines worth pausing, schedules worth reducing, triggers worth narrowing, duplicate work worth combining, workflows worth simplifying, and your top [five] changes, with evidence and trade-offs for each. Do not pause, delete, edit or create any routines, Bots, skills or connections without my approval.

Check [booking page links] for openings on [date] between [time window] for [party size]. Do it now and tell me what you see, then check every hour until [stop time]. Only message me when a slot I'd accept appears, with the time and the booking link. Don't book or enter any details yourself. If a page won't load or asks me to log in, tell me once and keep trying.

Go through [backlog] and score every open item: Reach (how many users it affects), Impact (1 to 3), Confidence (percent), Effort (days), and Blast radius (low, medium or high: how much could break). Score = Reach x Impact x Confidence / Effort. Sort by score, list the top 5 with one line each, and flag any high blast radius item as needing human review. Don't add new items unless they came from a real request.

Look through my work from the last two weeks: emails I sent, meetings, Slack messages, docs I edited, and anything else you can see.

List the tasks I did more than once, grouped by type. For each one, tell me:
- what the task is, in one line
- how often I did it
- roughly how long it takes me each time
- whether you could do it for me, partly or fully, and what you'd need access to

Then pick the top 3 to automate first, ranked by time saved, and suggest a routine or a dedicated bot for each.

Read public posts on X from the last [hours] hours about [niche]. Pick the 3 topics most worth a [format] from me, each with one line on why and the link to the best post. Then open my Notion database [database name]. If a topic fits an existing idea card, add the links to that card under Resources and tell me which cards you changed. Don't create new cards and don't post anything.

Build me a leadership Bot. Connect it to my meeting transcripts in [tool] and my team's Slack, including [channels]. Every Sunday morning, send me a short brief: what each team talked about this week, what decisions were made, and where that does or doesn't match my top priorities. My priorities are: [list]. Link the source of anything important and tell me what you couldn't read. Read only: don't post or reply anywhere.

Here are screenshots of my usage page and billing page: [screenshots]. Audit how my Bots use my weekly usage and build the results as a page called [Usage audit]. List every routine with its Bot, schedule and runs per week, and label each one Keep, Slow down, Change check or Retire, with a reason. For Change check, write the exact check-first line to add. Add a section for other drains: long chats, old group chats, browser jobs, third-party models, images and video. Mark which numbers are verified and which are estimated. Don't change, pause or delete anything until I approve.

When this webhook fires, read the meeting transcript in the request. Decide which Bot owns it: [routing rules]. Send it to that Bot with a 3 line summary and any action items, and file the transcript in [folder]. If it fits none of them, send it to me. Downstream Bots may draft but never send.

Set up a routine every weekday at [time] to go through my calendar for the day and make a prep doc for each meeting: who's attending, why we're meeting, recent emails with them and anything I promised. Send me each doc [minutes] minutes before the meeting starts. Skip [meetings to skip].

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.

Every Monday at 8am, check my email for renewals in the next 30 days, bills higher than last month, and price drops on things I've told you to watch. One short list with amounts and dates. Cancel or buy nothing without my yes.

Move everything in my [routine name] routine's instructions into a skill called [name]. Then change the routine's prompt to one line: run the [name] skill end to end. Show me both before you save.

Here's my usage CSV. Check this usage file, analyse my Bots' behaviour and tell me how we should optimise for usage. Rank fixes by usage saved. Don't change anything until I approve.

Right before you post or send anything, check the current time. If it's after 00:30 or before 7:00, skip this run and do nothing.

Check new signups and ping me only if one is real.

After every run, append one line to routines/log/[name].csv:
time,result,changed,minutes,needed_approval,note

result is one of: ok, no_change, draft_left, failed
note is under 12 words. Create the file with that header if missing.

Check the price of [exact product] at [shop links]. Only count the exact configuration. For each shop give: price, in stock yes or no, and the time checked. If a page won't load or the price isn't shown, write unknown; never guess. Message me only if a price is verified below [target price]. Then set this as a routine every day at [time].

Every weekday at 9:00 am, look through my Slack and email and send me a short report of what needs me. Then tell me three other routines you think I should have, based on what you know about my work.

Turn this into a clean one-page summary with headings: [paste text or attach file]. Then tell me what you weren't sure about.

Every night at [time], audit [repo] for [audit type]. For each improvement, start a cloud agent to make the change on its own branch and open a PR with proof: tests passing and [proof]. Keep each PR small and focused. Don't merge anything. In the morning, send me a list of PRs with one line each on what changed and the risk.