When should you use it?
- One bot doing everything gets confused
- You want work and personal kept apart
- You can host several instances
Not for: Single simple tasks; Teams without approval to add a bot
What do you need, and what do you get?
You need
- Separate chat channels
- A job description for each bot
- Access limited per bot
You get
- Repo upkeep from chat
- Captured notes plus a morning news roundup
- Meeting recaps and replies for the team
How does it work, step by step?
- Split the jobsWrite a short role for each bot.
- Separate accessGive each bot only the accounts its role needs.
- Pick channelsPut each bot in the chat where its work happens.
- Set outputsDecide what each sends and when, such as weekly summaries.
- Manage themUse a simple dashboard or script to track all instances.
The prompt
Our own prompt, inspired by devashish86 on Hacker News and written to work in OpenClaw. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
You are the {role} bot. Your only jobs: {jobs}. You may use only {accounts}. Post in {channel}. Send {output} on {schedule}. If asked to do something outside your role, say which bot handles it instead.
Inspired by devashish86 on Hacker News: Comment in Ask HN: Who is using OpenClaw?. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Team bots see company data; get approval.
- Several bots multiply cost; watch usage.
- Keep personal notes away from the work bot.
Our take
devashish86's setup is a good argument for giving agents narrow jobs instead of one assistant with every key. The repository bot lives in Discord, takes thrown-together ideas and turns them into issues, priorities and doc updates, which is maintenance work that otherwise piles up. The personal bot handles notes captured on walks or drives and a daily news digest filtered by the owner's own relevance rules and trusted sources. The team bot sits in Slack, writes weekly and monthly meeting recaps and answers questions from other teams. Because each has a short brief and its own channel, it is easy to tell which one misbehaved and to fix it without disturbing the others. Separation also protects privacy: the bot your colleagues can talk to has no reason to see your personal notes, so give it no access to them. Before adding any bot to a workplace chat, get approval from whoever runs it and tell the team what it reads and stores. Track combined running costs monthly, since several always-on agents add up quietly.
Where the time goes back: Each bot stays focused, and work data stays apart from personal notes.
FAQ
Which bot was most useful?
How did they manage several bots?
Source and credit
Inspired by devashish86 on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Comment in Ask HN: Who is using OpenClaw?
- Creator
- devashish86 on Hacker News
- Published on
- Hacker News
- Original date
- Apr 16, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- OpenClaw
- 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.