How to create a Grok bot

1. Decide the one job

Bots that try to do everything do nothing well. Write one sentence that names the outcome and the person it is for: “Every weekday at 8am, send me a five-bullet brief on what changed in my three competitors.” If you cannot write that sentence, the Bot is not ready.

2. Start from a template (optional, but faster)

Search the directory for your job. If a template is close, add it and edit the instructions rather than starting from a blank page. You get the creator's tested wording, skills and routine, and your copy is independent — changes you make never affect theirs.

3. Write the job description

In the Grok Bot app, create a new Bot and give it a name, a job title and a description. The description is what steers the Bot, so include:

• What it owns — the outcome you just wrote.
• Inputs — which sites, accounts or files it should look at.
• Output — the format you want back (bullets, a table, a draft email).
• Escalation — what it must ask you about before acting: sending, buying, publishing, deleting.
• Quiet rules — when it should say nothing because nothing changed.

4. Add skills

Skills are reusable instructions for a specific task, such as “summarize an earnings call” or “triage a GitHub issue”. Write them by hand, or let the Bot record you doing the task once and draft the skill for you to review. Keep each skill small and test it on a real example.

5. Connect accounts carefully

Bots sign in to tools on the shared cloud computer. Every Bot on your account can reach what you connect, so add accounts one at a time, prefer read-only access, and keep anything consequential behind your approval. When a site asks for a two-factor code or a CAPTCHA, the Bot hands control back to you.

6. Turn it into a routine

Once the Bot does the job well on demand, assign a routine: a schedule or an event that wakes it up. Routines use your plan's usage every time they run, even when there is nothing to report, so pick the slowest cadence that still works and limit it to working hours where you can.

7. Review the first week

Read every output for the first few runs. Tighten the description where it drifts, cut sources that add noise, and only widen access once the Bot's judgment matches yours.

8. Share it

When the Bot is genuinely useful, share it as a public link on x.ai and submit it to this directory. Write a one-line job description and be honest about what access it needs — listings that say exactly what they touch get added far more often.

Example job description

“You are my Competitor Desk. Every weekday at 8:00, check the blogs, changelogs and X accounts of Acme, Globex and Initech. Send me at most five bullets on meaningful changes, each with a link. If nothing meaningful changed, send nothing. Never contact anyone or post anything.”