← Back to library

Turn a customer-discovery routine into a coding-agent skill

u/Appropriate-Rip6784 on r/AgentsOfAI stopped maintaining a multi-part agent for customer discovery on Reddit and recreated the workflow as one Codex skill. It checks which communities are relevant, collects evidence, groups recurring problems and returns a brief you can hand to product.

  • OutcomeTurn a working customer-research routine into a skill your coding agent can rerun: find the right communities, gather evidence and group the problems people describe.
  • SetupAn afternoon+
  • LevelAdvanced
  • Creditu/Appropriate-Rip6784 on r/AgentsOfAI
View original
Works with
Claude CodeCustom agentClaude Cowork

Published Oct 20, 2026Updated Oct 20, 2026AI dry run on sample input: passed Oct 20, 2026Source verified Oct 24, 2026

When should you use it?

  • You're exploring a market or product idea and want to hear problems in customers' own words
  • You've run this kind of research by hand and want it repeatable
  • You already use a coding agent with web access

Not for: Contacting or messaging the people whose posts you read; Collecting personal details about individual users

What do you need, and what do you get?

You need

  • The market or problem area you're researching
  • A coding agent that supports skills or reusable instructions
  • Optional: a short list of communities you already know

You get

  • A list of relevant communities, each checked for fit
  • Problem clusters with links to the posts that support them
  • A ranked summary of which problems show signs people would pay to solve

How does it work, step by step?

  1. Write the method downDescribe how you research: which communities qualify, what counts as evidence, how to group problems.
  2. Add an approval checkpointHave the skill propose its plan and communities, and wait for your go-ahead before the main pass.
  3. Use code where it must be exactDeduplicate links, normalize URLs and compute scores with small scripts, not the model.
  4. Keep going in the same sessionAsk follow-up questions or dig into one cluster after the report arrives.

The prompt

Our own prompt, inspired by u/Appropriate-Rip6784 on r/AgentsOfAI and written to work in Claude Code, Custom agent and Claude Cowork. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt3 variables
Topic for this customer discovery run: {topic}. Source: Reddit.
Step 1 (plan): propose up to {n} relevant communities with one line on why each fits, plus your search terms. Stop and wait for my approval.
Step 2 (evidence): for approved communities, collect posts and comments where people describe a problem, workaround or wish. Save the link and a short paraphrase for each. Use scripts to deduplicate and normalize URLs.
Step 3 (clusters): group the evidence into problem clusters. Only count a cluster if it has at least {min_posts} independent posts.
Step 4 (report): for each cluster, summary, evidence links, and any signs people pay for solutions today.
Don't post, vote or message anyone, and don't record usernames in the report.

Inspired by u/Appropriate-Rip6784 on r/AgentsOfAI: I replaced a fairly complex Reddit research agent with a Codex skill. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • A few loud threads can look like a trend. Require several independent posts before calling something a cluster.
  • Respect each community's rules and platform terms; read, don't scrape at a scale that strains the site.

Our take

This post makes a useful argument for anyone tempted to build a custom research agent: often you only need to write down your method and let an existing coding agent run it. The poster took a multi-part Reddit research agent and rebuilt it as a single skill, and was struck by how much didn't need building, such as an agent loop, a model client, a browsing layer or a UI. Two design choices are worth copying. There's a human checkpoint before the expensive part of the run, so you can correct the plan and the list of communities. And deterministic jobs like deduplication, URL cleanup and scoring are done by small scripts rather than the model, which keeps the output consistent from run to run. We'd add a rule that every problem cluster links to the posts that support it, so you can judge the evidence yourself. In our dry run on a saved set of 60 made-up posts about invoicing software, our prompt proposed 4 communities and waited for approval, grouped 5 problem clusters with supporting links, and dropped a cluster built on only one thread.

Where the time goes back: Research you'd repeat by hand for each new idea becomes one instruction, and the evidence comes back organized instead of as a pile of tabs.

FAQ

Why a skill rather than a custom agent?
The poster's point is that a capable coding agent can already think through problems, browse, read files and run tools. The skill only needs to describe the method, which is less to build and maintain.
Can it be reused for other research?
Yes. The same structure (plan, approval, evidence, clusters, report) works for competitor reviews or support forums.

Source and credit

Inspired by u/Appropriate-Rip6784 on r/AgentsOfAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
I replaced a fairly complex Reddit research agent with a Codex skill
Creator
u/Appropriate-Rip6784 on r/AgentsOfAI
Published on
Reddit
Original date
Aug 9, 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 20, 2026: passed. Dry-run tested by our AI test agent on sample input. Checkpoint and evidence threshold worked.
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.

More in Marketing

All 97 Marketing playbooks →

Related playbooks

MarketingSkill✓ AI dry run

Get interviewed for real stories before AI writes your posts

Let an agent interview you once to build a reusable bank of your real numbers, turning points and opinions, so AI-drafted LinkedIn posts draw on facts you supplied instead of invented ones.

Credit: sergebulaev

Under an hour
MarketingWorkflow✓ AI dry run

Ship a competitor deck and feature spreadsheet

Replace an afternoon of tab-opening competitor research with an agent that finds the top players, benchmarks their positioning, and exports a deck and a spreadsheet.

Credit: Nick Woodford

Under an hour