When should you use it?
- You get journalist or writer requests from a sourcing service, newsletter or social posts
- You have real experience or data in a few topics and want to answer faster
- You worry AI-written replies will invent stories or credentials
Not for: Requests outside your experience; the agent should tell you to pass; Outlets that forbid AI-assisted replies, unless you write the answer yourself; Inventing customer stories, quotes or statistics to sound more useful
What do you need, and what do you get?
You need
- The full request text, including the outlet's rules and deadline
- A short file of confirmed facts: your role, real examples you may share, and data you can cite
- Your time zone, so the deadline check is right
You get
- A fit verdict: answer, or pass with the reason
- A short reply that leads with the answer and gives one specific example from your facts
- Flags on any sentence the facts do not support, and on rules such as AI-use limits
- The deadline converted to your time zone, with a warning if it is close
How does it work, step by step?
- Keep a facts fileWrite down your credentials, approved stories and numbers you can share, with where each comes from. The agent may use only this.
- Paste the requestGive the agent the full request, including rules on sources, format, AI use and the deadline.
- Check fit firstLet it tell you plainly if you are not a good source. Passing quickly keeps your reputation with writers.
- Draft answer-firstIt writes a short reply that answers the question up front, with one concrete example from your file, and flags any line it cannot support.
- Review and sendRead it, fix the voice, confirm the rules allow AI help, and send it yourself before the deadline.
The prompt
The original prompt by @BuildingWaves, word for word, with a link to where it was published. Below it is our adapted version with fill-in blanks, if you want it. Works in Grok Bot, ChatGPT agent and Claude. Values in lime are placeholders.
Original prompt by @BuildingWaves
Read this journalist request and its rules. Compare it with my confirmed experience below. Tell me if I'm not a suitable source. Draft a concise answer using only those facts, with the answer first and one specific example. Flag unsupported statements and check the deadline. Don't invent credentials, customer stories or quotes. Prepare a draft for my review.
Exactly as published by @BuildingWaves in X Article: SEO/AEO need backlinks, babe. Get them with AI.
Our adapted version (optional)
Fill in the blanks (optional; the copied prompt uses your values)
Help me answer a journalist request using only my confirmed facts. Do not send anything. Request (with rules and deadline): {request_text}. My facts file: {facts_file}. My time zone: {time_zone}. 1) Say first whether I am a suitable source, and why. If not, stop there. 2) List the outlet's rules that affect my reply, especially any limits on AI-assisted answers, and the deadline in my time zone. 3) Draft a reply under {max_words} words that answers the question in the first sentence and gives one specific example from my facts file. 4) Mark any sentence the facts file does not support. Never add credentials, customer stories, quotes or numbers that are not in it. 5) End with what I still need to confirm before sending.
What can go wrong?
- Writers increasingly check claims. One invented detail can get you dropped as a source for good.
- Some outlets ban AI-written answers. Read the rules, and write it yourself where they do.
- Long, generic replies are skipped. Lead with the answer and keep it short.
- A link is never guaranteed; treat a mention as a bonus and answer because you can help.
Our take
This is the method in Ghaffari's article where AI is most likely to cause harm, because the easy failure is a confident, invented anecdote sent to a reporter. His prompt is built to prevent that, so we quoted it word for word: it compares the request with confirmed experience, tells you when you are not a fit, and forbids invented credentials, stories and quotes. We added a standing facts file so you are not retyping your background each time, a deadline check in your own time zone, and an explicit look at the outlet's rules on AI help. Several outlets now ask that answers be written by the expert, and the right response there is to use the draft as notes and write it yourself. Keep replies short and lead with the answer; writers skim. In our dry run with two fictional requests and a five-line facts file for an invoicing-software founder, the agent said the founder was not a fit for a request seeking accountants. For a request about how freelancers chase late invoices, it drafted a four-sentence reply leading with the answer, used the one approved customer example, and flagged a line claiming most freelancers wait 30 days as unsupported. It also noted the deadline was 11 hours away and left sending to the founder.
Where the time goes back: Requests often have tight deadlines. A fast fit check and a draft built from your own facts file let you reply in minutes instead of skipping good chances.
FAQ
Where do these requests come from?
What if I do not have data on the topic?
Will this get me backlinks?
Source and credit
The original prompt on this page is by @BuildingWaves, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- X Article: SEO/AEO need backlinks, babe. Get them with AI
- Creator
- Kourosh Ghaffari (@BuildingWaves)
- Published on
- X
- Original date
- Oct 26, 2026
- License
- Not openly licensed; the original prompt is shown word for word with credit and a link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 26, 2026: passed. Dry-run tested by our AI test agent on sample input. Fit check first; only facts-file content used; unsupported line flagged; deadline checked; not sent.
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 26, 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.