Token导航 LogoToken导航TokenDH.com
研究检索只读clawhub未标认证来源可访问clear审计通过

customer-persona-copy-map客户角色复制图

Agent Skill

customer-persona-copy-map 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,548

周安装

62

GitHub Stars

1

下载量

501
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:customer-persona-copy-map(客户角色复制图)
来源仓库:https://github.com/harrylabsj/customer-persona-copy-map
安装命令:
openclaw skills install customer-persona-copy-map
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install customer-persona-copy-map

简介

将受众研究转化为详细的文案矩阵,关联客户角色与定制化营销语言。

  • 适合市场文案策划、广告素材生成和用户沟通策略制定。
  • 自动匹配痛点、利益点和行动号召话术,并提供证据支持。
  • 需用户提供真实客户画像资料,避免虚构受众特征。
  • customer-persona-copy-map 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Customer Persona Copy Map

Purpose

This skill turns audience research and customer signals into a practical copy matrix that maps different personas to their specific pain points, motivations, objections, preferred benefits, and CTA language. Instead of one-size-fits-all copy, it helps teams segment messaging across product pages, ad creative, email flows, and landing pages — all while clearly labeling what's evidence-based vs. assumed.

Triggers

  • "Map copy to different customer personas"
  • "Create persona-based messaging for my product"
  • "Build a copy matrix for audience segments"
  • "Segment my product messaging by buyer type"
  • "Write persona-specific ad copy"
  • "Create messaging for different customer types"

Workflow

  1. Audience signal collection — Gather known customer segments, demographic/behavioral signals, purchase data patterns (if available), review themes by customer type, support ticket themes, and any existing persona research.
  2. Evidence vs. assumption separation — For each persona, clearly separate: what data supports this segment (reviews, sales data, survey results) vs. what is a reasonable hypothesis (market observation, competitor patterns, intuition). Assumptions must be labeled.
  3. Persona card creation — For each distinct persona, create a card with: name/descriptor, primary need/job-to-be-done, dominant purchase barrier, emotional driver, trust requirement, and preferred channel.
  4. Pain-benefit-message matrix — Create a cross-reference matrix: persona → top pain points → product benefits that address them → message framing → CTA language → best channel.
  5. Copy snippet drafting — Write persona-specific copy snippets: above-the-fold headline, key benefit statement, objection pre-handler, and CTA. Each snippet should feel natural for that persona.
  6. Channel recommendation — For each persona-message pair, recommend the best channel(s) and format (e.g., "gift-buyer persona → Instagram Story with gift-guide angle").

Prompt Templates

1. Persona Copy Matrix Builder (persona_matrix)

Purpose: Build a complete persona-to-copy matrix from audience data.

Input:

  • ${product_name} — Product name
  • ${product_category} — Product category
  • ${personas} — List of customer persona descriptions (2–5 personas)
  • ${product_benefits} — Key product benefits
  • ${channels} — Available marketing channels
  • ${evidence_sources} — (Optional) data sources supporting persona definitions

Output: Complete matrix with persona cards, pain/benefit/message map, copy snippets, and channel recommendations.

2. Persona Expander (persona_expand)

Purpose: Expand a thin persona description into a full messaging profile.

Input:

  • ${persona_name} — Persona name or descriptor
  • ${known_traits} — What's known about this persona
  • ${product_context} — What this product does for them

Output: Expanded persona card with messaging angles, objections, and copy snippet drafts.

3. Message Adapter (message_adapt)

Purpose: Adapt one core message to multiple persona framings.

Input:

  • ${core_message} — The central product message
  • ${personas} — List of personas with key motivations
  • ${channels} — Target channels for adaptation

Output: Persona-specific message adaptations with rationale for changes.

4. Assumption Auditor (assumption_audit)

Purpose: Audit a persona set for untested assumptions that could lead to wasted spend.

Input:

  • ${persona_set} — Complete persona definitions with messaging
  • ${evidence_available} — What data actually supports each persona

Output: Each persona scored by evidence strength (High/Medium/Low), with assumptions highlighted and test recommendations for low-evidence personas.

Output Format

