BotShelf Vampire BOTSHELF VAMPIRE Register

GROK BOT TOOLS · CHECKLIST

Plan a routine usage budget

Estimates scheduled and event-driven runs against documented limits. Stops before increasing activity with unknown counts or allowing sending, publishing, payments, deletion or production changes.

No sign-upChecklistGrok BotRoutinesUntested

Where it goes

Nothing to paste. This is a list for you to work through with the app open. You can also paste it into a chat and ask the Bot to walk you through it one step at a time.

First three moves

  1. Fill the blanks with your own counts and list the owning Bot's routines.
  2. Calculate the scheduled runs in the busiest hour across all Bots.
  3. Count matching new events during a busy hour instead of using an average.

Where it stops

Blanks to fill

BlankWhat goes there
[BOT_NAME]The Bot whose routine plan you are reviewing.
[SCHEDULE_MINUTES]Each regular schedule's interval in minutes; use its own value for each schedule, at least five.
[SCHEDULED_RUNS_PER_HOUR]Scheduled runs across all Bots during the busiest planned hour.
[PEAK_EVENTS_PER_HOUR]Expected event-triggered runs across all routines during a busy hour, counting each matching routine.
[WEEKLY_RUN_BUDGET]Your own weekly run-count target; this is not a product usage allowance.

Replace every bracket. Leave none behind.

The text

Download text.md Fork it Results & questions

Unofficial checklist: count the runs your routines will make before you add one or raise a frequency.

1. List the routines [BOT_NAME] owns, plus the ones you plan to add. A Bot can own up to 50.
2. For each schedule, work out runs in its busiest hour: 60 divided by [SCHEDULE_MINUTES], rounded up. An interval under five minutes is not allowed.
3. Add the schedules of all your routines for the busiest hour and write the sum as [SCHEDULED_RUNS_PER_HOUR].
4. For each event trigger, count matching events in a busy hour, not an average hour. When one event matches several routines, count each. Write the sum as [PEAK_EVENTS_PER_HOUR].
5. Read every Slack trigger again. "Any message" in a busy channel, or all of Slack, can fire far more often than a mention or a phrase in one channel.
6. Add the two sums and the tests you plan to press. Compare with 300 runs per hour for all routines together.
7. Check each routine alone against 200 runs per hour.
8. Set [WEEKLY_RUN_BUDGET], your own weekly target. Every run consumes usage, and the weekly usage limit is separate from the hourly run limits.
9. Read the run records of the routines you already have. Only the 20 most recent are kept for each, so read them before they roll off.
10. Look for runs that failed with "Automation run rate limit exceeded". Failed runs are not retried automatically. Read what a failed run finished before you run it again by hand.
11. If the plan is over any limit or over your own target, lengthen intervals or narrow the matching rules. Keep the work that must happen.
12. If a count is still unknown, leave the frequency as it is and write the open question down. Counting runs approves nothing: sending, publishing, purchasing, paying, deleting and production changes stay behind approval.

License: MIT. Free, no sign-up. Use is at your own risk. BSV does not run it or set it up for you.

What it adds to the official page

The official page states routine and run limits. This checklist adds a busiest-hour calculation, a count for matching events and a personal weekly run target without treating run counts as usage units.

Sources

The product facts in this text come from these official pages, read on 2026-11-18. Products change: when a page and this text disagree, the page is right.

All Grok Bot tools Download all (ZIP) Search the shelf