When should you use it?
- You read a lot to write and forget what you have already covered
- You keep a searchable archive of your own work
- You want agents on a schedule, not on demand
Not for: Anyone not ready to secure a self-hosted agent; Inboxes holding sensitive client mail
What do you need, and what do you get?
You need
- Newsletter feed or inbox
- Index of your own posts and projects
- Always-on server
You get
- Twice-daily notes linking new reading to your past work
- Ideas for follow-up posts
How does it work, step by step?
- Index your own workBuild a searchable memory of everything you have written or shipped.
- Point the scan at subscriptionsHave a scheduled job collect new posts from your reading list.
- Cross-referenceFor each post, search your archive and note genuine connections.
- Deliver to chatSend the notes to a messaging channel you check.
- Lock it downRun on an isolated server and give it only the accounts it needs.
The prompt
Our own prompt, inspired by Jenny Ouyang and written to work in OpenClaw and Custom agent. Values in lime are placeholders.
Twice a day, collect posts published since the last run from my newsletter subscriptions. Read each one and search my archive index for my own posts or projects on the same subject. For each new post, write two lines: what it says and which of my items it connects to, with links. Skip posts with no clear connection. Send the result to my Telegram chat.
Inspired by Jenny Ouyang: OpenClaw Review: What It Is, What I Tried, and What Matters for You. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Self-hosted agents have had serious security issues; isolate them and limit access.
- Weak connections clutter the notes; ask for only clear overlaps.
Our take
The cross-reference step is what makes this more than another digest; it ties new material to what you have already made. For a writer, the useful output is not a summary of today's newsletters but a note saying this new piece connects to something you wrote months ago. That only works if your own archive is indexed well, so build that memory first and test a few searches before scheduling anything. Ask for clear overlaps only; loose connections fill the chat with noise and you will stop reading after a week. Twice a day suits Jenny's reading load; a lighter reader could run it once. The bigger caution is security. Self-hosted agents have had serious vulnerabilities, so keep this on an isolated server with access to the reading list and the archive and nothing else, and keep sensitive client mail away from it entirely. Treat each note as a prompt for your own thinking, not a draft to publish.
Where the time goes back: It turns passive reading into a prompt about your own body of work, without you having to remember it.
FAQ
How many jobs does she run?
Who else used it?
Source and credit
Inspired by Jenny Ouyang. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- OpenClaw Review: What It Is, What I Tried, and What Matters for You
- Creator
- Jenny Ouyang
- Published on
- buildtolaunch.substack.com (Substack)
- Original date
- Mar 7, 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.