## Persona Copy Map: [Product Name]
**Category:** [Category] | **Personas:** [N personas]

### Persona Cards

**Persona 1: [Name/Descriptor]**
- **Primary Need:** [Job-to-be-done]
- **Dominant Barrier:** [What keeps them from buying]
- **Emotional Driver:** [What feeling motivates them]
- **Trust Requirement:** [What proof they need]
- **Preferred Channel:** [Where they're most reachable]
- **Evidence Strength:** [High/Medium/Low] — [what data supports this]

**Persona 2: [...]**
...

### Pain-Benefit-Message Matrix

| Persona | Top Pain | Product Benefit | Message Frame | CTA Language | Best Channel |
|---|---|---|---|---|---|
| Persona 1 | [Pain] | [Benefit] | [How to frame] | "[CTA]" | [Channel] |
| Persona 2 | [Pain] | [Benefit] | [How to frame] | "[CTA]" | [Channel] |
| ... | ... | ... | ... | ... | ... |

### Copy Snippets

**For [Persona 1]:**
- 🎯 Headline: "[Above-the-fold headline]"
- 💡 Benefit: "[Key benefit statement]"
- 🛡️ Objection handler: "[Pre-handle common objection]"
- 🚀 CTA: "[Call to action]"

**For [Persona 2]:**
...

### Channel Recommendations
- **[Channel]:** Best for personas [X, Y] — format: [suggestion]
- **[Channel]:** Best for persona [Z] — format: [suggestion]

### Assumption Audit
- ✅ Persona 1: [Evidence strength] — supported by [sources]
- ⚠️ Persona 2: Medium evidence — [assumptions] need validation via [test idea]
- ❓ Persona 3: Low evidence — consider deprioritizing until [validation method]

Safety Rules

  • ALWAYS clearly label assumptions vs. evidence — unvalidated personas can waste budget and alienate real customers
  • NEVER stereotype based on protected characteristics (age, gender, race, religion, disability, sexual orientation) when the data doesn't support it
  • NEVER create personas for sensitive categories (health conditions, financial distress, personal crises) without extreme care and explicit disclosure of limitations
  • ALWAYS avoid manipulative messaging that exploits persona vulnerabilities (e.g., insecurity-based marketing to teens, fear-based messaging to elderly)
  • NEVER present assumed personas as "proven by AI" — clearly state the evidence basis for every segment

Examples

Example 1: Skincare Serum (3 Personas)

Input: Product="Vitamin C Brightening Serum", Personas="(1) Skincare Beginner — wants results without complexity, (2) Ingredient Nerd — researches every component, (3) Gift Buyer — buying for someone else, wants safe choice"

Output: Matrix showing: Beginner → pain="too many choices, don't know what works" → message="One serum, proven ingredients, simple routine" → CTA="Start your 2-step routine" → channel=Instagram/TikTok. Ingredient Nerd → pain="skeptical of marketing claims" → message="15% L-AA + E + ferulic, airless pump, dermatologist-tested — here's the data" → CTA="See the full ingredient breakdown" → channel=blog/email. Gift Buyer → pain="will they like it? will it work for their skin?" → message="Universally loved, fragrance-free, suitable for most skin types, beautiful packaging" → CTA="Gift the glow" → channel=Facebook/Instagram.

Example 2: Kitchen Gadget (2 Personas)

Input: Product="Air Fryer Liners", Personas="(1) Convenience Cook — wants faster cleanup, (2) Eco-Conscious Cook — wants to reduce waste (aluminum foil/paper)"

Output: Matrix: Convenience → pain="air fryer cleanup is annoying" → message="Cook, eat, toss the liner — no scrubbing" → CTA="Make cleanup optional" → channel=TikTok. Eco-Conscious → pain="using disposable foil/paper feels wasteful" → message="Reusable silicone liners replace hundreds of foil sheets" → CTA="Cook cleaner, waste less" → channel=Instagram/blog. Assumption audit flags that "Eco-Conscious" is partially assumed — recommended survey validation.

Related Skills

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

90.3%
按下载量换算452

安全审计

VirusTotal

未展示

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills