When should you use it?
- You are new to agents
- You do not know what to automate
- You want a quick win
Not for: Teams with a mapped process already; Tasks needing judgment calls each time
What do you need, and what do you get?
You need
- A notebook or note app
- One workday
- A bot account
You get
- Ranked friction list
- A first bot with one job
- A one-week review
How does it work, step by step?
- Log a dayWrite down every repetitive or annoying task as it happens.
- SortPut each into data entry, research or communication.
- ScoreRate frequency and how much you dread it.
- Hand off oneGive the top item to one narrowly named bot.
- Review after a weekWiden its scope only if the week went well.
The prompt
Our own prompt, inspired by James Camp π ,π (@JamesonCamp) and written to work in Grok Bot. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Here is my friction log from today: {friction_log}.
Sort each item into data entry, research or communication, and score frequency (daily, weekly, rarely) and dread (1 to 5).
Rank them and propose one narrowly named bot for the top item, with its instructions, the access it needs, and what it must ask me before doing.Inspired by James Camp π ,π (@JamesonCamp): I Spent Tens of Thousands on AI Tools. Grok Bot Is the First Agent Iβd Recommend to My Mom.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- All bots under one account use the same files and sessions, so they do not isolate access.
- Do not start with five bots at once.
- Measure hours back and tasks no longer dreaded.
Our take
James Camp's friction audit is the cleanest starting method we have seen for people who keep hearing about agents and never begin. Logging tasks as they drain you beats brainstorming a list later, because the dull jobs you avoid are the ones you forget when asked what to automate. Scoring by frequency and dread surfaces work that is both common and unpleasant, which is where an agent pays off quickly. One bot, one job, one week is the right pace: you learn whether the handoff actually helps before building a fleet. After the week, decide with evidence: did it save time, did you trust its output, what broke. His caveat about shared computers and sessions under one account matters when you connect email or files; give access deliberately and start with the lowest-stakes job on your list. Prefer tasks with clear inputs and a reviewable output, such as a draft or a sorted folder, over anything that sends messages or spends money on day one.
Where the time goes back: You start where the payoff is highest instead of automating something that barely matters.
FAQ
How many bots does he run?
When should you build custom?
Source and credit
Inspired by James Camp π ,π (@JamesonCamp). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I Spent Tens of Thousands on AI Tools. Grok Bot Is the First Agent Iβd Recommend to My Mom.
- Creator
- James Camp π ,π (@JamesonCamp)
- Published on
- X
- Original date
- Aug 24, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Grok Bot
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.