Standing orders for a scheduled Grok Bot (free sample)
by PaperChaseWebb
The card we use for every scheduled Grok Bot job, a cron table in local time, and two reporting rules (quiet by default, end of day) that cut most of the noise.
- Price
- Free
- Difficulty
- Beginner
- Setup
- 5 min
- Format
- .md file
standing-orders-for-a-scheduled-grok-bot-free-sample.md · 2 KB · direct download, no signup
What you end up with
Your scheduled bot runs in the right time zone, stops when its job ends and messages you only when something needs you.
What you get
- The standing order card
- A cron table in local time
- Quiet-by-default and end-of-day reporting rules
Who it is for
Anyone whose scheduled bot messages at odd hours, reports too often or keeps running after its job is over.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free.
Time to result: Five minutes per routine
Sample prompts, free to use
Every [day / week] I [manual task]. Write a standing order card: cron line in [zone], exact or flexible, run and report windows, end date, steps, done-when check and a REPORT ONLY IF rule.
The REPORT ONLY IF line does most of the work.
Free preview of the file
# Standing orders for a scheduled Grok Bot (free sample)
A free sample from Grok Bot Templates: personas, standing orders and handoffs, by PaperChaseWebb. Written for Grok Bot.
A bot that runs on a schedule is only as good as the order it reads at the start of each run. Loose orders give you messages at odd hours, reports nobody reads and watches that never stop. This sample gives you the card we use for every scheduled job, a cron cheat sheet in local time, and the two reporting rules that cut most of the noise.
## The standing order card
Paste this into the bot's instructions or a file it reads at the start of every run.
```text
STANDING ORDER: [short name]
OWNER: [bot name]
SCHEDULE: [cron line] in [time zone], [exact or flexible within N minutes]
WINDOW: run [any time / hours]; report [weekdays 07:00 to 19:00 local]
EXPIRES: [date, or the condition that ends it]
JOB: [one sentence]
STEPS: 1. [...] 2. [...] 3. [...]
DONE WHEN: [the check that proves the run worked]
REPORT: [every run / end of day / only if] to [who]
REPORT ONLY IF: [conditions worth a message]
NEVER: send, post, spend, trade, deploy or delete without my yes for that one action.
```
## Cron in local time
| You want | Cron line |
|---|---|
| Weekdays at 7:30 AM | `30 7 * * 1-5` |
| Hourly, 7 AM to 7 PM, weekdays | `0 7-19 * * 1-5` |
| Every 30 minutes, working hours | `*/30 7-18 * * 1-5` |
| Mondays at 9 AM | `0 9 * * 1` |
Write the zone next to the line ("America/Chicago", not "my time"). If the plaWorth knowing
- Check whether your setup runs schedules in local time or UTC before you trust the first run.
Questions
What is in the full pack?
8 ready-to-paste personas, event routine recipes, multi-bot handoffs with a decision log and four approval gates, memory hygiene rules, a 20-point check with 10 test scenarios, and 12 prompts.
Details
Version 1.0 · Updated Oct 26, 2026 · Markdown version of this page
License: Personal and commercial use. Download terms
Related
Grok Bot Templates: personas, standing orders and handoffs
A Markdown pack for setting up Grok Bots that do useful work on a schedule: 8 ready-to-paste personas, standing order cards for scheduled routines, event routine recipes, multi-bot handoffs with a decision log and four approval gates, memory rules and a test set.
Ask-first rules for AI agents: hard nos, approval cards and a test set
Paste-in rules that make an agent ask before it sends, spends, posts or deletes, define what a real yes is, and stop retries after a no, plus 12 test scenarios to check it.