Grok Bot people ops prompts that stop before the HRIS
Employee onboarding checklists, review-cycle packs, and headcount notes. Distinct from recruiting (pipeline) and meetings. The Bot does not email employees, change the HRIS, or send offers.
In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Onboarding checklists
5 promptsNew-hire checklist from the role doc
1/21✨ What it does
The Bot builds a day-one onboarding checklist for [ROLE] starting [START DATE], covering paperwork, tools, and first-week meetings from your sources. You still update the HRIS and you assign each item.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a day-one onboarding checklist for [ROLE] starting [START DATE]. Cover paperwork, tools, and first-week meetings. Sources: [ROLE DOC], [ONBOARDING TEMPLATE], [HRIS EXPORT], [TOOL LIST]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. Deliverable: Checklist with owner, due day, source, and already-done (yes/no/unknown). Review point: I assign items. I update the HRIS.
Pro tip: Name the role and start date. A generic "new hire pack" misses visa, equipment, and team-specific tools.
Accounts and equipment checklist
2/21✨ What it does
The Bot lists accounts, hardware, and access for [NEW HIRE] against [TOOL LIST], and marks what is already done versus still missing. You still update the HRIS and you provision each account.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List accounts, hardware, and access for [NEW HIRE] against [TOOL LIST]. Mark done versus missing. Do not provision anything. Sources: [TOOL LIST], [SSO EXPORT], [IT TICKET QUEUE], [NEW HIRE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not create accounts or order hardware. Deliverable: Item, system, status, who provisions it, draft ticket (unpublished). Review point: I provision. I update the HRIS.
Pro tip: Point at the real tool list. "Give them access" with no list invents SaaS you do not use.
First-week intro schedule
3/21✨ What it does
The Bot drafts a first-week intro schedule for [NEW HIRE] on [TEAM], with suggested meetings and a buddy block from [CALENDAR RULES]. You still update the HRIS and you send the calendar holds.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a first-week intro schedule for [NEW HIRE] on [TEAM] using [CALENDAR RULES]. Do not create events or email anyone. Sources: [TEAM ROSTER], [CALENDAR RULES], [BUDDY IF ANY], [TRAINING CALENDAR]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not create calendar events. Deliverable: Day, meeting, purpose, suggested host, duration. Review point: I send the holds. I update the HRIS.
Pro tip: Give hours and who must meet them. An open calendar dump books the new hire into eight hours of "quick intros".
Manager day-one brief
4/21✨ What it does
The Bot writes a manager day-one brief for [NEW HIRE] using [ROLE DOC] and [TEAM NORMS], including what to cover and what to skip. You still update the HRIS and you run the first day.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a manager day-one brief for [NEW HIRE] from [ROLE DOC] and [TEAM NORMS]. What to cover, what to skip. Sources: [ROLE DOC], [TEAM NORMS], [30-60-90 IF ANY], [MANAGER NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not message the manager or the new hire. Deliverable: Agenda, must-cover, skip list, links, open questions. Review point: I run day one. I update the HRIS.
Pro tip: Skip career-goal fiction. If the manager never wrote goals, the brief says unknown.
30-60-90 plan draft
5/21✨ What it does
The Bot drafts a 30-60-90 plan for [NEW HIRE] in [ROLE] from [ROLE DOC] and [TEAM GOALS], with outcomes a human can check. You still update the HRIS and you agree the plan with the manager.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a 30-60-90 plan for [NEW HIRE] in [ROLE] from [ROLE DOC] and [TEAM GOALS]. Outcomes a human can check. Sources: [ROLE DOC], [TEAM GOALS], [LEVELING DOC IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. Deliverable: Day 30 / 60 / 90 outcomes, evidence, owner, unknown goals. Review point: I agree it with the manager. I update the HRIS.
Pro tip: Outcomes you can see, not "ramps up." If a goal has no source, mark it as a draft for the manager.
First 90 days
4 promptsBuddy brief for week one
6/21✨ What it does
The Bot writes a buddy brief for [BUDDY] supporting [NEW HIRE] in week [N], with topics and a do-not-decide-for-them line. You still update the HRIS and you ask the buddy in person.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a buddy brief for [BUDDY] supporting [NEW HIRE] in week [N]. Topics, and a do-not-decide-for-them line. Sources: [NEW HIRE ROLE], [TEAM NORMS], [BUDDY GUIDE IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not Slack the buddy or the new hire. Deliverable: Topics, hours, escalate-to-manager list, draft ask (unpublished). Review point: I ask the buddy. I update the HRIS.
Pro tip: Buddies are not shadow managers. Write what they can answer and what they must send back to the manager.
Missing-paperwork chase list
7/21✨ What it does
The Bot lists missing new-hire paperwork for [COHORT OR DATE RANGE] from [HRIS EXPORT] and drafts one chase note per person. You still update the HRIS and you send those notes.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List missing new-hire paperwork for [COHORT OR DATE RANGE] from [HRIS EXPORT]. Draft one chase note per person. Do not send. Sources: [HRIS EXPORT], [REQUIRED DOCS LIST], [START DATES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. Deliverable: Name, missing item, due, draft note, confidence. Review point: I send the notes. I update the HRIS.
Pro tip: Read the export. Do not invent a missing form because a column is blank in a way you do not understand.
Day-30 check-in pack
8/21✨ What it does
The Bot builds a day-30 check-in pack for [NEW HIRE] from [30-60-90], [1:1 NOTES], and [TOOL USAGE IF ANY], with open loops only. You still update the HRIS and you hold the check-in.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a day-30 check-in pack for [NEW HIRE] from [30-60-90], [1:1 NOTES], and [TOOL USAGE IF ANY]. Open loops only. Sources: [30-60-90], [1:1 NOTES], [TOOL USAGE IF ANY], [ONBOARDING CHECKLIST]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not message the new hire. Deliverable: Done, late, unknown, 5 questions for the manager. Review point: I hold the check-in. I update the HRIS.
Pro tip: Open loops only. A novel about "how they are settling in" is not a check-in pack.
Offboarding checklist draft
9/21✨ What it does
The Bot drafts an offboarding checklist for [EMPLOYEE] leaving [DATE], covering access, equipment, knowledge handoff, and final-pay notes. You still update the HRIS and you revoke access yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft an offboarding checklist for [EMPLOYEE] leaving [DATE]: access, equipment, knowledge handoff, final pay notes. Do not revoke access or email them. Sources: [ACCESS EXPORT], [ROLE DOC], [EXIT NOTES], [PAYROLL CALENDAR]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not revoke access. Do not file termination. Deliverable: System, owner, revoke/keep/ask, handoff item, draft notes (unpublished). Review point: I revoke access. I update the HRIS.
Pro tip: Revoke is irreversible. The Bot lists systems. You click revoke. Do not let it email the departing person.
Review cycle packs
5 promptsReview-cycle kickoff pack
10/21✨ What it does
The Bot builds a review-cycle kickoff pack for [CYCLE NAME] from [ELIGIBILITY LIST] and [TIMELINE DOC], with who is in, who is out, and missing managers. You still update the HRIS and you announce the cycle.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a kickoff pack for [CYCLE NAME] from [ELIGIBILITY LIST] and [TIMELINE DOC]. Who is in, who is out, missing managers. Sources: [ELIGIBILITY LIST], [TIMELINE DOC], [ORG SHEET], [HRIS EXPORT]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not open the cycle in the HRIS. Deliverable: In / out / ask, missing manager, dates, draft announce (unpublished). Review point: I announce. I update the HRIS.
Pro tip: Eligibility is a source, not a vibe. If someone is missing from the list, say missing, do not add them.
Self-review prompt pack
11/21✨ What it does
The Bot writes a self-review prompt pack for [CYCLE] against [COMPETENCY DOC], with one question per signal and a length cap. You still update the HRIS and you send the pack to employees.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a self-review prompt pack for [CYCLE] against [COMPETENCY DOC]. One question per signal, with a length cap. Do not email employees. Sources: [COMPETENCY DOC], [CYCLE GUIDE], [PRIOR CYCLE EXAMPLES IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. Deliverable: Questions, length cap, what not to write, draft send note. Review point: I send the pack. I update the HRIS.
Pro tip: One question per signal. Long forms get pasted from last year.
Manager review packet
12/21✨ What it does
The Bot assembles a manager review packet for [EMPLOYEE] from [1:1 NOTES], [GOALS], and [PEER INPUT], keeping quotes separate from opinion. You still update the HRIS and you write the final review.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Assemble a manager review packet for [EMPLOYEE] from [1:1 NOTES], [GOALS], and [PEER INPUT]. Keep quotes separate from opinion. Do not write a rating into the HRIS. Sources: [1:1 NOTES], [GOALS], [PEER INPUT], [COMPETENCY DOC]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not submit a rating or a review. Deliverable: Per-signal evidence, gaps, disagreements, open questions. Review point: I write the review. I update the HRIS.
Pro tip: Quotes versus opinion. The Bot is a clerk. It does not assign a rating.
Calibration grid draft
13/21✨ What it does
The Bot drafts a calibration grid for [TEAM] in [CYCLE] from [SCORE EXPORT], flagging thin evidence and split ratings. You still update the HRIS and you run calibration.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a calibration grid for [TEAM] in [CYCLE] from [SCORE EXPORT]. Flag thin evidence and split ratings. Do not lock ratings. Sources: [SCORE EXPORT], [LEVELING DOC], [TEAM ROSTER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not change ratings. Do not filter on protected traits. Deliverable: Name, draft rating, evidence thickness, split notes, questions. Review point: I run calibration. I update the HRIS.
Pro tip: This is a discussion grid, not a ranking engine. Do not ask it to force a curve.
Promo or leveling packet
14/21✨ What it does
The Bot builds a promo or leveling packet for [EMPLOYEE] against [LEVELING DOC], listing evidence, gaps, and open questions. You still update the HRIS and you decide the level.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a promo or leveling packet for [EMPLOYEE] against [LEVELING DOC]. Evidence, gaps, open questions. Do not change the level. Sources: [LEVELING DOC], [REVIEW PACKET], [ROLE DOC], [BAND DOC]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not change title, level, or pay. Deliverable: Proposed level, evidence, gaps, questions for the committee. Review point: I decide. I update the HRIS.
Pro tip: Must-haves from the leveling doc only. Do not invent a "stretch" level to be kind.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
Headcount notes
4 promptsPlan versus actual headcount
15/21✨ What it does
The Bot compares approved headcount in [PLAN] to people in [HRIS EXPORT] for [PERIOD], and lists over, under, and unknown seats. You still update the HRIS and you explain the gaps.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare approved headcount in [PLAN] to people in [HRIS EXPORT] for [PERIOD]. List over, under, and unknown seats. Sources: [PLAN], [HRIS EXPORT], [ORG SHEET], [CONTRACTOR LIST IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not open or close seats. Deliverable: Team, approved, actual, gap, unknown, source of each number. Review point: I explain the gaps. I update the HRIS.
Pro tip: Contractors and leave break naive counts. Say how each row was classified, or mark unknown.
Empty seats and dual fills
16/21✨ What it does
The Bot matches approved seats in [HEADCOUNT PLAN] to named people in [ORG SHEET], and flags empty seats, dual fills, and contractor placeholders. You still update the HRIS and you decide what to hire or freeze.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Match approved seats in [HEADCOUNT PLAN] to named people in [ORG SHEET]. Flag empty seats, dual fills, and contractor placeholders. Sources: [HEADCOUNT PLAN], [ORG SHEET], [HRIS EXPORT]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not open a req or contact candidates. Deliverable: Seat, named person or empty, dual-fill flag, contractor flag, note. Review point: I hire or freeze. I update the HRIS.
Pro tip: This is a seat map, not a recruiting pipeline. Do not source candidates here.
Backfill or transfer note
17/21✨ What it does
The Bot writes a backfill or transfer note for [SEAT] after [PERSON] using [ORG CHART] and [ROLE DOC], with work that stops versus work that moves. You still update the HRIS and you post the change.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a backfill or transfer note for [SEAT] after [PERSON] using [ORG CHART] and [ROLE DOC]. Work that stops versus work that moves. Do not post the change. Sources: [ORG CHART], [ROLE DOC], [TEAM WORKLOAD], [HEADCOUNT PLAN]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not announce the move or open a req. Deliverable: Work that moves, work that stops, draft note, open questions. Review point: I post the change. I update the HRIS.
Pro tip: Work that stops is a valid outcome. Do not assume every seat must be backfilled.
Comp-band check for a current employee
18/21✨ What it does
The Bot checks [EMPLOYEE] cash and equity against [BAND DOC] for [LEVEL], and flags if current pay or the ask sits outside. You still update the HRIS and you make the compensation change.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Check [EMPLOYEE] cash and equity against [BAND DOC] for [LEVEL]. Flag if current pay or the ask sits outside. Do not send an offer or change pay. Sources: [BAND DOC], [EMPLOYEE COMP], [LEVEL], [ASK IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - Do not invent equity numbers. Do not send an offer. Deliverable: Band, current, ask, gap, questions for finance. Review point: I change pay if I choose. I update the HRIS.
Pro tip: Do not invent a number outside the band "to keep them." Outside means flag, not a new offer.
Make the people-ops Bot durable
3 promptsPeople-ops Bot description
19/21✨ What it does
The Bot writes a people-ops Bot description named [NAME] with sources, the draft-only rule, and never-email / never-edit-HRIS / never-send-offers. You still update the HRIS after you create the Bot.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a people-ops Bot description named [NAME] with sources, the draft-only rule, and never-email / never-edit-HRIS / never-send-offers. Sources: [TOOLS], [HRIS], [REVIEW WINDOW], [TEAMS IN SCOPE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. Deliverable: Name, job, sources, pack format, never-do, privacy line. Review point: I create the Bot. I still update the HRIS.
Pro tip: Put the never-do line in the description, not only in chat. Shared computer: every Bot can see HR files you leave there.
Monday people-ops pack
20/21✨ What it does
The Bot writes a Monday people-ops pack routine at [TIME] [TZ] covering missing paperwork, cycle dates, and headcount drift, drafts only. You still update the HRIS after you read the pack.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Mondays at [TIME] [TZ], post a people-ops pack: missing paperwork, cycle dates, headcount drift. Drafts only. If a source is down, say so. Sources: [HRIS EXPORT], [CYCLE CALENDAR], [HEADCOUNT PLAN]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email employees. Do not change the HRIS. Do not send offers. - If a source is missing or stale, say so. Do not reuse last week. Deliverable: Routine card: next run, inputs, output, approval line, failure behavior. Review point: I enable after a test Monday. I update the HRIS.
Pro tip: Cap the pack. An unread novel on Monday is how people-ops Bots get muted.
What people-ops Bots never do
21/21✨ What it does
The Bot writes a never-do list for people-ops Bots from [RULES DOC], covering no employee email, no HRIS edits, no offers, and no protected filters. You still update the HRIS; the list only binds the Bot.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write the never-do list for people-ops Bots from [RULES DOC]. Cover no employee email, no HRIS edits, no offers, and no protected filters. Sources: [RULES DOC] (no employee email, no HRIS edits, no offers, no protected filters). Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - This is not legal advice. When unsure, I ask counsel. Deliverable: 12 never-do items and the human substitute. Review point: I paste it into every people-ops Bot.
Pro tip: Protected traits, surprise ratings, and live HRIS edits belong on this list before the first pack goes out.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides