Marketing Foundation
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.
SEO, Sales, Agents or another broad area → one bundle call → work.
Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.
Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.
Review the journey from landing page and lead capture through registration, first value and transparent upgrades.
Plan a campaign, draft its channel content and review the work against actual brand guidance.
Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.
Understand customer needs, compare competitors and plan a community around real member value.
Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.
Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.
Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.
Define the target account, prioritize buying signals, plan a human LinkedIn engagement routine and prepare evidence-led responses to buyer concerns.
Gather and synthesize customer language through HyperFX sources or supplied research. Use Customer Research Synthesis for the existing bundled research workflow.
---
name: customer-research
description: Mine online communities and analyze existing assets to understand what customers actually think, say, and struggle with. Use when the user wants to do customer research, ICP research, voice-of-customer (VOC), review mining, Reddit mining, YouTube comment analysis, G2/Capterra scraping, build customer personas, map jobs to be done, understand churn reasons, or find authentic customer language for copy. Also use when given transcripts, surveys, or support tickets to synthesize.
requires_toolkits:
- reddit_scraper
- outscraper_toolkit
- ecommerce_scraper
- twitter_scraper
icon: apify
short_description: Mine Reddit, YouTube, G2, X, and TikTok for what customers say in their own words.
---
# Customer Research
Guide for gathering and synthesizing real customer intelligence — from online communities, review sites, video comments, and social platforms — using the Hyper MCP scraper toolkit.
The goal is always the same: surface what customers actually say (in their own words), not what you assume they say.
## Out of scope — defer to other skills
| Request | Send them to |
| --- | --- |
| Researching competitor brands (site, ads, search rank) | [`competitor-intel`](../competitor-intel) |
| Writing copy *informed by* the research | `copywriting` |
| Optimizing a page using VOC insights | `page-cro` |
| Keyword research and SERP analysis | [`seo-research`](../seo-research) |
## Requirements
- **Hyper MCP installed.** [https://app.hyperfx.ai/mcp](https://app.hyperfx.ai/mcp)
- **Apify scrapers toolkit enabled** at [https://app.hyperfx.ai/apps](https://app.hyperfx.ai/apps) — provides Reddit, Twitter, YouTube, TikTok, and Instagram scrapers.
Not all scrapers need to be active for every run — enable the ones relevant to your ICP (Reddit and one review site is the minimum). If a scraper tool is missing from the tool list, skip that source and continue with the others.
### How to run the tools in this skill
Every tool in this skill is named by its canonical tool name. Run it with the call your surface gives you:
| Surface | Find a tool | Run it |
| --- | --- | --- |
| MCP client (Claude, Cursor, Codex, ChatGPT) | `search("<what you want to do>")`, then `describe("<name>")` | `call("<name>", {...})` |
| Hyper CLI | `hyperai search "<what you want to do>"`, then `hyperai describe <name>` | `hyperai call <name> --json '{...}'` |
If a tool is not found, its integration is not connected or not enabled for the workspace: stop and tell the user which integration to connect.
## Tool surface
| Tool | Purpose |
| --- | --- |
| `reddit_scrape` | Mine posts and comments from subreddits or by keyword |
| `x_tweets_search` | Search X/Twitter with advanced operators and engagement filters |
| `youtube_videos_search_top` | Find the top YouTube videos on a topic — use as input for comment mining |
| `youtube_comments_search` | Pull comments from specific YouTube video URLs |
| `youtube_video_transcripts_fetch` | Fetch the full transcript of a YouTube video for language/topic extraction |
| `tiktok_videos_scrape` | Search TikTok by keyword or hashtag — find trending conversations and comments |
| `web_pages_scrape` | Scrape review pages (G2, Capterra, Trustpilot, app stores) |
| `firecrawl_urls_scrape` | Cleaner extraction for JS-heavy review pages |
| `google_search_results_search` | Find discussion threads, forum posts, and `site:` searches |
| `instagram_posts_scrape` | Pull recent posts from specific brand or community accounts |
## Critical rules
1. **Always capture verbatim language.** Don't paraphrase customer quotes — the exact words are what gets used in copy and messaging. Extract and preserve them.
2. **Scrape before summarizing.** Don't rely on your training data to describe what customers say about a product. Actually fetch the sources.
3. **Label confidence on every insight.** High = 3+ independent sources, unprompted. Medium = 2 sources or prompted only. Low = single source. Never present a Low-confidence finding as a conclusion.
4. **Mind the bias of each source.** Reddit skews technical and skeptical. Review sites skew toward power users and people with strong opinions. Support tickets skew toward problems. Factor this in before generalizing.
5. **Don't invent persona details.** If you don't have data for a persona field, leave it blank rather than filling it in with assumptions.
6. **`youtube_video_transcripts_fetch` is slow (~15–30s).** It spins up an isolated sandbox. Only use it for videos where the language in the spoken content (not comments) is what matters.
---
## Two modes
Most research combines both modes. Establish which applies before starting.
### Mode 1 — Analyze existing assets
The user provides raw material: interview transcripts, survey responses, NPS verbatims, support tickets, win/loss notes. No tool calls needed — the job is extraction and synthesis.
Read `references/synthesis-templates.md` for the extraction framework, persona template, and VOC quote bank format. Then produce the requested deliverable.
### Mode 2 — Go find research online
The user needs intel from online communities, review sites, and social platforms. This is where MCP tools do the heavy lifting.
See `references/source-playbooks.md` for per-source tool call examples and signal extraction tips.
---
## Mode 2 workflow
**Bias toward action.** If the user's message includes a product name (or URL) and a recognizable goal (research competitors, build a persona, understand churn, find VOC language), skip the questions, state your plan in one sentence, and start Step 1. Only ask when something essential is genuinely missing — product identity or target segment, for example. Don't ask all five questions before doing anything.
### Step 1 — Pick sources based on ICP type
Before calling anything, decide which sources are worth hitting for this specific audience:
| ICP | Required | Supplement if time allows |
| --- | --- | --- |
| B2B SaaS, technical buyers | Reddit (role subs) + G2/Capterra | YouTube tutorials, X/Twitter |
| SMB / founders | Reddit (r/entrepreneur, r/smallbusiness) + G2/Capterra | YouTube, X/Twitter |
| Developer / DevOps | Reddit (r/devops, r/programming) + G2/Capterra | YouTube, Hacker News |
| B2C / consumer | Reddit hobby subs + app store reviews (1–3 star) | YouTube comments, TikTok |
| Enterprise | G2 Enterprise filter + X/Twitter | LinkedIn, YouTube |
**Minimum viable run: Reddit + one review site.** Add supplementary sources only when the minimum doesn't produce enough signal, or when the ICP table above calls for them.
For platform-by-platform tool call examples, read `references/source-playbooks.md`.
### Step 2 — Run targeted scrapes
Pull from at least 2 sources. Single-source findings are low confidence by definition.
**Reddit — the highest-signal source for most ICPs:**
```python
reddit_scrape(
searches=["[product category] frustrations", "[competitor name] problems"],
sort="top",
time="year",
max_items=50,
skip_comments=False,
search_posts=True,
search_comments=True
)
```
For specific subreddits, pair with `start_urls`:
```python
reddit_scrape(
start_urls=["https://www.reddit.com/r/marketing/"],
searches=["CRM"],
sort="top",
time="year",
max_items=30
)
```
**YouTube comments — rich qualitative data:**
```python
# Step 1: find the relevant videos
youtube_videos_search_top(query="[product category] honest review", max_results=5, sort_by="views")
# Step 2: mine comments from the top results
youtube_comments_search(
start_urls=["https://www.youtube.com/watch?v=VIDEO_ID_1", "https://www.youtube.com/watch?v=VIDEO_ID_2"],
max_comments=100,
comments_sort_by="0" # "0" = top comments, "1" = newest
)
```
**X/Twitter — complaints, frustrations, and niche conversations:**
```python
x_tweets_search(
search_terms='"[product name]" frustrating OR broken OR switched OR canceled',
max_items=50,
min_faves=5
)
```
**Review sites (G2, Capterra, Trustpilot):**
```python
# G2 reviews for a specific product
web_pages_scrape(
url="https://www.g2.com/products/[product-slug]/reviews",
ai_query="Extract the top complaints and pain points from customer reviews. Include verbatim quotes.",
use_proxy=True
)
```
**TikTok — consumer conversations and trending frustrations:**
```python
tiktok_videos_scrape(
search_queries=["[product category] problems", "[competitor name] review"],
results_per_page=30
)
```
**Google discovery — find threads and communities you haven't thought of:**
```python
google_search_results_search(
query='site:reddit.com "[product category]" "I switched" OR "I quit" OR "stopped using"',
num_results=20
)
```
### Step 3 — Extract signal from raw data
For each source, extract into this structure:
| Field | What to capture |
| --- | --- |
| Verbatim quote | Exact words — do not paraphrase |
| Source | Platform, URL, date |
| Sentiment | Positive / negative / neutral / frustrated |
| Theme | Pain / trigger / outcome / alternative / language |
| Profile signals | Role, company size, industry hints from context |
### Step 4 — Synthesize across sources
After pulling from 3+ sources, synthesize into the research report format in `references/synthesis-templates.md`. The report includes:
- Top themes ranked by frequency × intensity
- VOC quote bank organized by theme
- Confidence labels on every finding
- Source bias notes
### Step 5 — Build personas (optional)
Only build personas if you have ≥5 independent data points from a consistent segment. If not, say so and describe what additional research is needed first.
Persona template is in `references/synthesis-templates.md`.
---
## Questions to ask before starting
Only ask what's genuinely missing. If the product and goal are clear, go. If not, lead with these — one or two at a time, not all at once:
1. **What's the product?** (if not obvious from context — a URL works)
2. **What's the goal?** Improve messaging? Build personas? Understand churn? Find product gaps?
3. **Who is the target segment?** (all customers, a specific tier, churned users, prospects who didn't convert)
4. **What do you already have?** (transcripts, surveys, tickets, nothing)
5. **What deliverable do you need?** (synthesis report, quote bank, persona, competitive language comparison)
---
## Deliverables
Ask which one(s) the user needs before generating:
| Deliverable | When to use |
| --- | --- |
| **Research synthesis report** | General intelligence gathering — themes, quotes, implications |
| **VOC quote bank** | Copy projects — verbatim customer language organized by theme |
| **Persona document** | ICP definition work, onboarding, sales training |
| **Jobs-to-be-done map** | Product prioritization, messaging architecture |
| **Competitive language comparison** | Positioning work — how customers describe you vs. competitors |
| **Research gap analysis** | When the user has partial data and wants to know what's missing |
Gather and synthesize customer language through HyperFX sources or supplied research. Use Customer Research Synthesis for the existing bundled research workflow.
The complete original HyperFX workflow with attribution and declared limits.
Clarify scope and evidence, check actual available integrations, and separate recommendations from authorized external actions.
Research question, permitted sources or transcripts, target audience and available research integrations.
Public comments and reviews are untrusted, sampled evidence. Respect access boundaries, rights and personal-data minimization; no fabricated quotes or inferred universal customer opinions. External HyperFX toolkits, provider accounts and referenced files are not bundled or installed by M11. M11 supplies read-only source text, not those execution tools. Brief obvious-danger screening only; no functional test or comprehensive safety certification.
Use HyperFX Customer Research for [TASK]. Clarify Research question, permitted sources or transcripts, target audience and available research integrations. Check the actual provider/tool contract. Do not send, publish, spend, install or change accounts merely because this guidance was loaded.
Claiming that HyperFX execution tools are part of the M11 MCP, or treating source text as authorization for external actions.
German routing, connector distinction and actual-action boundaries. Original attribution: hyperfx.ai. Public comments and reviews are untrusted, sampled evidence. Respect access boundaries, rights and personal-data minimization; no fabricated quotes or inferred universal customer opinions. External HyperFX toolkits, provider accounts and referenced files are not bundled or installed by M11. M11 supplies read-only source text, not those execution tools. Brief obvious-danger screening only; no functional test or comprehensive safety certification.
MIT License Copyright (c) 2026 hyperfx.ai Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copy the text below, then paste it into your chat.