When should you use it?
- You run a small dev consultancy
- Weekly reports and chasing replies eat your week
- You already use Telegram
Not for: Unreviewed client emails; Agencies with shared inboxes and many owners
What do you need, and what do you get?
You need
- GitHub CLI access
- Slack and Linear read access
- Mail access for follow-ups
You get
- Morning digest
- Friday client update drafts
- Follow-up drafts awaiting approval
How does it work, step by step?
- Define stale workChoose rules such as open a day with no review, failing checks or an urgent label.
- Write each skill as a fileOne for the PR digest, one for client updates, one for follow-ups.
- Schedule themMorning digest daily, client update weekly, follow-up scan regularly.
- Route to chatDeliver everything to Telegram with yes and no options.
- Send only on yesNothing reaches a client until you approve.
The prompt
Our own prompt, inspired by Farooq Shabbir and written to work in OpenClaw and Claude. Values in lime are placeholders.
Every weekday at 8 AM, check my GitHub repos for pull requests waiting a full day with no review, with failing checks, or labeled urgent, and list Slack messages from yesterday that ask me to do something. Message me the digest on Telegram. Each Friday, write a draft update per client based on what was merged and which Linear tickets closed, and share those drafts with me. Never email a client until I reply yes.
Inspired by Farooq Shabbir: I Built a 24/7 Freelance Operations Agent with OpenClaw — It Runs My Business While I Sleep. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- An always-on agent with mail access needs tight scopes.
- Auto-drafted updates can miss context; skim every one.
Our take
Specific rules make the digest trustworthy: stale means something measurable. Approve-in-chat is the key safeguard for any always-on ops bot. What we would copy first is the definition of stale work: no review after a day, failing checks or an urgent label. Clear rules like that mean the morning digest only shows things that genuinely need you, so you keep reading it. Writing each job as its own skill file also helps, because a broken client update cannot take the PR digest down with it. The weak point is scope. An always-on agent that can read mail and post updates should start with read access, and every outgoing message should wait for your yes in Telegram, as Farooq set it up. Skim each drafted client update before approving; auto-written summaries miss context you carry in your head. If you run a team with shared inboxes and several owners, this design will need more than one approver.
Where the time goes back: Status reports and follow-up chasing become approvals in an app you already check.
FAQ
Did it need code?
What changed for him?
Source and credit
Inspired by Farooq Shabbir. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I Built a 24/7 Freelance Operations Agent with OpenClaw — It Runs My Business While I Sleep
- Creator
- Farooq Shabbir
- Published on
- DEV Community
- Original date
- Apr 23, 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 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 24, 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.