Work
A three-line running notes file so routines stop redoing work
Your 6pm run repeats what the noon run already did, because each run starts from zero.
What hurt
ShareGrokBots (@ShareGrokBots) suggests one small file that a routine reads first and writes last, so every run starts where the last one stopped. Not affiliated with xAI.
What to install or create
Each run appends three lines, newest at the bottom: what it did this run, anything left unfinished and why, and what to check first next time. No more liking the same post twice, re-sending the same summary, or re-checking things that were fine.
Bots
No new bot. Follow the first-run steps.
Plugins
None on day one. Follow the first-run steps.
Files
A running notes file per routine: three lines per run, newest at the bottom.
Routines
None on the first run. Watch one manual pass first.
The prompt
What goes in the notes file (author-quoted)
Quoted from @ShareGrokBots — as published. Do not invent a second system prompt.
1. What it did this run, in one line. 2. Anything it left unfinished, and why. 3. What it should check first next time.
First run
- 1Read https://x.com/ShareGrokBots/status/2107607371975368991 (credit @ShareGrokBots).
- 2Pick one routine that runs more than once a day.
- 3Ask the bot to keep a notes file for it: read it at the start of every run, write to it at the end.
- 4Use the three lines below for every entry.
- 5After a day, read the file and check the later runs picked up where the earlier ones stopped.
Approval fence
If the routine sends or posts, the notes file is also how it knows it already did — check it before any repeat send.
What to tweak
Read first, write last. The file doubles as a plain diary when something goes wrong.
Source
ShareGrokBots.com @ShareGrokBots · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.