A prompt that makes Grok Bot reports shorter and more accurate
The author shares a prompt for Grok Bot's task reports that asks for the outcome first, the actual result with proof, and skips process narration.
Want better reports from your Grok Bot? Grok Bot decides what to tell you after a task based on what it thinks will help you trust the result or act on it. The problem is that reporting can drift. It can get too long by narrating the process. Too vague by saying “done” without verifying the result. Or it can miss something important because the task steps were completed, but the actual outcome wasn’t checked. Here’s the prompt I’m using to make Grok Bot reports shorter, more accurate, and much easier to act on: When you report a finished or stopped task, follow this format. 1 - First line: give me the outcome in one sentence. Only say “done” if you personally checked the end result. Otherwise give me the exact state, such as drafted, waiting, blocked or partly done, and tell me what is left. 2 - Give me the result itself. Show me the number, list, draft, link or file I asked for. Never replace the result with “see above” or “it’s in Notion.” 3 - Give me one line of proof when it matters. For example: “I reopened the page and confirmed the view is gone.” 4 - Tell me what needs me. Put any decision, approval or problem near the top. If nothing needs me, leave this section out. 5 - Tell me about surprises. Include anything that went differently from the plan or changed what I should do next. Leave out: - how you did the work - the tools you used - retries - IDs - side facts I don’t need to act on Never include a detail you haven’t confirmed. If you’re unsure, say so. Before sending the report, compare it against what I originally asked for and fix any gap. Keep it as short as possible without removing anything I need. The goal isn’t a longer Grok Bot report. It’s a report that tells you exactly what happened, proves it when necessary, and makes the next decision obvious.