One outcome
A review list, a cited brief, or a keep-or-switch card — not “be my assistant.”
Use cases
Grok Bot use cases — start with one job
Pick one reversible job. Name the Bot after that job. Paste a brief that says what to return and when to stop. Do not stand up twelve Bots on day one.
How a first job should look
Official Get started asks for five parts. Community writeups that actually shipped work use the same shape.
Named sources
Inbox, CRM view, attached file, or the site you will take over to sign in.
A hard stop
Do not send, enroll, delete, book, or pay until you say so. Description beats a later “stop.”
Copy a starter job
Original briefs on this site, written to the official pattern: own one outcome, start as read-and-prepare, keep money and sends behind approval. Open the official use-cases for the longer role list.
Five minutes
Warm-up: one document
A cited brief from a file you attach. No connector. No login.
I attached one document. Give me (1) five bullets on what it says, and (2) every date, decision, and open question with a page or section cite. Leave the file unchanged.Chief of Staff
Morning attention list
What changed, what needs you, and what can wait. One door, not twelve Bots.
You are my only door today. Review yesterday across my inbox, calendar, and meeting notes against the priorities I pasted. Return only items that map to those priorities. For each: source, why it matters, the next step, and whether I owe a decision. Do not send messages, create more Bots, or change meetings.Ops
Inbox to drafts
A sorted pile plus replies in your voice. You still hit send.
Walk this inbox. Group messages into needs me, can wait, and junk. Draft replies in my voice for the first group only. Do not send, archive, unsubscribe, or delete.Sales
Outbound research pack
Scored accounts and review-ready drafts. No enroll, no send.
Research the accounts in this list (or this CRM view). Score each against the ICP I attached and any recent intent you can show. Name up to three contacts per account and draft email plus LinkedIn in the style samples. Skip anyone already in a sequence. Return a review list. Do not send or enroll anyone.Life
Declutter audit
A numbered list of unused mail, Drive clutter, and paid subs. Approval before any cut.
Audit email, Drive, and paid subscriptions. Return a numbered list of what looks unused and the evidence. Wait for my yes before you delete, unsubscribe, or spend.Life
Travel hunt
Keep-or-switch options with fees. The last click stays yours.
Find the upcoming trip in my calendar or the confirmation I pasted. Compare the booked fare and stay with three cheaper options, including change fees. Recommend keep or switch, with the total after fees. Do not book, cancel, or enter payment.From X — jobs people actually posted
Official @bot recap on 2026-08-19 quoted eleven field posts (fetched 2026-09-04). Each card is the original. This site does not invent outcomes.
Text a robot vacuum
Yun-Ta · original post
Build a site, buy the domain, deploy
Wayne Sutton · original post
24/7 digital declutter
Peter Yang · original post
Support mail and refunds
Gergely Orosz · original post
Custom game art assets
Danny Limanseta · original post
Office manager for a shop
Jon ONeill · original post
Play a retro game on the cloud PC
Peter Yang · original post
Sit in on a missed meeting
Kiara · original post
Drive an Arduino LED ticker
KettlebellDan · original post
Chase merchant refunds
Darian Shirazi · original post
Overnight sales prospecting
Krista Letz · original post
Threads worth opening
High-signal X writeups that teach a first roster. Open the post; do not treat a list as a shipped result.
X · GrokBotDev
Five starter workflows
Inbox detox, a weekly “be happier” pass, a grocery team, a morning YouTube brief, then one Chief of Staff.
X · klöss
21 jobs from the official recap
Chief of Staff, office manager, inbox purge, outbound in your voice, CRM hygiene, refund recovery — a map of the @bot thread.
X · Dan McAteer
Chief of Staff in 15 minutes
Pasted a CoS guide, connected Gmail, Slack, Jira, and Granola. Field note, not a billed outcome.
X · s1rozha
One job per Bot
Email Bot at 7:30, sponsor-lead labels on a timer, calendar Bot separate. The trick is stopping using it as chat.
X · Greg Isenberg
One-person company stack
Friend’s newsletter desk on Grok Bot agents. Best-practices thread — treat as a pattern, not a revenue claim.
X · @bot
Connect Stripe Link, then shop
Official: Bot raises a spend request; you approve; a one-use card appears. US first. Approval stays with you.
Skills worth installing first
Most “Grok Bot skill” repos on GitHub are 0–1★ dumps. These have a documented Grok Bot or Cursor-marketplace install path and recent maintenance (checked 2026-09-04). A skill you save after two good runs still beats a random pack. Full catalog: Tools.
Compound Engineering · 24.8k★
Install once in the Cursor marketplace. Grok Bot inherits that plugin library. Do not clone the repo onto the Bot computer.
superpowers · marketplace
Largest general skill pack Grok Bot can load through Cursor: plan, debug, write.
Aaron Marketing Skills · 2.7k★
120 marketing skills as an 8-bot staff on Grok Bot. Named teammates, not a SKILL.md dump.
Grok Ship · 156★
Grok-Bot-native software factory. Tell a Bot to follow GROK_SHIP.md. Scout vs ship; you merge.
Gojiberry Sales OS · 93★
Outbound pack with a hosted MCP. Intent, enrich, LinkedIn, replies — do not invent contacts.
Vercel plugin · 275★
Official Vercel connector: deployments, logs, domains. Watch the OAuth redirect thread.
xAI plugin marketplace · 211★
Official .grok-plugin catalog. Browse here, then install through Cursor / Grok Bot plugins.
Skip the 195-skill catalogs. Repos that only ship a pile of SKILL.md files with no stars, no license review, and no Grok Bot install steps stay off this list.
High-star GitHub — not the official app
Self-hosted alternatives and companion repos. They are not xAI’s Grok Bot. Side-by-side: official vs OpenMausBot, rakazo, gawkbot, OpenClaw. Reconstructed clients and grok.com prompt dumps are omitted on purpose.
OpenMausBot · 2.1k★
Self-hosted alternative with a VM the bots can use. Apache-2.0. Not the official client.
rakazo · 1.9k★
Bring your own model and sandbox. Web, Electron, Expo. Apache-2.0.
gawkbot · 1.3k★
Local-first: npx gawkbot. Approval gate on every send. Not xAI’s cloud computer.
opengrok · 417★
Model picker inside the official Grok Bot app. Keys stay on your machine. Third-party.
plugin-marketplace · 211★
Official xAI .grok-plugin catalog that Grok Bot inherits under Cursor plugin policy.
botdirectory.ai · 160★
Paste-ready agent prompts for Grok Bot and Rakazo. Community directory.
awesome-grok-bot · 220★
Upstream CC0 list this catalog is built from.
First week
1
Install and sign in
Desktop or phone. Cursor account. Have one real login ready — empty demos burn the week.
2
One Bot, one job
Short name. Paste a starter brief. Watch the computer. Take over for password and 2FA — never paste those into chat.
3
Correct, then save a skill
Fix the output once. Ask it to keep that format. Save the method. All Bots share one computer.
4
Routine only after two good runs
Schedule the digest or the research pack. Tests do real things. Keep writes behind approval.
Do not start with money, customer sends, or twelve Bots. Nate’s “eight hours, twelve Bots” is a review, not an ops plan. Debbie’s flights case stopped at the last click. Gergely’s refunds case still needed a human before money moved.
Read these first
Guides that teach a first roster. This site does not reprint them.
Official Get started
Install, name the Bot, then a five-part first task.
Official use cases
Eight roles with a first prompt each. Read-and-prepare, then a routine.
@bot: jobs people ran this week
Official X recap of 11 field jobs, each quoting the original post.
Debbie: how to start
Name the job, sign in on the computer, start with one Chief of Staff.
Peter Yang: five to try
Advisor, YouTube researcher, X scout, inbox declutter, travel concierge.
Nate: two Bots, not twelve
Review of a first day. Start with work that finishes, not a briefing.
Honest early verdict
One reversible job first. Shared computer and weekly usage are the real limits.
Run a first week
Company OS files, a Chief of Staff, then a daily plan that cites sources.
Grok Bot for PMs
Official-adjacent roster: Chief of Staff plus narrow specialists. Sends stay behind review.
Field cases
What people actually handed off
54 sourced examples. English summaries here are original: who, what job, what the source claimed. Not independently reproduced. Numbers or returns not written in the source are never invented. Upstream list: awesome-grok-bot (CC0).
Engineering / product teams · n2parko
Product roster and PR handoffs
SpaceXAI product publicly showed a roster of Chief of Staff + eng manager + five eng ICs + Databricks + PM, with screenshots of agents handing off PRs. This site did not independently verify outcomes beyond those screenshots.
Architecture observations · Lee Robinson
Four technical bets
Public discussion of product shape: thin UI, thin client / thick server, always-on computer, browser as a first-class tool. Design observation, not a completed business case.
Life / shopping · Debbie
Booking flights
Author had a Bot act as travel assistant on airline sites. Her conclusion: nearly usable, but missing the last click; the video shows the attempt and failure points. She did not claim a completed ticket.
Life / shopping · Debbie
Sunday-night gluten-free beer
Chief of Staff + home Bot: added paper towels from the phone and completed an order; built a gluten-free beer cart on a grocery site and picked a delivery window. Login was hard on phone; desktop takeover got in. Author stresses this is computer use, not chat.
Life / shopping · Yun-Ta
Booking a table while walking
Mixed Chinese/English voice; Bot scanned the calendar and booked a restaurant. Outcome as claimed by the author; this site did not reproduce it.
Engineering / product teams · Gota
One roster, twelve jobs
Public roster covering image factory, research briefs, 3D, travel debates, unsubscribe, running a local LLM in a VM, and more. Job list, not a per-item acceptance report.
Ops / admin · Box
Credit committee pack
Reconciled materials, then wrote back to Box via MCP. Details in the original post.
Engineering / product teams · mrfundman
Teaching a WordPress update once
Used Teach a task on a real CMS instead of writing a deploy script first.
Engineering / product teams · KettlebellDan
Arduino updates
Bot pushed hardware updates so the author did not have to watch X. Same author also has an LED ticker case.
Engineering / product teams · Nate
Eight hours, twelve Bots
Review article asks whether a high-tier seat is worth it and shows a real day-one roster. Dollar amounts follow the original; this site does not restate unverified bills.
Ops / admin · YouTube demo
~19 minutes to 24/7 support
Uses routines to stand up a support Bot instead of rewriting a ticketing system. Duration from title/summary; this site did not time it.
Engineering / product teams · Farzad
Webby / Shotry / Writey
Named specialists plus an orchestrator — a shape that keeps recurring in the community. Original post includes team screenshots.
Research / briefs · Sid
Polymarket daily settlement brief
Bot scanned markets that settled that day and wrote a report.
Architecture observations · Logan
The unlock is the computer, not 4.6
Argument: without API, MCP, or a hosted browser, a Bot uses software like a human. Commentary, not a work ticket.
Architecture observations · Japanese note
A week on the shared VM
Japanese hands-on notes on living on the shared VM. Read the original; this site does not excerpt long passages.
Ops / admin · Peter Yang
Declutter Bot
Demo: audit email, Drive, and paid subscriptions; wait for approval before delete.
Ops / admin · Gergely Orosz
Stripe support refunds
Connected a Bot to support email and Stripe to proxy refunds, with human confirmation before money moves.
Ops / admin · Mike P
Cleaning a huge inbox
Had a Bot walk two Gmail accounts and toss junk the owner would not touch by hand. Original post states scale; this site does not rewrite the numbers.
Life / shopping · Yun-Ta
Texting a robot vacuum
Chief Engineer Bot talked with @maticrobots so the human could text the vacuum from anywhere.
Engineering / product teams · Wayne Sutton
Ship a site from two phone prompts
Convex + Cloudflare plugins; tryground.dev live demo; bought domain and redirects from the phone. Details follow the original post.
Creative production · Danny Limanseta
Card assets in two hours
Bot read the codebase, opened the author’s image-gen page, cropped transparent PNGs, and wired card assets back into the game. Counts follow the original post.
Ops / admin · Jon ONeill
Plumbing-shop office manager
Drain-and-sewer shop owner handed office-manager work to a Bot in the first 24 hours.
Life / shopping · Ben Lang
Internal job list
Public internal work examples: Starlink-leaning flights, recipes to Whole Foods, film-scan EXIF, contractor quotes, and more.
Research / briefs · Gavin Baker
Podcast summaries
Author compared Grok Bot to another Claude Code moment and said a podcast-summary setup came together quickly. Duration wording follows the original post.
Sales / GTM · Krista Letz
Enterprise GTM roster
SpaceXAI enterprise sales roster: Chief of Staff, overnight prospecting, per-account specialists, live slide updates.
Creative production · Peter Yang
Playing Commander Keen on the cloud desktop
Installed and played Commander Keen on the Grok Bot cloud desktop; author mentioned latency. Point: this is a real computer.
Meeting notes · Kiara
Bot sits in on a missed meeting
SpaceXAI field engineer had a Bot join a meeting she missed, introduce itself, and take notes.
Engineering / product teams · KettlebellDan
Arduino LED ticker
Bot talked to Arduino; the light board scrolled prices, spark lines, and SpaceX news. Code and hardware follow the original post.
Ops / admin · Darian Shirazi
Chasing five merchant refunds
Bot found unrefunded returns in email and wrote five merchants. Author claimed recovery exceeded the monthly fee; that comparison is from the post — this site did not see the bill.
Engineering / product teams · Grokularity
Site built by a Bot team
Non-coder said a Grok Bot team stood up grokularity.xyz in a day: humans read; only verified Grok agents write.
Sales / GTM · thoughtpilot99
Signal outbound recipe
GitHub recipe: hunt buyer signals, return a ranked list, draft two outreach scripts for a human to send.
Trading experiments · jjregier
Grok-Bot-Fund
Personal paper-to-live “hedge fund” desk with three Grok Bot teammates on the cloud computer; versioned playbook merges only via human PRs. Experimental — read the repo; not a return promise.
Research / briefs · WebDevJasonCameron
Market research desk
File-based market research desk: company mission, analyst instructions, scored opportunities, decision log, same repo layout.
Engineering / product teams · mtrxdev
build-brief into local grok
Reusable desk that interrogates a raw idea into a grounded Grok Build brief (PROFILE + BOT-SKILL + check gates), print-first, then paste into local grok. Target output is Grok Build, not Grok Bot itself.
Trading experiments · HammeredSmithy
Bull Desk / Webull
Seven-agent trading desk ported to Webull OpenAPI (US users): research, positions, id-gated execution approval and review; paper sandbox before live keys. Experimental.
Sales / GTM · jay-sahnan
Self-serve growth team
Shareable multi-Bot growth team (growth lead + specialists), narrow roles with handoffs; human approval before shipping or outreach.
Research / briefs · palehonk0-o
Market memory pack
Evidence-first implementation pack: use Grok Bot to turn public pages into decision briefs, paired with a public X article walkthrough.
Engineering / product teams · Logos52
Fleet public packet dump
Weekday public dump of files a Grok Bot fleet writes under /workspace on the shared cloud computer, mirrored for Mac /fold skill intake.
Engineering / product teams · jblack4vols
Per-Bot durable knowledge log
Durable logs for a real roster: decisions, delivered work, and long-term preferences dated in America/New_York.
Ops / admin · bilauitmcuti
UiTM calendar + MCP
Malaysia UiTM academic calendar assistant on Grok Bot; remote MCP supplies class, holiday, and exam dates.
Architecture observations · Greenlit Books
One reversible job, not a reorg
Field note: the product is approachable, still early. Start with a checkable, reversible workflow. Weekly usage, the shared computer, and money folklore are the real limits. Dollar claims in social posts are mostly unverifiable.
Ops / admin · Refound
Five-day company OS
Written first-week: put standing rules in the Bot description, cite source-of-truth files, plan the day with sources shown, then hang a routine only after the brief is reviewable. External actions stay behind approval.
Engineering / product teams · xAI guides
PM roster that stays quiet
Official-adjacent PM writeup: Chief of Staff owns calendar, Slack, and inbox; specialists stay narrow. Author still reviews external sends, purchases, and deletes.
Architecture observations · xAI docs
Eight official starter roles
Official use-cases page: sales outbound, talent scout, paid media, expense manager, product performance, bug reproduction, account health, Chief of Staff. Each role owns one outcome and starts as read-and-prepare work.
Research / briefs · Composio
Parallel research swarm
Practitioner guide: persistent teammates on a cloud computer, then bonus jobs such as a competitive-intel swarm, an open-source audit, and a fact-check engine. Treat as a pattern list, not a shipped outcome report.
Life / shopping · techAU
Shopping with Stripe Link
Field writeup of Bot shopping via Stripe Link: the Bot can raise a spend request; you approve in Link; only then does a one-time card appear at checkout. Vague briefs produce vague carts. Approval still sits with you.
Architecture observations · @bot
Official weekly field recap
Official 2026-08-19 thread: eleven jobs people actually ran that week, each quoting the original post. Vacuum, site deploy, declutter, refunds, game art, office manager, meetings, LED ticker, prospecting.
Life / shopping · @bot
Buy things with Stripe Link
Official 2026-08-28: connect Link, send the Bot shopping, approve every spend request, then a single-use card is minted. US first; mobile later. This is delegated checkout, not unattended spending.
Ops / admin · GrokBotDev
Five starter workflows
X thread with five first jobs: six-month newsletter detox (keep vs unsubscribe), a weekly “be happier” pass from mail and calendar, a three-Bot grocery team, a 7am YouTube summary, then one Chief of Staff.
Architecture observations · klöss
21 jobs mapped from @bot
Community map of the official weekly recap: Chief of Staff, office manager, inbox purge, outbound in voice, CRM hygiene, refund recovery, and more. A list, not a per-item acceptance report.
Ops / admin · Dan McAteer
Chief of Staff in 15 minutes
Author said a CoS was working in about 15 minutes after connecting Gmail, Slack, Jira, and Granola. Duration and connectors follow the post; this site did not time it.
Ops / admin · s1rozha
One job per Bot, on a timer
Public setup: an email Bot at 7:30, sponsor-lead labels on a work-hours timer, a separate calendar Bot. Author’s point: stop using Grok Bot as chat.
Sales / GTM · Greg Isenberg
Newsletter desk as a one-person company
Thread: a friend runs a newsletter business on Grok Bot agents, with a best-practices list for non-technical operators. Pattern post — not a verified P&L.
Ops / admin · RoundtableSpace
Daily job list for a first roster
Public job menu: inbox, daily briefing, expenses, calendar, research, account management, notes prep. A menu of roles, not a shipped-outcome report.