When should you use it?
- You use history to decide what to post next
- Your account contains test or automated posts
- You publish across several platforms
Not for: Auto-posting from inferred ideas; Accounts where history is incomplete
What do you need, and what do you get?
You need
- A download of everything you have published
- Filters for test and duplicate items
You get
- Idea list with the evidence behind each
- Questions where the agent is unsure
How does it work, step by step?
- Filter the historyRemove very brief items, repeats posted close together, and QA or review artifacts.
- Separate seeing from concludingHave the agent state what it found before saying what it means.
- Ask before assertingRequire a question whenever an idea depends on an inference such as an unfinished promise.
- Fill missing contextTell it what happened offline or on other platforms it cannot see.
- Review before draftingApprove the idea, then write.
The prompt
Our own prompt, inspired by Eugeniya Ivanova and written to work in Claude, ChatGPT and Custom agent. Values in lime are placeholders.
Read my post history export. Skip posts below 20 words, repeats published close together, and any QA or review artifacts. Suggest five post ideas. For each, show the past posts it is based on and separate what you observed from what you infer. If an idea depends on an inference, such as a follow-up I seem to owe, ask me whether it is true before including it. Ask what I have published elsewhere on the same subject.
Inspired by Eugeniya Ivanova: I gave an agent my posting history. It found a promise I never made.. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- The agent only sees what passed through the tool; posts elsewhere are invisible to it.
- Confident phrasing hides weak inferences; ask for evidence per idea.
Our take
One of the more useful failure write-ups on content agents. Nothing was hallucinated; the agent misread real records whose purpose it could not see, and it asserted a commitment that was not one. Eugeniya's fix is the part to copy. Filter the history first, removing very short items, near-duplicate posts and QA or test artifacts that were never meant for an audience. Then ask the agent to say what it found before saying what it means, and require a question whenever an idea depends on an inference, such as a promise you supposedly left unfinished. The agent only sees what passed through its tool, so tell it what happened offline or on other platforms. Ask for the evidence behind each idea; confident phrasing often hides a weak link. Approve an idea before any drafting begins, and never let inferred ideas post automatically. If your account history is incomplete, expect more questions and fewer reliable suggestions.
Where the time goes back: You get ideas fast without the risk of publishing something based on a misunderstanding of your own past.
FAQ
What went wrong?
What fixed it?
Source and credit
Inspired by Eugeniya Ivanova. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I gave an agent my posting history. It found a promise I never made.
- Creator
- Eugeniya Ivanova
- Published on
- DEV Community
- Original date
- Sep 8, 2026
- 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 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.