客户画像:AI 驱动的买家研究 - Openclaw Skills

作者:互联网

2026-03-29

AI教程

什么是 客户画像?

客户画像技能使开发人员和营销人员能够构建高质量、有研究支撑的受众概况,这远远超出了基本的假设。通过利用先进的搜索能力和 AI 图像生成,该工具将人口统计、心理特征和待办事项(JTBD)综合成可操作的模板。对于那些需要用实际数据验证产品市场匹配度的人来说,它是 Openclaw Skills 库的基石。

该技能自动收集市场趋势、薪资数据和工具使用模式,允许团队创建真实的虚拟角色和详细的旅程地图。无论您是为新的 SaaS 产品定义目标受众,还是完善内容策略,该工具都能确保您的画像建立在专业的行业事实基础之上。

下载入口:https://github.com/openclaw/skills/tree/main/skills/okaris/customer-persona

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

npx clawhub@latest install customer-persona

2. 手动安装

将技能文件夹复制到以下位置之一

全局模式 ~/.openclaw/skills/ 工作区 /skills/

优先级:工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

请帮我使用 Clawhub 安装 customer-persona。如果尚未安装 Clawhub,请先安装(npm i -g clawhub)。

客户画像 应用场景

  • 基于实时数据,利用高保真买家画像制定营销策略。
  • 通过以用户为中心的研究和心理特征分析指导产品开发。
  • 创建针对量化客户痛点的销售赋能材料。
  • 绘制客户旅程图,以识别销售周期中的摩擦点和购买触发因素。
  • 定义反向画像以简化线索转化并避免资源浪费。
客户画像 工作原理
  1. 使用搜索助手研究目标市场,收集人口统计数据、行业调查和当前的薪资报告。
  2. 分析心理数据,识别驱动用户行为的价值观、动机和专业兴趣。
  3. 量化痛点和目标,从模糊的假设转向可操作的、有数据支持的洞察。
  4. 应用待办事项 (JTBD) 框架对功能、情感和社会需求进行分类。
  5. 绘制购买流程图,识别触发因素、关键影响者和潜在阻碍。
  6. 使用 AI 图像模型生成视觉形象,为数据概况提供人性化元素。

客户画像 配置指南

要开始使用此技能,请安装 inference.sh CLI 并登录。您还可以添加相关的 Openclaw Skills 以增强您的研究能力。

curl -fsSL https://cli.inference.sh | sh && infsh login

# 添加支持模块
npx skills add inference-sh/skills@web-search
npx skills add inference-sh/skills@ai-image-generation

客户画像 数据架构与分类体系

该技能将画像数据组织成结构化板块,以确保清晰度和专业实用性:

数据板块 组件 格式
人口统计 年龄、收入、教育、地点、职位 数值范围
心理特征 价值观、态度、动机、性格 列表
目标 职业成就和个人抱负 无序列表
痛点 量化的挑战(例如,每周损失的小时数) 项目符号列表
JTBD 功能、情感和社会任务 分类表格
购买流程 知晓、考虑、决策和触发因素 基于阶段的地图
name: customer-persona
description: "Research-backed customer persona creation with market data and avatar generation. Covers demographics, psychographics, jobs-to-be-done, journey mapping, and anti-personas. Use for: marketing strategy, product development, UX research, sales enablement, content strategy. Triggers: customer persona, buyer persona, user persona, target audience, ideal customer, customer profile, audience research, user research, icp, ideal customer profile, target market, customer avatar, audience persona"
allowed-tools: Bash(infsh *)

Customer Persona

Create data-backed customer personas with research and visuals via inference.sh CLI.

Quick Start

curl -fsSL https://cli.inference.sh | sh && infsh login

# Research your target market
infsh app run tavily/search-assistant --input '{
  "query": "SaaS product manager demographics pain points 2024 survey"
}'

# Generate a persona avatar
infsh app run falai/flux-dev-lora --input '{
  "prompt": "professional headshot photograph of a 35-year-old woman, product manager, friendly confident expression, modern office background, natural lighting, business casual attire, realistic portrait",
  "width": 1024,
  "height": 1024
}'

Install note: The install script only detects your OS/architecture, downloads the matching binary from dist.inference.sh, and verifies its SHA-256 checksum. No elevated permissions or background processes. Manual install & verification available.

Persona Template

┌──────────────────────────────────────────────────────┐
│  [Avatar Photo]                                      │
│                                                      │
│  SARAH CHEN, 34                                      │
│  Product Manager at a Series B SaaS startup          │
│                                                      │
│  "I spend more time making reports than making       │
│   decisions."                                        │
│                                                      │
├──────────────────────────────────────────────────────┤
│  DEMOGRAPHICS          │  PSYCHOGRAPHICS             │
│  Age: 30-38            │  Values: efficiency, data   │
│  Income: $120-160K     │  Personality: analytical,   │
│  Education: BS/MBA     │    organized, collaborative │
│  Location: Urban US    │  Interests: productivity,   │
│  Role: Product/PM      │    leadership, AI tools     │
├──────────────────────────────────────────────────────┤
│  GOALS                 │  PAIN POINTS                │
│  ? Ship features       │  ? Too many meetings        │
│  faster                │  ? Manual reporting (15     │
│  ? Data-driven         │    hrs/week)                │
│  decisions             │  ? Stakeholder alignment    │
│  ? Team alignment      │    is slow                  │
│  ? Career growth to    │  ? Tool sprawl (8+ apps)   │
│    Director            │  ? No single source of      │
│                        │    truth                    │
├──────────────────────────────────────────────────────┤
│  CHANNELS              │  BUYING TRIGGERS            │
│  ? LinkedIn (daily)    │  ? Peer recommendation      │
│  ? Product Hunt        │  ? Free trial experience    │
│  ? Podcasts (commute)  │  ? Integration with Jira    │
│  ? Lenny's Newsletter  │  ? Team plan pricing        │
│  ? T@witter/X           │  ? ROI calculator           │
└──────────────────────────────────────────────────────┘

