Run all of this inside the full Agent OS — join the AI Profit Boardroom →

agentos.guide › blog

Grok Bot For Recruiting: Five Copy-Paste Prompts For Adverts, Screening, Interview Slots And A Hiring Digest In Your Agent OS

By Julian Goldie · 6 November 2026 · agentos.guide

Illustrated hiring desk with a stack of CVs, a calendar with two highlighted slots and draft envelopes behind a gold approval gate beside a glowing cloud computer

Grok Bot for recruiting fits an Agent OS cleanly: your agent writes the hiring briefs and rules, and Grok Bot does the reading, drafting and diary work on its cloud computer.

Below is a quick start, five copy-paste prompts and a weekly hiring rhythm.

Each prompt maps to the official Grok Bot use cases page, the skills and routines docs and the apps and email docs.

Fancy a hand mapping it to your own hiring? Get your Backlink Gameplan with my team, or try Polar Rank free for 3 days.

Quick start: six checks before the first application

  1. Confirm access: Premium, Super and Ultra include Grok Bot on The X Subscription, and Plus doesn't, per the plan page.
  2. Connect Gmail, Google Calendar, Google Sheets and Google Drive from Connect apps.
  3. Ask the Bot to claim its mail.grokbot.com address; the name is permanent, so choose it with care.
  4. Decide on a plus alias for applications, such as +jobs.
  5. Add the Ask first rule "Ask first before sending any external email".
  6. Write one line you never break: a person makes every hiring decision.

Who plans, who works

Your Agent OS is the planner: it knows your business, your roles and your tone, so it writes the instructions.

Grok Bot is the worker: all of your Bots share one cloud computer, each with its own screen, and they carry on with the laptop closed.

Approval cards appear in Grok Bot, so nothing your Agent OS drafts reaches a candidate without your click.

On connectors, be realistic: the docs name no applicant tracking system, and the Workday entry on the security page has no description of what it covers.

If your ATS has no app, the Bot uses its browser, or an MCP server your vendor provides.

Prompt 1: have your Agent OS write the Talent scout brief

The docs say a lasting Bot starts with a description holding the job, the sources, the output and the boundaries.

Give your Agent OS this:

Write a Grok Bot description for a "Talent scout" role in my business.
Job: source candidates for the roles I name, read applications sent to the +jobs alias, check them against the must-haves, draft replies and invitations.
Sources: the hiring sheet in Google Drive, the jobs alias, our ATS through the browser, public profiles where the site's terms allow.
Output: one row per person with must-haves met, evidence, open questions and a draft message.
Boundaries: a person makes every hiring decision. Never contact, reject or advance anyone. Never change the ATS. Respect candidate privacy and each source's terms.
Keep it under 200 words, in UK English.

Paste the result into the Bot's first message and ask it to remember it.

Prompt 2: the job advert

Attach the role notes as a Word or PDF file, then paste this into Grok Bot:

Using the attached notes, draft a job advert for this role in our house style: what the job is, the must-haves, the nice-to-haves, the hours and how to apply (email the +jobs alias).
Then list the must-haves as a numbered checklist I can confirm.
Save both to Google Drive as a new document. Do not post anything.

Saving to Google Drive always creates a new file, so you won't overwrite an old advert.

Confirm the checklist before Prompt 3, because the screening routine leans on it.

🔥 Want these hiring prompts tuned to your business on a live call?

Inside the AI Profit Boardroom you get step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members building agent workflows.

→ Join the AI Profit Boardroom

Prompt 3: the screening routine

Routines can start when email reaches the Bot's own address, and a routine on an alias runs only for mail sent to that alias.

Set up a routine: when email arrives at the +jobs alias, read the application and any CV attached.
Add one row to the hiring sheet: name, must-haves met with the line of evidence, must-haves missing, questions to ask.
Draft a short acknowledgement in my voice. Leave it as a draft.
Never reject or shortlist anyone yourself. If the CV can't be read, say so in the row.

Mail written by a routine is held back as a draft for you to send, and the docs offer no way to switch that off.

Routines can't filter by subject, so the alias does the sorting.

Prompt 4: interview slots

Google Calendar lets the Bot check free time and create events, but it can't add a Zoom link.

For the people I've marked "interview" in the hiring sheet, find two 45-minute slots each in my calendar next week, between 10:00 and 16:00.
Draft an invitation email for each with both options. Do not create any calendar events until I approve.
List any clashes you found.

Approve the events one at a time, then paste the video link into the event yourself.

Prompt 5: the Friday hiring digest

Every Friday at 16:00, post a hiring digest in this conversation: new applications this week, who is waiting on a reply from me, interviews booked, drafts still unsent.
If the hiring sheet can't be opened, report that instead of using last week's data.
Do not contact any candidate.

