When should you use it?
- You have a question that needs many searches
- You want a table, not an essay
- You can check samples by hand
Not for: Questions answered by one source; Research needing paywalled data
What do you need, and what do you get?
You need
- Clear question and fields to collect
- Search tool for agents
- Budget
You get
- Dataset table
- Trend notes
- Sample checks
How does it work, step by step?
- Define fieldsDecide exactly what each row should record.
- Split the searchesDivide the space, such as by industry or year.
- Run in parallelHave agents search and fill rows with a source link each.
- DeduplicateMerge duplicates and drop rows without a source.
- Check a sampleVerify some rows yourself before trusting trends.
The prompt
Our own prompt, inspired by lukasthoms on Hacker News and written to work in Claude. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
I want a dataset answering: {question}. Fields per row: {fields}, plus a source URL. Split the search space into {n} parts, search each, and return rows only when a source supports them. Merge duplicates, then summarize trends and list ten random rows for me to check.
Inspired by lukasthoms on Hacker News: Comment in Every AI Name. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Thousands of searches cost money; set a cap.
- Agents can invent rows; require a link for each.
- Trends from search results reflect what is easy to find.
Our take
lukasthoms built this for fun, but the pattern behind it is genuinely useful: break a broad question into thousands of narrow searches, run them in parallel, and assemble the results into a table you can analyze. The quality depends on a few unglamorous rules. Decide the fields before launching, such as company, bot name, industry, launch year and source link, so agents return comparable rows. Require a link for every row, merge duplicates, and check a random sample by hand before believing any trend; a single agent that misreads a page can skew a small category. Be careful about what conclusions mean. Searches find what is publicized and indexed, so a drop in launches could partly reflect fewer press releases rather than fewer bots, and the author rightly avoids over-interpreting. Set a budget before starting, since thousands of searches add up, and save raw results so you can rerun the analysis later. The same approach works for competitor pricing, local service listings or tracking how a term spreads.
Where the time goes back: A curiosity question turns into a real dataset in an afternoon.
FAQ
How many searches?
What did it find?
Source and credit
Inspired by lukasthoms on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Comment in Every AI Name
- Creator
- lukasthoms on Hacker News
- Published on
- Hacker News
- Original date
- Oct 11, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude
- 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, bookings 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.