Grok Bot playbooks tutorials

Start Grok Bot in an afternoon

Separate Grok, Grok Bot, and Grok Build, then set a safety floor, one bot, a skill, a Routine, and a quota rail.

The repo groups checked entries into nine sections. This page says what each section is for. Short reviews stay in the README.

A template, skill, or MCP is a grant of access. Do not let an ungated bot send, pay, or hold secrets.

When quota is nearly gone, pause everything, grade each Routine, then reopen one by one. High-frequency jobs stay silent when nothing changed.

Three to six bots hand work off as files, not as a group chat. Nothing goes out before a person approves it.

Scan public posts once a day and push a digest only when there is a real signal. Likes, replies, and reposts stay human.

Fetch public competitor pages on a schedule, drop timestamp noise, and push only material changes.

On Friday, draft the week from repo, doc, and calendar traces. Every item needs a link. A person edits and sends it.

Split research, draft, review, and posting. Hand off by file, approve once before publish, then reconcile.

Split spec, repro, pull request, and review. A person approves the spec and the merge. The reviewer bot does not write the PR.

Support, content, and research bots hand off by file. The person reviews on a fixed daily block.

Redact multilingual tickets, then triage them into drafts. Payment, security, and legal go to a person. The bot does not send mail.

Set the boundary and rollback before the demo. Afterward, write a reviewable skill card and dry-run it before a Routine owns it.