When should you use it?
- You are choosing what to write next
- You want real user language, not guesses
- You have not curated sources yet
Not for: Topics where you already have a short list of trusted links; Quoting users publicly without context
What do you need, and what do you get?
You need
- Topic
- How many sources
- Source type and focus, for example complaints
You get
- List of threads with the pain point each one shows
- Notes on recurring themes
How does it work, step by step?
- Fill the templateState topic, number of sources, where to look, what to look for and why.
- Let it runExpect around a quarter hour for a few dozen sources.
- Group the pain pointsAsk for themes with counts and example threads.
- Pick your angleChoose the theme with the most real frustration you can help with.
- Keep the linksSave thread links so you can revisit wording later.
The prompt
The original prompt by Raghav Mehra, 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 Custom agent, ChatGPT agent and Claude. Values in lime are placeholders.
Original prompt by Raghav Mehra
Research Task: Add [TOPIC] Sources to NotebookLM Objective: Curate and add at least [NUMBER] [SOURCE TYPE] containing [WHAT YOU’RE RESEARCHING] to NotebookLM. Instructions: 1. Find and add [NUMBER]+ [SOURCE TYPE] discussing [TOPIC/PAIN POINTS] 2. Use NotebookLM’s “Add Source” feature to input URLs 3. Use NotebookLM’s “Discover” feature to find additional related sources about [TOPIC] 4. Add all discovered sources to the notebook Expected Outcome: A NotebookLM notebook with [NUMBER]+ sources covering [WHAT YOU WANT TO LEARN/ANALYZE].
Exactly as published by Raghav Mehra in I Made Perplexity Comet My Substack Assistant for a Week - Here are 4 Workflows That Actually Worked + Prompt Templates.
Our adapted version (optional)
Find [30] Reddit threads from the last six months where people discuss [topic]. Focus on complaints, workarounds and feature wishes. For each thread give the link, subreddit, the main frustration in one line and a short paraphrase of how people describe it. Then group everything into themes, ranked by how many separate threads mention each, and suggest one article angle per theme.
What can go wrong?
- Broad search suits open questions; if you have curated links, browse them yourself instead.
- Loud threads are not always representative; note how many separate people raise a point.
Our take
The writer's guidance is the useful part: use the AI browser when you are not yet committed to sources and need wide search, and fall back to normal browsing when precision matters. Raghav's template asks for topic, number of sources, where to look, what to look for and why, and that structure is what makes the run repeatable. Let it work for about a quarter of an hour, then ask for themes with counts and example threads, so you can see which frustration comes up across many different people rather than one loud thread. Keep the thread links; the actual wording users choose is often the best headline material. Check quotes in context before using them, and do not quote users publicly in a way that exposes them. Stay within Reddit's terms and keep it to reading. If you already have a short list of trusted links, his advice applies: browse those yourself instead, because wide search is for when you have not chosen your sources yet.
Where the time goes back: An evening of scrolling forums becomes a short wait and a grouped list.
FAQ
Did it need supervision?
Why a template?
Source and credit
The original prompt on this page is by Raghav Mehra, shown word for word with a link to where it was published. The summary, notes and adapted version are ours.
- Original
- I Made Perplexity Comet My Substack Assistant for a Week - Here are 4 Workflows That Actually Worked + Prompt Templates
- Creator
- Raghav Mehra
- Published on
- cashandcache.substack.com (Substack)
- Original date
- Oct 28, 2025
- 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 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.