When should you use it?
- You publish content but dread distributing it
- You want drafts, not autopilot posting
- You can approve or rewrite from your chat app
Not for: Auto-publishing without a human approving each post; Automating the writing you want to keep yours
What do you need, and what do you get?
You need
- Your published articles, read automatically
- A knowledge base of your past work
- An approval channel in your chat app
You get
- Channel drafts generated from each article
- Reddit replies to threads your work answers
- A record that learns your voice from your edits
How does it work, step by step?
- Draw the line firstDecide what you automate (distribution) and what stays human (the writing).
- Ingest your own workHave it ingest each new piece and file it into a personal wiki.
- Draft, do not postGenerate Reddit posts, replies and channel posts as drafts only.
- Route to approvalSend every draft to your chat to approve, rewrite or reject.
- Let it learn from editsFeed your rewrites back weekly so it sounds and thinks more like you.
The prompt
Our own prompt, inspired by Daria Cupareanu and written to work in Claude Code and Custom agent. Values in lime are placeholders.
Whenever a new piece of mine goes live, read it and file it into my knowledge base. Then draft: a post for each of [channels], and replies to recent [subreddit] threads my writing actually answers. Do not publish anything; send every draft to my [chat app] so I can approve, rewrite or reject it. Keep my voice using the examples in [style notes], and each week read my rewrites to improve how you draft.
Inspired by Daria Cupareanu: Claude Code AI Agent That Runs My Content Distribution 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?
- Begin with the work you avoid, not the work you would do anyway; that is where it earns its keep.
- It drafts in your voice but can misjudge a thread; approval is the safeguard, so keep it.
Our take
Daria Cupareanu's rule of thumb is the most useful line here: automate the work you dread, not the work you would happily do anyway. Distribution is a classic example, since most writers publish and then never share, so an agent that drafts the follow-up posts creates value that would otherwise never exist. The personal wiki is what makes the replies worth reading. Because the agent knows the archive, it can answer a thread with something the author has actually written instead of generic commentary. The Slack gate keeps the voice and judgment human, and each approval, rejection or rewrite teaches the agent what fits. Two cautions apply. Communities like Reddit dislike promotional replies and often ban accounts that post links too eagerly, so read each subreddit's rules and keep link-drops rare. And an easy approval can become automatic, so read every draft as if a stranger wrote it. Keep a log of what was posted where, which makes it easy to see which channels actually bring readers.
Where the time goes back: Distribution work you keep avoiding actually gets done, because the dreaded drafting is automated and only approval needs you.
FAQ
Does it publish on its own?
What should it not touch?
Source and credit
Inspired by Daria Cupareanu. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Claude Code AI Agent That Runs My Content Distribution While I Sleep
- Creator
- Daria Cupareanu
- Published on
- aiblewmymind.substack.com (Substack)
- Original date
- Jun 11, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- 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 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.