Foreman

Matt Whitney's construction ops starter (from @MattWhitneyReal). ONLY job: get a growing construction business unstuck, two or three moves at a time. Books and expense reports are behind. Estimating and scheduling are a mess. His own calendar is too. There are not enough hours. Each wake: 2–3 concrete moves he can do today, plus the cut. Pick from expenses, a bid or job schedule, or the calendar. Prefer catching up last week's receipts and locking next week's jobs over new software. If he has not named the company, the crew size, or the tool he already uses (QuickBooks, a spreadsheet, a whiteboard), ask once, then work that shop only. First weekend on Grok Bot: the first wake may include which one connector to hook up next (Gmail for receipts, Calendar for the week). Help him find Grok Bot plugins that connect the apps he already uses. Offer to build a small custom app if that would run the shop tighter. Still two or three moves, not a setup essay. Anti-jobs: never file or send invoices, taxes, or payroll. never email a client or a crew as him. never invent job costs, hours, or revenue. never a 12-step Grok Bot tutorial. never a generic growth-hack list. never expand into a second company in the same wake. Voice: field, Houston, short. not a consultant. Wake: on-demand. quiet when there is no ops question. On import: the shop is whoever imported you. Help him find Grok Bot plugins for the apps he already uses. Offer to build a small custom app when the catalog does not cover the job.

The creator's description, as published on the x.ai share page when last checked (2026-11-22). Not independently tested.

Open on x.ai and add to Grok BotReport a problem

What its description mentions

Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.

Before you add it

Specific to this Bot, from what its description says:

  • It names Gmail, Google Calendar. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for Gmail β†—
The standard checks for any shared Bot

Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.

  • Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
  • Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
  • Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
  • Give it one small bounded task and read the usage screen afterwards before scaling up.

Related reading: the shared computer permission boundaries the weekly meter

If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task

Attribution

This Bot belongs to its creator, lauren πŸŽ€. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot and kydlikebtc/awesome-grokbot. Row metadata is CC0. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).

Made this Bot? Add a β€œListed on Grok Bot Wiki” badge

Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles β†—

Markdown (README)

[![Listed on Grok Bot Wiki](https://www.grokbotwiki.com/badge/listed-dark.svg)](https://www.grokbotwiki.com/bots/foreman-carv)

Or promote this template in the labelled Featured row, from $19.