What the documentation establishes

Grok Bot is documented as a persistent teammate that can use a cloud computer and connected tools. The official onboarding guide covers account eligibility, installation, creating a Bot, and handing it a task. Check that guide for current access requirements before buying a plan; this page does not independently verify availability for your account.

The exercise below is an original starting task. It has not been executed or benchmarked by this wiki.

Documentation: Official getting started guide ↗ Grok Bot overview ↗

Start with an answer you can check

Pick a document you already understand: meeting notes, a public project brief, or a non-sensitive checklist. Ask for an action register with one row per commitment. You should be able to judge its completeness without spending an afternoon learning a new system.

A first task should reveal whether the Bot can follow your definition of done. Connecting five apps at once makes it harder to tell whether a bad result came from missing access, unclear instructions, or reasoning. Expand the task after the small version works.

  1. Choose one approved source with a clear date or version. Remove material the task does not need.
  2. Write down the expected output: action, owner, deadline, and supporting passage. Unknown owners should stay unknown.
  3. Give the Bot the file and the task below. Replace every bracketed field before sending.
  4. Compare its output against the original. Check one ordinary item, one ambiguous item, and one commitment with no deadline.
  5. Correct the instruction that caused a mistake, then try a different document before reusing the process.

Try this brief

This template deliberately asks for traceable extraction. A clean-looking answer is not enough if the source never assigned the work.

Try this brief

Use the attached [document name/version] to create an action register. Return a table with action, named owner, explicit deadline, source passage, and uncertainty. Include only commitments supported by the document. Mark missing owners or dates as unspecified; do not infer them. Then list ambiguous statements that need a human decision. Preserve the original file. Do not contact anyone or create tasks in another app. Finish with the number of commitments found and anything you could not read.

Original editorial template. Replace placeholders and review access before running.

Decide what to connect next

If the extraction passes review, choose one additional input that would improve the outcome, such as the current task list. Ask for a comparison before allowing edits. The next milestone is an accurate proposed change, followed by a reviewed change if you choose to authorize it.

  • Every action points to a passage you can locate.
  • Unspecified information is visible instead of filled in plausibly.
  • The output is complete enough to use after review.
  • You know which access the next task actually requires.

Sources & next steps

Capabilities are grounded in the documentation below. The workflow design and acceptance checks are editorial suggestions.

Build your own workflow brief ↗