How this helps you
Long chats get slow and costly. A handoff file lets you continue in a fresh chat without losing the goal or decisions.
Save a handoff file with the current goal, the decisions we've confirmed, the relevant files and the next action. Then give me a short prompt I can paste into a fresh chat to pick up from here.
What they did
@Greshamtrade suggests saving a /clean-start prompt as a skill. It isn't a built-in command. The Bot saves the current goal, confirmed decisions, relevant files and next action in a handoff file, then gives you a short prompt to continue in a fresh chat. The same post suggests four more private skills in the same style: changed-since (only investigate items whose timestamps or IDs changed since the last run), batch-the-noise (group non-urgent checks into 3 daily batches and show the schedule first), use-the-receipt (reuse a saved valid result instead of redoing work) and stop-the-loop (no more than 2 attempts at a failing step, then return the partial result and exact error). Start with your busiest recurring workflow and compare usage before and after.
Who it's for: Anyone whose chats run for days.
How to try it
- Ask your Bot to save the prompt below as a skill called clean-start.
- Check it appears in the / menu as one of your private skills.
- When a chat gets long or slow, type / and run clean-start.
- Open the handoff file it saved and check the goal, decisions and next action are right.
- Paste the short prompt it gives you into a new chat.
- If you like the pattern, add the post's stop-the-loop rule as a second skill: at most 2 attempts at a failing step, then return the partial result and the exact error.
What to expect
A HANDOFF.md file and a short prompt you paste into a new chat.
Common mistakes
- Treating it as built in. You save it as your own skill and run it from the / menu.
- Trusting the post's savings figures. The author says the prices are illustrative API costs, not measured Grok Bot savings.
Related tips
- Analyse your own usage CSV: Export usage from the Usage page and ask your Chief of Staff Bot how to cut it.
- 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.
- Do it by hand, save a skill, then schedule: Most automations break because they're scheduled before they've worked once.
- Keep long jobs sharp: helpers, files and the cheapest tool first: How the Grok Bot harness avoids running out of context, and how to ask for work in the same shape.
- Two habits that make usage last: batch requests, send words not screenshots: Every message makes a Bot reread the chat, so send related requests together, skip 'thanks' replies, and paste text or cropped images instead of full screenshots and PDFs.
Worth knowingThe same post suggests other skills too: /changed-since, /batch-the-noise, /use-the-receipt and /stop-the-loop (at most 2 retries, then stop with a partial result).
Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot skills tips