Grok Bot agency prompts that stop before the client
Retainer hours, utilization, weekly updates, and SOW drafts. The Bot reads time and tickets on the shared computer. You send to clients. You change invoices.
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.
Retainers and hours
5 promptsHours versus the contracted cap
1/21✨ What it does
The Bot compares logged hours on [RETAINER OR CLIENT] against the contracted cap for [PERIOD] and flags overrun, leftover, and missing entries. You send the hours conversation to the client if you want one.
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 logged hours on [RETAINER OR CLIENT] to the contracted cap for [PERIOD]. Flag overrun, leftover, and missing entries. Do not email the client or edit invoices. Sources: [TIME TOOL], [RETAINER OR SOW], [INVOICE VIEW READ ONLY]. 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 send messages to clients. Do not create, edit, or send invoices. - If a cap or period is missing, write unknown. Do not invent hours. Deliverable: Client, cap, logged, leftover or overrun, missing people, evidence links. Review point: I send any hours note. I change invoices.
Pro tip: Name the cap and the period. "How is the retainer" with no number makes every client look fine or on fire.
Scope creep versus the signed SOW
2/21✨ What it does
The Bot lines up work logged on [CLIENT] against the signed [SOW OR RETAINER DOC] and lists tasks that look out of scope with evidence. You send the scope note to the client; the Bot does not.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Map work on [CLIENT] for [PERIOD] to [SOW OR RETAINER DOC]. List likely out-of-scope items with evidence. Sources: [TIME TOOL], [TICKETS], [SIGNED SOW], [SLACK IF NAMED]. 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 send messages to clients. Do not create, edit, or send invoices. - Quote the SOW line. Do not invent a clause. Deliverable: Task, SOW line or "not in SOW", hours, evidence, draft internal flag. Review point: I decide what becomes a change order. I send.
Pro tip: Point at the signed file, not "the Slack vibe". Paraphrased scope is how you give away a sprint.
Retainer renewal radar
3/21✨ What it does
The Bot lists retainers in [PORTFOLIO] that renew in [N] days, with hours used, open risks, and a draft internal plan. You send the renewal conversation; the Bot does not email the client.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Retainers in [PORTFOLIO] renewing in [N] days: hours used, risks, missing stakeholders, draft internal plan. Do not contact the client. Sources: [RETAINER SHEET], [TIME TOOL], [TICKETS], [CONTRACT 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 send messages to clients. Do not create, edit, or send invoices. - Do not create a renewal invoice or edit the contract. Deliverable: Client, end date, hours vs cap, risk, missing people, draft internal plan. Review point: I run the renewal. I send.
Pro tip: Ask for the economic buyer by name. "They seem happy" is not a renewal plan.
Unused or rolling hours
4/21✨ What it does
The Bot finds unused or rolling hours on [RETAINER LIST] for [PERIOD] and drafts a use-or-lose note plus a keep-or-cut recommendation. You send the note if you choose to; invoices stay yours.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find unused or rolling hours on [RETAINER LIST] for [PERIOD]. Draft a use-or-lose note. Do not send. Do not edit invoices. Sources: [TIME TOOL], [RETAINER TERMS], [INVOICE VIEW READ ONLY]. 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 send messages to clients. Do not create, edit, or send invoices. - Do not invent rollover rules. Unknown if the contract is silent. Deliverable: Client, unused hours, roll yes/no/unknown, draft note, keep or cut. Review point: I send the note. I change invoices.
Pro tip: Say whether unused hours roll. If you do not know, the cell is unknown, not "probably roll".
Retainer health one-pager
5/21✨ What it does
The Bot builds a one-page health pack for [CLIENT] from time, tickets, and the SOW: hours, risks, next deliverable, suggested ask. You send the pack; the Bot does not change invoices.
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 one-page health pack for [CLIENT] for [PERIOD]. Hours, risks, next deliverable, suggested ask. Do not send. Sources: [TIME TOOL], [TICKETS], [SOW], [LAST UPDATE]. 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 send messages to clients. Do not create, edit, or send invoices. - Separate facts in the tools from guesses. Deliverable: One-pager path: hours vs cap, risks, next deliverable, suggested ask, links. Review point: I send if the client should see it.
Pro tip: Cap it at one page. A novel about one retainer is how Monday review dies.
Utilization and staffing
4 promptsWeekly utilization table
6/21✨ What it does
The Bot builds a utilization table for [TEAM OR PEOPLE] over [PERIOD] from [TIME TOOL], with billable, non-billable, and target. You send the table internally; the Bot does not edit invoices or time.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Utilization for [TEAM OR PEOPLE] over [PERIOD]: billable, non-billable, target. Do not edit time or invoices. Sources: [TIME TOOL], [TARGET UTILIZATION], [ROLE MAP]. 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 send messages to clients. Do not create, edit, or send invoices. - Do not edit time entries. If a person has no logs, say missing, do not invent hours. Deliverable: Person, billable, non-billable, target, gap, evidence. Review point: I send the table to the team if I want to.
Pro tip: Define billable in the brief. Internal "strategy" hours will otherwise look like a crisis.
Over-allocated versus bench
7/21✨ What it does
The Bot flags who is over [UTILIZATION CAP] and who is on the bench against [STAFFING SHEET] and [PIPELINE OF SOWS]. You send staffing asks; the Bot does not message clients or change invoices.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Who is over [UTILIZATION CAP] and who is on the bench vs [STAFFING SHEET] and [PIPELINE OF SOWS]. Do not message anyone. Sources: [TIME TOOL], [STAFFING SHEET], [SOW PIPELINE]. 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 send messages to clients. Do not create, edit, or send invoices. - Do not assign work in the staffing tool. Deliverable: Person, load, bench or overrun, suggested move, confidence. Review point: I send staffing asks. I change assignments.
Pro tip: Name the cap. Without it every busy week looks like burnout and every gap looks like a firing.
Staffing sketch for a new SOW
8/21✨ What it does
The Bot sketches a staffing plan for incoming [SOW OR CLIENT] using [TEAM CAPACITY] and [SKILL MAP], with gaps and a draft role list. You send the plan to the team; the Bot does not assign work in the tool.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Sketch staffing for [SOW OR CLIENT] from [TEAM CAPACITY] and [SKILL MAP]. List gaps. Do not assign people. Sources: [SOW DRAFT], [CAPACITY], [SKILL MAP], [TIME TOOL]. 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 send messages to clients. Do not create, edit, or send invoices. - Do not email the client a team list. Do not create assignments. Deliverable: Role, person or gap, hours, risk if we start without the gap filled. Review point: I send the plan. I assign.
Pro tip: Must-have skills in the brief or it staffs whoever is free, not whoever can do the work.
Missing time entries
9/21✨ What it does
The Bot finds people on [TEAM] with missing or under-logged time for [WEEK] against [EXPECTED HOURS] and drafts a nudge. You send the nudge; the Bot does not edit time or invoices.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: People on [TEAM] with missing or under-logged time for [WEEK] vs [EXPECTED HOURS]. Draft a nudge. Do not send. Do not edit time. Sources: [TIME TOOL], [EXPECTED HOURS], [PTO CALENDAR 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 send messages to clients. Do not create, edit, or send invoices. - Do not create or edit time entries. Skip people on approved PTO. Deliverable: Person, logged, expected, gap, draft nudge, PTO yes/no. Review point: I send the nudge.
Pro tip: Expected hours per person, or the Bot nags the contractor who works three days.
Weekly client updates
4 promptsWeekly status from time and tickets
10/21✨ What it does
The Bot drafts a weekly status for [CLIENT] from [TIME TOOL] and [TICKETS OR SLACK], with hours, shipped work, and next week. You send the update; the Bot does not email the client.
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 weekly status for [CLIENT] for [WEEK] from time and tickets. Hours, shipped, next week, risks. Do not send. Sources: [TIME TOOL], [TICKETS OR SLACK], [SOW], style examples attached. 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 send messages to clients. Do not create, edit, or send invoices. - No fake shipped work. If nothing shipped, say so. Deliverable: Subject, body, hours vs cap, risks, links, what you assumed. Review point: I send from my mailbox.
Pro tip: Attach two updates you actually sent. "Write like us" without examples writes like a status robot.
Risk and blocker list
11/21✨ What it does
The Bot lists risks and blockers on [CLIENT] from [TICKETS], [SLACK], and [SOW], each with evidence and a suggested owner. You send the risk note if you want the client to see it.
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 risks and blockers on [CLIENT] this week. Evidence and a suggested owner each. Do not email the client. Sources: [TICKETS], [SLACK CHANNEL], [SOW], [LAST UPDATE]. 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 send messages to clients. Do not create, edit, or send invoices. - Do not invent a blocker to make the list look complete. Deliverable: Risk, evidence link, owner, client-visible yes/no, draft line. Review point: I send the ones that should leave the building.
Pro tip: Ask for the quote or ticket. Risks without a source become theater.
Client meeting recap draft
12/21✨ What it does
The Bot drafts a recap of [CLIENT MEETING] for [ATTENDEES] from [NOTES OR TRANSCRIPT], including decisions, asks, and dates. You send the recap; the Bot does not mail the client.
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 recap of [CLIENT MEETING] on [DATE] for [ATTENDEES]. Decisions, asks, dates. Do not send. Sources: [NOTES OR TRANSCRIPT], [DECK], [SOW], two recaps I have sent. 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 send messages to clients. Do not create, edit, or send invoices. - Do not add a calendar hold. Do not invent a date I did not say. Deliverable: Subject, body, decisions quoted, open asks, dates, TBD. Review point: I send.
Pro tip: Quote decisions. Paraphrased "we aligned" is how two sides leave with different jobs.
Monday pack across retainers
13/21✨ What it does
The Bot builds a Monday pack for [CLIENT LIST]: hours vs cap, risks, and a draft update per client that still needs you. You send each update; the Bot does not email anyone.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Monday pack for [CLIENT LIST]: hours vs cap, top risk, draft update each. Do not send. If [TIME TOOL] is down, report failure. Sources: [TIME TOOL], [TICKETS], [RETAINER SHEET]. 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 send messages to clients. Do not create, edit, or send invoices. - Do not reuse last week if a source is down. Deliverable: Per client: hours, risk, draft update, confidence. Fail closed if time is down. Review point: I send the updates I want out.
Pro tip: Cap the list. Twelve clients on Monday is a novel you will not read.
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.
SOW and change orders
4 promptsSOW draft from discovery notes
14/21✨ What it does
The Bot drafts a SOW for [CLIENT] from [DISCOVERY NOTES] and [RATE CARD], with scope, out of scope, and assumptions marked TBD if missing. You send the SOW; the Bot does not.
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 SOW for [CLIENT] from [DISCOVERY NOTES] and [RATE CARD]. Scope, out of scope, assumptions. TBD if missing. Do not send. Sources: [DISCOVERY NOTES], [RATE CARD], [PRIOR SOW TEMPLATE]. 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 send messages to clients. Do not create, edit, or send invoices. - Do not invent rates, dates, or legal terms. Not legal advice. Deliverable: SOW draft path, TBD list, questions I still owe. Review point: I edit and I send.
Pro tip: Lock the rate card. Bots will "be helpful" and invent a friendly number.
Change order when work drifted
15/21✨ What it does
The Bot drafts a change order for [CLIENT] when work on [PROJECT] drifted from [SOW], with added scope, hours, and a draft note. You send the change order; invoices stay untouched.
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 change order for [CLIENT] on [PROJECT] vs [SOW]. Added scope, hours, draft note. Do not send. Do not edit invoices. Sources: [SOW], [TIME TOOL], [TICKETS], [THREAD I POINT AT]. 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 send messages to clients. Do not create, edit, or send invoices. - Do not create an invoice for the extra work. Do not invent hours. Deliverable: Added scope, hours, fee or TBD, draft client note, evidence. Review point: I send the change order. I bill.
Pro tip: Cite the SOW line and the hours. A vibe-based change order is how you eat the work.
Estimate versus actual mid-project
16/21✨ What it does
The Bot compares estimate vs actual on [PROJECT] from [TIME TOOL] and [SOW PHASES] and drafts a mid-engagement note. You send the note; the Bot does not change invoices.
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 estimate vs actual on [PROJECT] by [SOW PHASES]. Draft a mid-engagement note. Do not send. Do not change invoices. Sources: [SOW], [TIME TOOL], [PHASE SHEET]. 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 send messages to clients. Do not create, edit, or send invoices. - If a phase has no estimate, write unknown. Do not backfill a guess. Deliverable: Phase, estimate, actual, gap, draft note, recommendation. Review point: I send the note. I change invoices.
Pro tip: Phase the compare. A single blob of hours hides the phase that already blew up.
Kickoff deliverable checklist
17/21✨ What it does
The Bot builds a kickoff checklist for [CLIENT] from [SOW]: deliverables, owners, missing inputs, and a draft kickoff email. You send the email; the Bot does not.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Kickoff checklist for [CLIENT] from [SOW]: deliverables, owners, missing inputs, draft kickoff email. Do not send. Sources: [SOW], [TEAM LIST], [CLIENT CONTACTS I PASTE]. 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 send messages to clients. Do not create, edit, or send invoices. - Do not email the client. Do not create tasks in the PM tool unless I ask after review. Deliverable: Checklist, missing inputs, draft kickoff email, TBD owners. Review point: I send the kickoff. I create tasks.
Pro tip: Owners and missing inputs, not a poster of hope. Unowned deliverables slip on week one.
Make the agency Bot durable
4 promptsAgency Bot description
18/21✨ What it does
The Bot writes an agency Bot description named [NAME] covering [TIME TOOL], [CLIENT LIST], weekly pack format, and a never-send, never-invoice line. You send every client note yourself after you paste the description.
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 an agency Bot description named [NAME] for retainers, utilization, and drafts. Never send to clients. Never change invoices. Sources: [TIME TOOL], [CLIENT LIST], [REVIEW WINDOW, E.G. 9AM MONDAY]. 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 send messages to clients. Do not create, edit, or send invoices. - Never send, never change invoices, never edit time, never publish to a client portal. Deliverable: Name, job, sources, weekly pack format, never-do, tuning instructions. Review point: I paste it into Create your own.
Pro tip: Put the client list and the never-send line in the description, not only in chat.
Monday retainer pack routine
19/21✨ What it does
The Bot prepares a Monday routine at [08:00] [TZ] that builds retainer packs for [CLIENT LIST] and stops at drafts if [TIME TOOL] is down. You send each update after you enable the routine; the Bot never emails clients.
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 [08:00] [TZ], build retainer packs for [CLIENT LIST]: hours, risks, draft updates. Do not send. Fail closed if [TIME TOOL] is down. Sources: [TIME TOOL], [TICKETS], [RETAINER SHEET]. 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 send messages to clients. Do not create, edit, or send invoices. - Do not reuse last week. Report failure if a source is missing. Deliverable: Routine card: next run, input, output, approval line, failure behavior. Review point: Test run first. I enable it. I send.
Pro tip: Fail closed if time is down. A recycled pack from last Monday is worse than a failure note.
What agency Bots never do
20/21✨ What it does
The Bot writes a never-do list for agency Bots on [TOOLS], covering client send, invoice edits, time changes, and live portal updates. You send the list to the team and paste it into each 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 agency Bots on [TOOLS]. Client send, invoices, time, live portals, legal accept. Sources: My rules, [TOOLS]. 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 send messages to clients. Do not create, edit, or send invoices. - Do not email the list to clients. This stays internal. Deliverable: 12 never-do items with one line why each. Review point: I send it to the team. I paste it.
Pro tip: Paste this on day one, before the first weekly update looks good enough to auto-send.
Per-client expert Bot brief
21/21✨ What it does
The Bot writes a description for an expert that only works on [CLIENT], including weekly output and a refuse-list for other retainers. You send every client message yourself after you create that 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 description for an expert that only works on [CLIENT]. Weekly output, refuse-list for other retainers. Never send. Never change invoices. Sources: [CLIENT SOW], [TIME TOOL], [TICKETS], [VOICE EXAMPLES]. 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 send messages to clients. Do not create, edit, or send invoices. - Remind me every Bot shares one computer. Do not treat this expert as a security boundary. Deliverable: Name, job, weekly output, refuse-list, never-do. Review point: I create the Bot. I send.
Pro tip: One client per expert. A Bot that "knows the whole book" will mix two retainers in one update.
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