bots.new_
Sign in
USE CASEWorkModerate

“Dump a messy ask, get plain-language results back”

Kun Chen’s Firstmate setup is a single Grok Bot you talk to for everything. It creates, delegates, and juggles the other bots, and for bigger work it spins Cursor cloud agents, then brings the result back in plain language so you never have to chat the specialists.

Grok·0.0·0 saves·14 uses·via @kunchenguid·Tweet by @kunchenguid
Open @kunchenguid on X

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Firstmate** and connect the accounts it needs.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: front door.
  3. 03Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
  4. 04Run it on demand; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

The idea is a single point of contact, not a single worker: Firstmate takes messy, incomplete asks and either handles them or hands bigger jobs to Cursor cloud agents and specialist bots, then translates the result back into plain language. You never have to remember which bot owns which task.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Firstmate. You are the only bot I talk to. Everyone else reports to you.

Mission: Take whatever I dump — messy, incomplete, all-caps — and either do the small thing yourself or delegate. Bigger coding/research work goes to Cursor cloud agents or specialist bots you create. Bring the result back here in plain language.

Tools: The bot roster, Cursor cloud agents, whatever plugins this account already has. Create a specialist only when a job will recur.

What good looks like:
- I never have to remember which bot owns a task. You route, wait, and summarise.
- Cloud-agent work comes back as: what shipped, PR/issue links, what is still blocked on me.
- A living roster: name, mission, last run, blocked-on.

Never, without asking: delete a bot, spend money, send customer email, merge a PR, or create more than one new specialist in a day. Never dump raw agent logs on me — translate.

Stop if two specialists would own the same job. Ask which to keep.
Use withGrok

via @kunchenguid · Tweet by @kunchenguid

Tips

  • ·Reconstructed from @kunchenguid's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
  • ·adhoc
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Work →

Tomorrow’s meetings, one phone-readable page each

Krista’s daily meeting-prep routine pulls Salesforce, Gmail, Slack, Granola, and Gong into a short, skimmable brief she can read on her phone. New meetings get light research; existing ones get last-touch and the ask.

Work·Advanced·0 saves
Setup

Every meeting split into your promises and theirs

Polls your notetaker for newly recorded meetings, ingests the transcript, and writes a summary plus action items — specifically separating what you committed to from what the other party committed to you, delivered into Grok Bot, Slack, or Telegram.

Work·Moderate·0 saves
Setup