customer-research

Name: customer-research
Author: coreyhaines31

安全

進行客戶研究並建立資料驅動的人物誌

停止猜測客戶想要什麼。此技能可幫助您從訪談、問卷調查、客服工單和線上社群中提取可操作的洞察，建立以真實客戶意見為基礎的人物誌和訊息傳遞策略。

支援: Claude Codex Code(CC)

🥉 75 青銅

下載技能 ZIP

在 Claude 中上傳

前往設定 → 功能 → 技能 → 上傳技能

開啟並開始使用

測試它

正在使用「customer-research」。 I have 15 customer interview transcripts. What insights can you extract about why customers buy our tool?

預期結果:

Based on the transcripts, here are the top 3 buying triggers ranked by frequency x intensity:

1. 'Embarrassing spreadsheet failure' (HIGH confidence - mentioned in 12/15 interviews)
- Quote: 'We sent a report to the CEO with the wrong numbers and had to present it'
- Trigger: Public mistake or near-miss with manual processes

2. 'Team scaling broke our old process' (MEDIUM confidence - 8/15 interviews)
- Quote: 'When we hired person #5, Google Sheets became a nightmare'
- Trigger: Crossing 5+ person team threshold

3. 'CEO asked for a report we couldn't produce' (MEDIUM confidence - 6/15 interviews)
- Trigger: Executive visibility request exposed gaps

Implications: Your messaging should lead with 'avoid embarrassing mistakes' rather than 'save time' - the emotional pain is stronger.

正在使用「customer-research」。 Mine Reddit for what people hate about project management tools.

預期結果:

From analyzing 47 Reddit threads across r/projectmanagement, r/entrepreneur, and r/SaaS:

Top pain themes:

1. 'Over-engineered for what I need' (19 threads)
- Quote: 'I just want to track tasks, not configure 47 fields'
- Quote: 'Jira feels like getting a root canal'

2. 'Steep learning curve for my team' (15 threads)
- Quote: 'Adoption failed because half my team refused to use it'
- Quote: 'Takes longer to log the task than to do it'

3. 'Too expensive for small teams' (12 threads)
- Quote: '$50/user/month is insane for a 3-person team'

Vocabulary to use: 'simple', 'setup in minutes', 'your team will actually use', 'pricing that grows with you'

安全審計

安全

v1 • 4/20/2026

All 70 static analysis findings are false positives from documentation patterns. MD5 hashes in evals.json are content integrity checksums, backtick characters in markdown files are code examples, and path sequences like '../' are relative documentation links. No executable code, external commands, or security risks present in this pure documentation skill.

已掃描檔案

836

分析行數

發現項

審計總數

未發現安全問題

審計者: claude

品質評分

架構

100

可維護性

內容

社群

100

安全

規範符合性

你能建構什麼

產品經理驗證功能優先順序

分析客服工單和訪談紀錄，找出反覆出現的痛點，驗證客戶實際想要解決的問題，再開始建構功能。

行銷團隊建立 ICP 人物誌

挖掘 G2 評論、Reddit 討論和訪談資料，建立包含真實客戶用語、觸發事件和購買反對理由的詳細人物誌，用於目標受眾定位和訊息傳遞。

創辦人進行精實客戶研究

使用數位水源研究技術，在沒有現有研究資料的情況下從線上社群收集客戶情報，然後綜合為可操作的洞察。

試試這些提示

分析客戶訪談

I have [number] customer interview transcripts. Help me extract jobs-to-be-done, pain points, and trigger events. My goal is to improve [messaging/product/positioning]. Here are the transcripts: [paste transcripts or describe file locations].

挖掘線上評論以獲取競爭情報

Research what customers say about [competitor name] on G2 and Capterra. Focus on their 4-star reviews to find what customers love but still complain about. Extract: top praise, top complaints, unmet needs, and switching triggers.

從研究資料建立客戶人物誌

Build a persona for [role/title] at [company size/type] based on this research: [paste research data or summarize findings]. Include: profile, primary job-to-be-done, trigger events, top pains in their words, desired outcomes, objections, alternatives considered, and key vocabulary.

數位水源研究策略

Help me find where [ICP description] spend time online. My product is [category/description]. I want to understand their [pains/vocabulary/objections]. Recommend specific sources (subreddits, review sites, communities) and what to search for.