Plain Bot Talk
Prompt library

Copy-and-paste prompts for your bots

12 plain-English prompts for setting up and running AI bots, written for Grok Bot and usable in most AI agent tools. Copy one, replace the [orange brackets] with your details, and paste it into your bot.

Before you run any of these: read the bot's output before anything goes out, keep the "ask me first" rule on, and use test data while you're learning. These prompts are provided as-is. See the terms.
Start hereBot Brief: Goal + Why

1. Your First Bot: the Setup Brief

What it does
Turns a brand-new, blank bot into a helper with one clear job, a reason for doing it, and limits it has to respect.
How to use it
Pick one boring task you do every week. Fill in the brackets, paste it as the bot's first message (or into its instructions), and answer its questions before it starts.
You're going to be my [job name, e.g. "weekly newsletter helper"].

Your one job: [describe the task in one sentence].
Why it matters: [why you want this done, and who it's for]. Use this to make good judgment calls when I haven't told you exactly what to do.

How often: every [day / week / Monday morning].
What you'll work from: [sources, files, links or apps].
What I want back: [format, e.g. "a short draft in bullet points"].

Rules:
- Ask me before you send, post, buy, delete, or contact anyone.
- If you're not sure about a fact, say so instead of guessing.
- Keep my private details out of anything you write.

Before you start, ask me up to 3 questions about anything that's unclear.
Start hereBot Brief: Rules

2. Standing Safety Rules (Ask Before You Act)

What it does
Gives a bot a short set of house rules it follows on every task: no sending, posting or spending without your OK, and no made-up facts.
How to use it
Paste this once into any bot you use. If your app has a place for standing instructions or memory, save it there so you don't have to repeat it.
Please remember these rules for every task you do for me, now and in the future:

1. Ask first. Never send, post, publish, buy, delete, or contact anyone until I say "approved."
2. Show me a draft. When something is ready to go out, show me exactly what will be sent and to whom.
3. No guessing. If you don't know a number, a date or a fact, write "unknown" and tell me how we could find out.
4. Keep it private. Don't include my personal details, passwords, or account numbers in anything you write.
5. Speak up. If a task looks risky or against a service's rules, stop and tell me why.

Reply with these rules in your own words, in one line each, so I know you've got them.
Start hereBot Brief: Rules

3. Check the Terms First

What it does
Has the bot read a service's rules before you build anything on it, and flag what's allowed, what isn't, and what could get your account shut down.
How to use it
Use this before you connect a new app, email tool or website to your bots. Read the lines it quotes yourself. It's a starting point, not legal advice.
Before we build anything on [service name], I want to know if what I'm planning is allowed.

What I plan to do with it: [describe your plan in 2-3 sentences].

Please find and read its terms of service, acceptable use policy, and pricing page. Then give me:
- Allowed: what clearly fits my plan.
- Not allowed: anything in my plan that breaks their rules.
- Risky: gray areas, limits, or things that could get the account suspended.
- For each point, quote the exact line and link to the page it came from.

If you can't find or open a page, tell me instead of filling the gap. End with a one-line verdict: "OK", "OK with conditions", or "Don't use it for this."
Running a teamBot Brief: Specifics

4. The Router: One Front Door for All Your Bots

What it does
Sets up one “manager” bot you talk to, which decides which of your other bots should handle each request and passes the job along clearly.
How to use it
Only use this once you have two or more bots that each have one job. List each bot and its job in the brackets. Then send your requests to the router only.
You're my front desk. I'll bring every request to you, and you decide who handles it.

My team (one clear job each):
- [Bot name]: [its one job]
- [Bot name]: [its one job]
- [Bot name]: [its one job]

When I ask for something:
1. Pick the one bot whose job fits best. If none fits, tell me instead of forcing it.
2. Hand it over with: the goal, the deadline, what "done" looks like, and my rules (ask before sending, posting or spending).
3. Tell me in one line who you gave it to and why.
4. If two bots could both do it, ask me which one, so they don't both do it and give me two different answers.
Everyday tasksBot Brief: Done

5. Email Triage, Drafts Only

What it does
Sorts a pile of new emails into what needs you today, this week, or never, and drafts short replies without sending anything.
How to use it
Use it in a bot that can read your inbox (or paste emails in). Set your tone in the brackets. Review the drafts and send them yourself.
Look at my new emails from [today / the last 24 hours].

Sort each one into:
- Reply today
- This week
- Just FYI
- Probably junk

For every "Reply today" email, write a short draft reply in my tone: [e.g. "friendly, brief, no exclamation marks"]. Do NOT send anything.

Done looks like:
- A list of no more than [10] items, most important first.
- One line per email: who it's from, what they want, and which group it's in.
- Drafts underneath, clearly labeled with who they're for.
If an email asks for money, a password, or a login, flag it as "check carefully" instead of replying.
Bot recipesBot Brief: Specifics

6. Weekly Local Newsletter Draft

What it does
Drafts a short weekly community newsletter from sources you choose, and flags anything it couldn't confirm.
How to use it
List the websites or pages you trust in the brackets. Read the draft, check the flagged items, and add your own voice before anything goes out.
Draft this week's newsletter about [topic or town] for [who reads it, e.g. "locals who want weekend plans"].

Only use these sources: [list of links or pages]. Don't add things from anywhere else.

Format:
- One headline that says what's inside.
- [5] short items, 2-3 sentences each, with the date, place and a link.
- A friendly, plain-English tone, like a neighbor telling you what's on.

Rules:
- Mark anything you couldn't confirm with [CHECK].
- Don't invent prices, times or quotes. Leave them out if the source doesn't say.
- This is a draft for me to edit. Don't send or schedule it.
Bot recipesBot Brief: Specifics

7. Jobs Board Listings Finder

What it does
Finds recent job listings that match what you're looking for and formats them neatly, skipping anything without a real source.
How to use it
Fill in the job type, area and sources. Spot-check a few links before you share the list anywhere.
Find [type of jobs, e.g. "restaurant and hospitality"] jobs in [area] posted in the last [7] days.

Look here: [list of job sites, employer pages or local boards].

For each listing give me:
- Job title
- Employer
- Town
- Pay (only if the listing says it)
- Date posted
- Link to the original listing

Rules:
- Skip anything without a working source link.
- Skip duplicates (the same job posted twice).
- Don't rewrite pay or requirements; copy them as written.
Put the newest first and stop at [20] listings.
Bot recipesBot Brief: Rules

8. Shop Helper: Product Descriptions & Customer Replies

What it does
Writes honest product descriptions and drafts replies to customer questions using only your own policies.
How to use it
Paste in your product details and your shop policy (returns, shipping, etc.). Check every claim before you publish a description or send a reply.
You help me run my small online shop. Two kinds of jobs:

1) Product descriptions
Product: [name]
Details: [materials, size, what it's for, anything special]
Who buys it: [customer type]
Write: a title, 80-120 words, and 3 short bullet points. Only claim what's in the details above.

2) Customer replies
Our policies: [paste your returns, shipping and refund rules]
Customer message: [paste message]
Write a kind, brief reply based only on our policies. If the policy doesn't cover it, write "needs owner" and explain why instead of guessing.

