The prompt
Prompt
Adapt this outline. Do not treat it as a finished prompt.
Help me hire my first specialist Bot correctly:
1. Propose a real name + one job sentence (reject the name Assistant).
2. Take a brief in chat — no separate workflow builder.
3. Attach exactly one connector to start.
4. Have me show the task once; save a routine only after a clean dry run.
5. Keep non-trivial code work in Grok Build until the Bot path is proven.
Bound the clock. Quiet if nothing changed. Draft-only until I say send.
Start: ask what single job should exist before any second Bot.How it's set up
@arianlooterking posted the hire-in-10-minutes checklist (https://x.com/arianlooterking/status/2099008451003449652) and a follow-up on show-once to routine with quiet-empty and draft-only rules (https://x.com/arianlooterking/status/2099134554627883390), linking Introducing Grok Bot (https://x.ai/news/introducing-grok-bot).
- Follow the four steps literally.
- Do not add a second connector until the first routine is boringly reliable.
Why it works
The anti-pattern is a vague Assistant. The product is one named job that survives contact with Monday morning.
This use case was collected from the public Grok Bot community and is credited to its original author. Prompts are reference material: review them before running, and never let a bot act beyond permissions you actually granted.