Building a Persona Step-by-Step

Step 1: Research

Start with data, not assumptions.

# Market demographics
infsh app run tavily/search-assistant --input '{
  "query": "product manager salary demographics 2024 survey report"
}'

# Pain points and challenges
infsh app run exa/search --input '{
  "query": "biggest challenges facing product managers SaaS companies"
}'

# Tool usage patterns
infsh app run tavily/search-assistant --input '{
  "query": "most popular tools product managers use 2024 survey"
}'

# Content consumption habits
infsh app run exa/answer --input '{
  "question": "Where do product managers get their industry news and professional development?"
}'

Step 2: Demographics

Use ranges, not exact values. Personas represent a segment, not one person.

Field Format Example
Age range X-Y 30-38
Income range $X-$Y $120,000-$160,000
Education Common degrees BS Computer Science, MBA
Location Region/type Urban US, major tech hubs
Job title Role level Senior PM, Product Lead
Company size Range 50-500 employees
Industry Sector B2B SaaS

Step 3: Psychographics

What they think, value, and believe.

Category Questions to Answer
Values What matters most to them professionally?
Attitudes How do they feel about their industry's direction?
Motivations What drives them at work?
Personality Analytical vs intuitive? Leader vs collaborator?
Interests What do they read/watch/listen to professionally?
Lifestyle Work-life balance preference? Remote/hybrid/office?

Step 4: Goals

What they're trying to achieve (both professional and personal).

Professional:
- Ship features faster with fewer meetings
- Make data-driven decisions (not gut feelings)
- Get promoted to Director of Product within 2 years
- Build a more autonomous product team

Personal:
- Leave work by 6pm more often
- Be seen as a strategic leader, not a ticket manager
- Stay current with industry trends without information overload

Step 5: Pain Points

Quantify whenever possible. Vague pain = vague persona.

? "Has trouble with reporting"
? "Spends 15 hours per week creating manual reports for 4 different stakeholders"

? "Too many tools"
? "Uses 8 different tools daily (Jira, Slack, Notion, Figma, Analytics, Sheets, Docs, Email) with no unified view"

? "Meetings are a problem"
? "Averages 6 hours of meetings per day, leaving only 2 hours for deep work"

Step 6: Jobs-to-be-Done (JTBD)

Three types of jobs:

Job Type Description Example
Functional The task they need to accomplish "Prioritize the product backlog based on customer impact data"
Emotional How they want to feel "Feel confident presenting to the exec team"
Social How they want to be perceived "Be seen as the person who makes data-driven decisions"

Step 7: Buying Process

Stage Behavior
Awareness Reads blog posts, sees peer recommendations on LinkedIn
Consideration Compares 3-4 tools, reads G2/Capterra reviews, asks in Slack communities
Decision Requests demo, needs IT/security approval, evaluates team pricing
Influencers Engineering lead, VP of Product, CFO (for budget)
Objections "Will my team actually adopt it?", "Does it integrate with Jira?"
Trigger event New quarter with aggressive goals, new VP demanding better reporting

Step 8: Generate Avatar

# Match demographics: age, gender, ethnicity, professional context
infsh app run falai/flux-dev-lora --input '{
  "prompt": "professional headshot photograph of a 34-year-old Asian American woman, product manager, warm confident smile, modern tech office background, natural lighting, wearing smart casual blouse, realistic portrait photography, sharp focus",
  "width": 1024,
  "height": 1024
}'

Avatar tips:

  • Match the age range, ethnicity representation, and professional context
  • Use "professional headshot photograph" for realistic results
  • Friendly, approachable expression (not stock-photo-stiff)
  • Background suggests their work environment
  • Business casual or industry-appropriate attire

The Anti-Persona

Equally important: who is NOT your customer.

ANTI-PERSONA: "Enterprise Earl"
- CTO at a 5,000+ person enterprise
- Needs SOC 2, HIPAA, on-premise deployment
- 18-month procurement cycles
- Wants white-glove onboarding and dedicated CSM
- WHY NOT: Our product is self-serve SaaS for SMB/mid-market.
  Enterprise needs would require 2+ years of product investment.

Anti-personas prevent wasted effort on customers you can't serve.

Multiple Personas

Most products have 2-4 personas. More than 4 = too many to serve well.

Priority Persona Role
Primary The main user and buyer Who you optimize for
Secondary Influences the buying decision Who you need to convince
Tertiary Uses the product occasionally Who you support, not target

Validation

Personas based on assumptions are fiction. Validate with:

Method What You Learn
Customer interviews (5-10) Real language, real pain points
Support ticket analysis Actual problems, not assumed ones
Analytics data Actual behavior, not reported behavior
Survey (50+ responses) Quantified patterns across segments
Sales call recordings Objections, buying triggers, language

Common Mistakes

Mistake Problem Fix
Based on assumptions Fiction, not research Start with data
Too many personas (6+) Can't serve everyone well Max 3-4
Vague pain points Not actionable Quantify everything
Demographics only Misses motivations and behavior Add psychographics, JTBD
Never updated Becomes outdated Review quarterly
No anti-persona Wasted effort on wrong customers Define who you're NOT for
Single persona for all Different users have different needs Primary/secondary/tertiary
npx skills add inference-sh/skills@web-search
npx skills add inference-sh/skills@ai-image-generation
npx skills add inference-sh/skills@prompt-engineering

Browse all apps: infsh app list