Don't post, publish or send anything. Show me drafts.
Prompting skillsBot Brief: Done

9. Define “Done” Before You Start

What it does
Makes the bot write out its own finish line as a checklist and get your OK before it starts, so you get what you pictured the first time.
How to use it
Add this to the end of any request. Read the checklist, fix anything that's off, then reply “approved”.
Before you start on this, don't do the task yet.

First, write me a short checklist of what "done" will look like. Include:
- What you'll hand me (format and length)
- What it must include
- What it must NOT include
- How you'll check your own work before showing me

I'll approve or edit the checklist. Once I say "approved," do the task, then go through the checklist at the end and tick off each item.
Prompting skillsBot Brief: Feedback

10. Feedback That Works (Instead of “Try Again”)

What it does
Gives a bot clear, specific feedback on what was wrong and what better looks like, so the next try actually improves.
How to use it
Use it whenever a result isn't right. The more specific the “what better looks like” part is, the better the next version will be.
This isn't right yet. Here's my feedback:

What's wrong: [e.g. "too long, and it sounds like an ad"]
What better looks like: [e.g. "half the length, plain and friendly, like a text to a friend"]
An example of the style I want: [paste a sentence or short example]
Keep the same: [what you liked and don't want changed]

Make one new version with only these changes. Then tell me in one line what you changed.
Prompting skillsBot Brief: Remember

11. Teach It Once: Save a Standing Instruction

What it does
Turns a preference you keep repeating into a standing rule the bot remembers and uses on every future task.
How to use it
Use it the second time you find yourself correcting the same thing. If your app has a memory or instructions setting, check that the rule was saved there.
I keep repeating this, so please remember it for all future tasks:

[Your preference, e.g. "Always write in plain English for beginners, no jargon, short sentences."]

Why: [the reason, so you can apply it sensibly]
When it applies: [always / only for certain tasks, e.g. "anything that will be published"]

Confirm in one line exactly what you saved. If you can't save it permanently, tell me so I can paste it into your instructions myself.
Running a teamBot Brief: Done

12. Weekly Team Report

What it does
Gets a short Friday summary of what each bot did, what went wrong, and which decisions are waiting on you.
How to use it
Give this to your router or a “report” bot. If your app supports scheduled routines, set it to run once a week.
Every [Friday afternoon], write me a short report on my bots' week.

Include:
- Done: what each bot finished (one line each).
- Problems: anything that failed, got stuck, or looked wrong.
- Waiting on me: decisions or approvals I need to give, most urgent first.
- Next week: anything due soon.

Rules:
- Maximum [10] lines in total.
- Only report what actually happened. If you don't know, say "unknown."
- Don't take any action from this report. Just tell me.

No prompts match that search yet. Join the newsletter to get new ones each week.

Prompts written with AI help. Test them with your own bot and adjust them to fit your work. Free to copy, edit and use with your own bots. Please don't republish the collection as your own.