The routines docs ask for exactly this kind of no-data rule.

A new routine waits for its next slot, so use Test to see the first digest straight away.

Where each prompt runs

PromptRuns inStops at
1. Talent scout briefYour Agent OSText you paste into Grok Bot
2. Job advertGrok Bot chatA Drive document you post yourself
3. Screening routineGrok Bot routineA sheet row and a draft
4. Interview slotsGrok Bot chatDraft invitations and an approval card
5. Friday digestGrok Bot routineA summary in the chat

Two small-business examples

A beauty salon hiring a weekend therapist.

  1. The Agent OS writes the brief from the owner's notes.
  2. Grok Bot drafts the advert; the owner posts it.
  3. The screening routine logs each reply and drafts a thank-you.
  4. The owner picks three people; the Bot drafts invitations with Saturday slots.
  5. The owner sends them and runs the trial sessions herself.

An IT support firm sourcing a field engineer.

  1. The owner runs the docs' sourcing prompt for ten candidates, excluding anyone already in the ATS.
  2. The Bot returns evidence for each match and a draft message, and contacts nobody.
  3. The owner keeps five and approves those messages.
  4. First-contact emails go to one person each with a one-click unsubscribe link.

📞 Hiring because demand is growing?

Get your Backlink Gameplan and we'll look at how new customers find you in search while you build the team.

Backlink Gameplan or try Polar Rank free for 3 days

Save the screening method as a skill

After two or three clean runs, ask Grok Bot to save the screening process as a skill called "Application screening".

Per the docs, a useful skill spells out six things: the trigger for using it, required inputs and access, the steps in sequence, a validation check, the output, and anything needing approval.

Skills are shared across all your Bots, so a second hiring Bot can reuse it.

On a team, you can publish the skill so colleagues and their Bots can use it too, once it has a description.

Give your Agent OS the corrections you made each week and let it rewrite the skill's decision rules; then paste the new version back.

Troubleshooting the hiring routines

Still stuck? Get your Backlink Gameplan from my team and we'll look at it with you, or try Polar Rank free for 3 days.

Bring the hiring panel in through Slack

On a Cursor team, share the Talent scout and add the panel as Collaborators.

Each person's chat with a shared Bot stays private, per the shared Bots page.

Choose Bring to your team's Slack, and the panel can mention it in a hiring channel.

Only the person who asked can answer its Review an action card in a thread.

The weekly hiring rhythm

Monday: ask your Agent OS to update the brief for any new role.

Each morning: read new sheet rows and send the drafts you agree with.

Friday: read the digest and decide who moves forward.

Monthly: review routines and apps, and pause anything whose source has changed.

When a role is filled, pause its screening routine rather than leaving it listening to an alias nobody advertises any more.

That keeps usage down and stops old adverts from filling the sheet.

For the sales version of this setup, see our Grok Bot for sales prompts, and for coaching, the AI Profit Boardroom has the walkthroughs.

FAQ

Which prompt comes first?

Prompt 1, so the Bot has a brief with its job, sources, output and boundaries. Then draft the advert and confirm the must-haves checklist.

Can the screening routine reply to applicants automatically?

No. Email from a routine waits as a draft until you press Send, and the docs say there's no option for unattended sending.

Why use a plus alias for applications?

A routine watching an alias only runs for mail sent to it, and routines cannot filter by subject, so the alias keeps applications separate.

Can the Bot add video links to interviews?

It can create Google Calendar events after you approve, but it can't add a Zoom link, so paste that in yourself.

Final word on Grok Bot For Recruiting

Paste the five prompts, keep every hiring call with a person, and join the AI Profit Boardroom to run Grok Bot for recruiting in your Agent OS.

About Julian

I'm Julian Goldie, an AI entrepreneur, SEO expert and the founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

My YouTube channel has 400,000+ subscribers, and I run Goldie Agency, a seven-figure SEO agency.

→ Get my best AI training inside the AI Profit Boardroom

Related guides on agentos.guide

→ Grok Bot For Business: Write The Approval Rules, Inbox Wiring And Team Setup With 5 Prompts In Your Agent OS

→ Grok Bot Email: How To Name, Alias And Automate Your Bot's Inbox In Your Agent OS, With Five Copy-Paste Prompts

→ Grok Bot Routines: How To Plan, Test And Review Every Routine In Your Agent OS, With Five Copy-Paste Prompts

→ Grok Bot AI Full Course (Step By Step)

Get the whole Agent OS

The installable system behind every guide on this site — dashboard, agents, memory and pipelines — updated as new tools land, with 3,400+ members and four coaching calls a week.

Join the AI Profit Boardroom →

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

← all guides on agentos.guide