# Customer Pain Mining > Extract verbatim customer complaints about competitors — the exact wording the founder's product copy should steal, in customers' own words. Use when a founder asks "what do users hate about X?", "what's broken about [category]?", "what's the white space?", or needs raw customer language for landing-page copy, custdev prep, ad copy, or product strategy. Combines Anysite MCP (Reddit broad sweeps,… - **Type:** Skill - **Install:** `agentstack add skill-anysiteio-agent-skills-customer-pain-mining` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [anysiteio](https://agentstack.voostack.com/s/anysiteio) - **Installs:** 0 - **Category:** [Content & Media](https://agentstack.voostack.com/c/content-and-media) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [anysiteio](https://github.com/anysiteio) - **Source:** https://github.com/anysiteio/agent-skills/tree/main/skills/customer-pain-mining ## Install ```sh agentstack add skill-anysiteio-agent-skills-customer-pain-mining ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Customer Pain Mining Competitors at the early stage aren't a threat — they're a **proxy for the customer**. Their unhappy users have already done your custdev calls. This skill harvests them. The goal is **verbatim wording**, not paraphrase. Founders summarize and lose the gold. Pull exact phrases — they become product copy. ## When this skill applies - A founder asks what users dislike about competitors or the category - Preparing custdev calls — you want talking points in the customer's own language - Writing landing-page copy or positioning — you need real pain wording - Hunting white-space features competitors aren't shipping - After `competitor-discovery` — going deeper on the named players ## What you need 1. **Competitor list** — 1 to 5 named competitors (run `competitor-discovery` first if there isn't one) 2. **Niche / category** — one line for context (e.g. "AI writing for students") 3. **Use case for the output** — affects source weighting: - Custdev prep → Reddit (long-form verbatim wins) - Ad copy → Exa for short blog-post pull-quotes - Product strategy → Exa for structured "Pros / Cons" review pages ## Tools **Anysite MCP**: - `mcp__claude_ai_Anysite__execute(source="reddit", category="search", endpoint="search_posts", params={...})` — Reddit posts by query (anonymous, viral, long-form). - `mcp__claude_ai_Anysite__execute(source="linkedin", category="search", endpoint="search_posts", params={"keywords": "", "sort": "relevance", "count": 15})` — LinkedIn posts BY professionals describing the pain. Critical: search by the PAIN, not the competitor name (see Step 5). - `mcp__claude_ai_Anysite__query_cache(cache_key, conditions, ...)` — filter cached results (e.g. `vote_count > 50`). - `mcp__claude_ai_Anysite__get_page(cache_key, offset)` — paginate. - `mcp__claude_ai_Anysite__execute(source="youtube", category="video", endpoint="video_comments", params={"video": "", "count": 50})` — comments under a competitor-review YouTube video; people who watched a 15-min review have committed to evaluating the product. Filter `like_count >= 5`. Watch for affiliate astroturf (5+ short identical-tone praises from different accounts). - `mcp__claude_ai_Anysite__execute(source="twitter", category="search", endpoint="search_posts", params={"query": "", "min_likes": 5, "count": 20, "language": "English"})` — viral short-form pain quotes. Set `min_likes` ≥ 50 for breakthrough quotes; otherwise filter aggressively for relevance because the query catches handle namesakes (e.g. "Bright" matches users named "Bright"). **Exa MCP** (covers review aggregators and blog content): - `mcp__claude_ai_Exa__web_search_exa(query, numResults)` — find blog reviews, comparison articles, "why I left X" Medium posts. - `mcp__claude_ai_Exa__web_fetch_exa(urls)` — pull full review content. Note: Exa fetch on Reddit URLs sometimes returns SOURCE_NOT_AVAILABLE; use the Anysite Reddit endpoint as primary for Reddit content. Budget: ~8 Anysite executes (3-4 Reddit + 1-2 LinkedIn + 1 YouTube + optional Twitter) + ~5 Exa calls. Reddit, LinkedIn, Exa, and YouTube comments each carry distinct slices of signal — Reddit is anonymous-viral, LinkedIn is identified-professional, Exa is curated review-blog, YouTube comments are evaluation-stage. ## Source mix — pick by segment BEFORE you start The order of sources depends on where the user lives professionally. Don't run blindly — pick the right primary first: | Segment | Primary | Secondary | Skip / late | |---|---|---|---| | Consumer + EdTech + B2C SaaS | Reddit broad sweep (Step 1) | Exa review blogs (Step 6) | LinkedIn helpful but not primary | | B2B SaaS sold to professionals (sales tools, marketing, HR) | LinkedIn issue-pain search (Step 5) | Exa fetch of structured review pages | Reddit thinner for these niches | | Developer tools / DevTool / AI infrastructure | Exa review blogs + LinkedIn issue-pain (parallel) + r/programming / r/LocalLLaMA / r/webscraping / r/AI_Agents | YouTube comments under review videos; Twitter for viral pain | — | | Mixed (pro-sumer, freelance tools) | Reddit + LinkedIn in parallel | Exa review blogs | — | Test (3 second check): "Would the typical user of this competitor post their complaint on Reddit (anonymous), LinkedIn (professional reputation), or a developer blog post (technical depth)?" Start with whichever wins. ## How to run ### Step 1 — Reddit category-level pain sweep (start broad) — **consumer / viral-pain niches only** Counterintuitively, **for niches where pain is broadly viral, a broad query often returns more pain than a negative query.** Reddit's algorithm surfaces high-virality posts; in pain-dominated niches (consumer detector/integrity scandals, broken health products, expensive subscriptions), pain dominates. `mcp__claude_ai_Anysite__execute(source="reddit", category="search", endpoint="search_posts", params={"query": " ", "sort": "top", "time_filter": "year", "count": 20})` For pain-dominant consumer niches (e.g. AI-writing-students), broad queries like `"best AI writing tool college essay"` (sort=top) surface viral pain posts at 20K–48K upvotes describing exactly the product friction you'd otherwise need to dig for. The query is framed as discovery but the algorithm bubbles up frustration. Pre-check before running this step: Skim the top 5 results' titles. If most are about regulation/ethics/controversy and NOT about product friction, the niche isn't pain-dominant and broad-Reddit-first will mislead. Drop to Step 2 + Step 5 instead. For developer / B2B niches, broad-Reddit-first usually misleads — skip to Step 2 + Step 5 + Step 6. ### Step 2 — Reddit per-competitor sweep For each named competitor, run ONE single-phrase query. Avoid OR-chains — Reddit's relevance ranking gets confused: `mcp__claude_ai_Anysite__execute(source="reddit", category="search", endpoint="search_posts", params={"query": " ", "sort": "relevance", "time_filter": "year", "count": 15})` Working query patterns: - `" review"` — review threads - `" "` — e.g. `"QuillBot paraphrase robotic"` or `"Bright Data expensive failed requests"` - `" "` — e.g. `"Jenni citations hallucination"` or `"Firecrawl credit multiplier"` - `" alternative"` — implicit critique (also surfaces substitute names) Anti-patterns to avoid: - OR-chains like `" sucks OR broken OR hate OR alternative"` confuse relevance and return off-topic threads. - Single-phrase queries combining a smaller-brand name with multiple descriptors can return zero results because the smaller brand has a thin Reddit footprint. Start with the most-talked-about competitor first. For each post, capture: title, subreddit, vote_count, any quotable phrase from the title. Titles are usually the most distilled version of the complaint. Filter cached results to keep only posts with real engagement (10+ votes for small subs, 50+ for major ones): ``` mcp__claude_ai_Anysite__query_cache(cache_key="", conditions=[{"field": "vote_count", "op": ">=", "value": 10}], sort_by="vote_count", sort_order="desc") ``` ### Step 3 — Find the dedicated subreddit Niche pain often clusters in a single subreddit dedicated to the problem. For AI-writing-detection pain, validation has surfaced `r/BypassAiDetect`, `r/humanizing`, `r/PromptEngineering`. For web-scraping API pain, the recurring subs are `r/webscraping`, `r/WebScrapingInsider`, `r/WebDataDiggers`, `r/Agent_AI`, and `r/LocalLLaMA` (self-host workaround). If you spot a recurring sub in Step 1–2 results, run one targeted query inside it via title-keyword filtering — though the Reddit endpoint doesn't filter by sub directly, results from that sub float to the top of relevance queries. ### Step 4 — YouTube comments under a top review video For consumer or DevTool products with strong YouTube review presence, comments under a 10–30K-view "honest review" video are dense pain. People watching a 15-minute review have committed to evaluating the product. 1. `mcp__claude_ai_Anysite__execute(source="youtube", category="search", endpoint="search_videos", params={"query": " honest review problems", "count": 10})` — pick 1–2 videos with `view_count >= 5000` and `duration_seconds >= 300`. 2. `mcp__claude_ai_Anysite__execute(source="youtube", category="video", endpoint="video_comments", params={"video": "", "count": 50})` 3. Filter `like_count >= 5`. Watch for affiliate astroturf — 5+ short identical-tone praise comments from different accounts is paid promotion, not signal. Skip the cluster. Validated on the web-scraping niche: Greg Isenberg's Firecrawl explainer (169K views) returns comments like `"dont use the firecrawl agent, it sucks"` plus free-tier and pricing questions that are themselves a signal. ### Step 5 — LinkedIn issue-pain search (the most underused primitive) The key insight: Searching LinkedIn by *competitor name* (e.g. `"QuillBot review"`) returns affiliate-marketer spam. Searching by *the pain itself* (e.g. `"Turnitin flagged my essay"`, `"scrapers break every time website changes"`) returns verifiable professionals describing the problem with their names attached. This is the most underused pain source. LinkedIn pain has a property Reddit doesn't: identity + social proof. A Wharton professor writing "False positives are unavoidable with AI detectors" carries weight anonymous Reddit can't. A founder can @-mention the person to do custdev. #### Query patterns that work ``` mcp__claude_ai_Anysite__execute(source="linkedin", category="search", endpoint="search_posts", params={"keywords": "", "sort": "relevance", "count": 15}) ``` Examples that have surfaced high-engagement pain quotes: - AI-writing niche: `"AI detector false positive student essay"`, `"Turnitin flagged my essay"` — surface Wharton professors, PhDs, undergrads with 65–222 likes describing false-positive pain in their own words. - Web-scraping API niche: `"scrapers break every time website changes"` — Eric Vyacheslav's Scrapling launch post at **2,045 likes**, the single highest-engagement pain quote in the niche. - B2B SaaS niche: `""` — search by the verb of the pain ("manually copying from website to spreadsheet"), not the product name. #### Query patterns that don't work - `"Grammarly frustrating problem"` → mostly generic frustration posts, not Grammarly-specific (10/10 noise). - `"QuillBot review"` → affiliate marketing posts ("I made $4200 with QuillBot"), not pain. - `" alternative"` → promotional content from competing vendors. Why: LinkedIn rewards branded posts that drive engagement — affiliates and brand content rank above complaints under product-name queries. Reddit is the opposite. On LinkedIn, search by the *problem*, not the *product*. #### How to filter Use `query_cache` to keep only posts with engagement (reactions[0].count >= 5) and pull from the result. The first reaction in the array is usually "like" with the highest count. #### Bonus filter: by `author_industries` or `author_title` If your niche has a clear professional audience, add `author_industries` (e.g. "Education", "Higher Education", "Marketing and Advertising", "Information Technology and Services") or `author_title` (e.g. "Professor", "Marketing Director") to narrow to in-domain voices. ### Step 6 — Exa: review blog posts (verbatim quote goldmine) This is where the highest-density verbatim quotes live. Describe the ideal review post: `mcp__claude_ai_Exa__web_search_exa(query=" honest review complaints — what's frustrating about it — blog post", numResults=6)` A well-targeted query typically surfaces 6 review posts in one call, each with 5–10 pull-quote complaints. The Exa snippets often contain the quote directly — you may not even need to fetch. If you need more context, fetch: `mcp__claude_ai_Exa__web_fetch_exa(urls=[""])` Validated on the web-scraping niche: `"honest review of Firecrawl Bright Data Apify web scraping API — what's frustrating about pricing and reliability — developer blog post"` returned 8 review blogs with structured Pros/Cons including the verbatim ScrapeGraphAI breakdown: *"Firecrawl's credit multipliers make the real cost 5-7x higher than the headline numbers suggest for AI extraction workloads."* ### Step 7 — Exa: "why I left" / churned-user posts Long-form pain from people who actively quit: `mcp__claude_ai_Exa__web_search_exa(query="why I stopped using — switched to alternative — frustrated user blog post", numResults=5)` Churned-user posts are gold for product strategy because the user has already articulated their next-best alternative and the specific reason they left. ### Step 8 — Cluster the pain Read everything. Group into **3–5 themes**. Themes should be distinct (don't merge "buggy" with "expensive"). For each theme: - 3–6 word name (e.g. "AI-detector false flags ruin grades") - **2–3 verbatim quotes**, with quotation marks. Cite source: subreddit + post title + vote_count, OR LinkedIn name + headline + reactions, OR blog URL. - 1-line **trigger** — what causes the complaint (specific feature, pricing change, competitor release) - 1-line **workaround** users describe — often the seed of a feature idea - (optional) **Cross-platform signal**: if pain appears on Reddit AND LinkedIn AND Exa-blogs, that's a strong validated pattern — call it out. ### Step 9 — Identify white space The single most valuable output: what users **ask for** that no competitor ships. Re-scan everything for phrases: - "I wish X did Y" - "If only..." - "Why doesn't anyone..." - "I would pay for..." - "I built my own script to..." Pull these separately. Each is a candidate feature with proven demand. Even 1–2 quotes here is gold. ## Output Markdown report, ~600–900 words: ``` # Pain Mining — ## Executive summary 3 sentences: the dominant pain theme, the most-asked-for-but-missing feature, the one quote the founder should pin to the wall. ## Pain clusters ### 1. (most common) - "" — r/, "" ( votes) - "" — blog: - "" — r/, "" **Trigger:** **Workaround:** ### 2. [same pattern] ### 3. [same pattern] ## White space (asked for, not shipped) - "" — - "" — ## Recommendations - Landing-page copy line the founder could literally use - Custdev question to validate the dominant pain - One product gap worth exploring ``` ## Quality bar - **Verbatim only.** If you can't find a real quote, mark the cluster "weak evidence" and move on. - **At least 2 quotes per cluster.** One quote is anecdote; two is pattern. - **Cite every quote.** The founder must be able to validate it themselves. - **Don't editorialize.** "Users find onboarding frustrating" is paraphrase. "I spent 3 hours trying to import my data" is the real thing. - **Filter astroturf.** If a "complaint" is suspiciously polished and links to a competitor's homepage in the same paragraph, skip it. ## Don't - Don't fabricate quotes. Ever. If signal is thin, return fewer clusters. - Don't exceed ~8 Anysite calls + ~6 Exa calls. - Don't rank-order pain by your judgment — order by engagement (vote count, reactions). - Don't bury white space at the bottom — it's often the single most valuable section. - Don't write paragraphs. Quotes + 1-line annotations only. - Don't use Reddit OR-chains (`A OR B OR C OR D`) — confuses ranking. Single-phrase queries only. - Don't search LinkedIn by competitor name (`"QuillBot review"`, `"Grammarly frustrating"`) — that returns affiliate spam. Search by the pain itself (`"Turnitin flagged my essay"`, `"scrapers break every time website changes"`). - Don't run Twitter without aggressive engagement filters. `min_likes` ≥ 5 catches namesake-handle noise (e.g. `"Bright Data"` matches users whose handle starts with `bright_`); for breakthrough quotes set ≥ 50 and skim manually. - Don't try to use the Anysite `g2` source for verbatim reviews — only `g2/search/search` is exposed and it returns category listings without Pros/Cons content. For G2-style review depth, use Exa to fetch the actual G2 page URL or use the Exa-for-review-blogs pattern in Step 6. - Don't blindly run … ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [anysiteio](https://github.com/anysiteio) - **Source:** [anysiteio/agent-skills](https://github.com/anysiteio/agent-skills) - **License:** MIT Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-anysiteio-agent-skills-customer-pain-mining - Seller: https://agentstack.voostack.com/s/anysiteio - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.