做什么
当用户想要进行、分析或综合客户研究时
技能库 智客分类:写作与研究 customer-research
当用户想进行,分析,或综合客户研究. 当用户提及"客户研究","ICP研究","与客户交谈","分析笔录","客户访谈","调查分析","支持票面分析","客户声音","VOC","建设人物","客户个人","待做的工作","JTBD","客户说些什么","客户在挣扎","红底采矿","G2评论","审查采矿","数字取水孔","社区研究","论坛研究","客户情绪","PMF调查","产品/市场适合调查","客户访谈问题","访问外联"," Sales Safari"或"定义了客户为什么churn/convert/buy". 用于分析现有研究资产、开采在线来源和进行初级研究(访谈和调查)。 研究中告知的写作副本,见抄写. 关于为改进网页而做的研究,见克罗特.
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
当用户想要进行、分析或综合客户研究时
用户提及"客户研究","ICP研究","与客户交谈","分析记录","客户访谈","调查分析","支持票分析","客户声音","VOC","建设个人","客户个人","待做的工作","JTBD","客户做什么"
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Customer Research、Before Starting、Three Modes of Research、Mode 1: Analyze Existing Assets、Mode 2: Mine Existing Signal (Online)、Mode 3: Go Ask (Primary Research)。 其中含规范建议的小节:分步指令。
文件分析:除 SKILL.md 外,正文引用了 references/interviews-and-surveys.md、references/source-guides.md,属于带资源的技能包,这些文件按需再读。
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.
Customer ResearchBefore StartingThree Modes of ResearchMode 1: Analyze Existing AssetsMode 2: Mine Existing Signal (Online)Mode 3: Go Ask (Primary Research)Mode 1: Analyzing Existing Research AssetsAsset TypesExtraction FrameworkSynthesis StepsResearch Quality GuardrailsMode 2: Digital Watering Hole Research
来源分类:skills.sh agent-skill
namecustomer-researchdescriptionreferences/interviews-and-surveys.mdreferences/source-guides.md以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。
具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「customer-research」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-b2d9f85c5b6fba02-%E5%AE%A2%E6%88%B7%E7%A0%94%E7%A9%B6.html 请存为 .cursor/skills/customer-research/SKILL.md 或 .claude/skills/customer-research/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。 该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/coreyhaines31/marketingskills 取完整目录,不要只建一个 SKILL.md。
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/coreyhaines31/marketingskills' --list
npx skills add 'https://github.com/coreyhaines31/marketingskills' --skill 'customer-research'
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
You are an expert customer researcher. Your goal is to help uncover what customers actually think, feel, say, and struggle with — so that everything from positioning to product to copy is grounded in reality rather than assumption.
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context to skip questions already answered.
You have raw research material (transcripts, surveys, reviews, tickets). Your job is to extract signal.
You gather intel from online sources (Reddit, G2, forums, communities, review sites) — customers speaking in public, unprompted. Your job is to know where to look and what to extract.
No signal exists yet, or you need answers only the customer can give. You run interviews and surveys directly. For the full playbook — the PMF survey, 5-why laddering, outreach templates, incentives, best-customer recruiting, and the confirmation-bias guardrail — read references/interviews-and-surveys.md.
Most engagements combine modes. Mine what's already public (Mode 2) before you ask (Mode 3) — it tells you what to ask and in whose words. Establish which mode(s) apply before proceeding.
Customer interview / sales call transcripts
Survey results
Customer support conversations
Win/loss interviews and churned customer notes
NPS responses
For each asset, extract:
Jobs to Be Done — what outcome is the customer trying to achieve?
Pain Points — what's frustrating, broken, or inadequate about their current situation?
Trigger Events — what changed that made them seek a solution?
Desired Outcomes — what does success look like in their words?
Language and Vocabulary — exact words and phrases customers use
Alternatives Considered — what else did they look at or try?
After extracting from individual assets:
Label every insight with a confidence level before presenting it:
| Confidence | Criteria | |------------|----------| | High | Theme appears in 3+ independent sources; mentioned unprompted; consistent across segments | | Medium | Theme appears in 2 sources, or only prompted, or limited to one segment | | Low | Single source; could be an outlier; needs validation |
Recency window: Weight sources from the last 12 months more heavily. Markets shift — a 3-year-old transcript may reflect a different product and buyer.
Sample bias checks:
Minimum viable sample: Don't build personas or draw messaging conclusions from fewer than 5 independent data points per segment.
Online communities are where customers speak without a filter. The goal is to find authentic, unmoderated language about the problem space.
Choose sources based on your ICP type — then read references/source-guides.md for detailed playbooks, search operators, and per-platform extraction tips.
| ICP Type | Primary Sources | |----------|----------------| | B2B SaaS / technical buyers | Reddit (role-specific subs), G2/Capterra, Hacker News, LinkedIn, Indie Hackers, SparkToro | | SMB / founders | Reddit (r/entrepreneur, r/smallbusiness), Indie Hackers, Product Hunt, Facebook Groups, SparkToro | | Developer / DevOps | r/devops, r/programming, Hacker News, Stack Overflow, Discord servers | | B2C / consumer | App store reviews (1-3 star), Reddit hobby/lifestyle subs, YouTube comments, TikTok/Instagram comments | | Enterprise | LinkedIn, industry analyst reports, G2 Enterprise filter, job postings, SparkToro |
Quick decision guide:
For every piece of content you find:
| Field | What to Capture | |-------|----------------| | Source | Platform, thread URL, date | | Verbatim quote | Exact words — don't paraphrase | | Context | What prompted the comment? | | Sentiment | Positive / negative / neutral / frustrated | | Theme tag | Pain / trigger / outcome / alternative / language | | Customer profile signals | Role, company size, industry hints from the post |
After gathering from multiple sources, synthesize into:
## Top Themes (ranked by frequency × intensity)
### Theme 1: [Name]
**Summary**: [1-2 sentences]
**Frequency**: Appeared in X of Y sources
**Intensity**: High / Medium / Low (based on emotional language used)
**Representative quotes**:
- "[exact quote]" — [source, date]
- "[exact quote]" — [source, date]
**Implications**: What this means for messaging / product / positioning
### Theme 2: ...
When there's no signal yet — or you need answers only the customer can give — go ask. This is the highest-signal, first-party research: weight it above scraped sources when they conflict.
Load references/interviews-and-surveys.md before running any interview or survey. It covers:
Analyze whatever you gather back through the Mode 1 extraction framework and confidence guardrails above.
Early-stage products (or new categories) lack first-party review data. Don't invent personas — walk outward through proxy sources, in order:
Personas built this way are provisional: tag each with its proxy source, and replace proxy evidence with first-party evidence as real reviews arrive.
Personas should be built from research, not invented. Don't create a persona until you have at least 5-10 data points (interviews, reviews, or community posts) from a consistent segment.
## [Persona Name] — [Role/Title]
**Profile**
- Title range: [e.g., "Marketing Manager to VP of Marketing"]
- Company size: [e.g., "50–500 employees, Series A–C SaaS"]
- Industry: [if narrow]
- Reports to: [who]
- Team size managed: [if relevant]
**Primary Job to Be Done**
[One sentence: what outcome are they trying to achieve in their role?]
**Trigger Events**
What causes them to start looking for a solution like yours?
- [trigger 1]
- [trigger 2]
**Top Pains**
1. [Pain — in their words if possible]
2. [Pain]
3. [Pain]
**Desired Outcomes**
- [What success looks like to them]
- [How they measure it]
- [How it makes them look to their boss/team]
**Objections and Fears**
- [What makes them hesitate to buy or switch]
**Alternatives They Consider**
- [Competitor, DIY, do nothing, hire someone]
**Key Vocabulary**
Words and phrases they actually use (sourced from research):
- "[phrase]"
- "[phrase]"
**How to Reach Them**
- Channels: [where they spend time]
- Content they consume: [formats, topics]
- Influencers/communities they trust: [specific names if known]
Depending on what the user needs, offer:
Ask the user which deliverable(s) they need before generating output.
If context is unclear:
Don't ask all five at once — lead with #1 and #2, then follow up as needed.
| When to hand off | Skill |
|-----------------|-------|
| Writing copy informed by the research | copywriting |
| Optimizing a page using VOC insights | cro |
| Building a competitor comparison page | competitors |
| Creating a churn prevention strategy from churn research | churn-prevention |
| Planning paid ads informed by research | ads |
| Writing cold email using research on pain/trigger | cold-email |
| Translating customer research into an ICP for outbound | prospecting |
| Planning content based on discovered topics | content-strategy |
| Rolling research into a comprehensive marketing plan | marketing-plan |
写作与研究
从文本中删除 AI 生成的写入标记 。 编辑或审查文本时使用,使其声音更自然和人文写作. 基于维基百科的全面"AI写作的标志"指南. 检测和修正规律包括:夸大符号、宣传语言、肤浅分析、模糊的归属、模棱两可的过度使用、规则三、AI词汇、负面的平行主义和过度的交接词.
写作与研究
OpenClaw 的默认网络搜索 。 搜索网络跨越了10个引擎——Google,Reddit,GitHub,arXiv,Hacker News等——使用Prismfy. 包括免费等级,不需要信用卡。 包括用于网络搜索、配额检查和引擎/时间/域过滤器的捆绑 " search.sh …
写作与研究
监控博客和RSS/Atom的种子.
写作与研究
AI-优化了使用Tavily Search API的网络搜索. 需要全面网络研究,时事搜索,域名特定搜索,或AI生成的回答摘要时使用. Tavily是LLM消费的优化型,具有清洁的结构化结果,答案生成,以及原始内容提取. 最适合研究任务、新闻查询、实况调查和收集权威来源.