When should you use it?
- You have opinions but little time to write them up
- You already post regularly, so there is voice data
- You are comfortable with scripts in a repo
Not for: Scraping sites in ways their terms forbid; Publishing generated text unedited
What do you need, and what do you get?
You need
- A raw notes file
- Your past posts for style
- Sources you follow for industry context
You get
- A long-form newsletter draft
- Two or three LinkedIn post drafts
- A short thread for X
How does it work, step by step?
- Dump your thinkingWrite a few hundred words, messy is fine, in a text file.
- Refresh your voice dataRe-read your latest posts so style tracks how you write now.
- Add context carefullyPull ideas from sources you follow, within their terms, and credit them.
- Generate the setProduce the newsletter, posts and thread into one dated folder.
- Edit and publish yourselfCut, fact-check and post by hand.
The prompt
Our own prompt, inspired by Harshit Jain and written to work in Custom agent. Values in lime are placeholders.
Read notes/today.txt (my raw thinking) and my last 30 posts in posts/ for voice. Write: one newsletter draft of about 1,500 words, two LinkedIn posts and a 6-part X thread, all in my voice. Use only ideas from my notes and the saved links in sources/; credit any borrowed idea by name. Save everything to drafts/[date]/. Flag any statement that needs a fact check.
Inspired by Harshit Jain: I built a Cursor playbook that writes my newsletter and all content exactly like me. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Automated scraping of social sites can breach terms; prefer feeds or manual saves.
- Borrowing hooks from other writers too closely becomes copying; keep ideas, not phrasing.
Our take
Harshit Jain's useful idea is the division of labor: you supply the thinking in rough form, and the system handles expansion, formatting and versions for each channel. Training the voice on your own recent posts keeps output sounding like you rather than generic marketing copy. Committing everything to Git is a neat touch, since you can see exactly how drafts changed and roll back. Two adjustments would make it sturdier. Rather than automatically scraping other writers' posts, which raises platform terms issues and risks echoing their wording, keep a file of links you chose yourself, and have the system credit any idea it borrows. And be wary of length for its own sake: a 2,000-word expansion of a few raw thoughts can easily become padding, so set a rule that every section must contain a concrete point, example or number from your notes. Read each piece fully before publishing, since your name is on it, and check facts or statistics the system adds that were not in your original file.
Where the time goes back: One brain dump becomes a week of drafts across channels.
FAQ
How much input does it need?
Where does output go?
Source and credit
Inspired by Harshit Jain. 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 Cursor playbook that writes my newsletter and all content exactly like me
- Creator
- Harshit Jain
- Published on
- newsletter.qback.ai
- Original date
- Aug 25, 2025
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- 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.