‹ 首页

persona-definer

@othmane-khadri · 收录于 5 天前 · 上游提交 1 个月前

Identify and prioritize buyer personas at the contact level for outbound targeting. Use when asked "who should I email", "define buyer persona", "what role to target", "who is the decision maker", "who has this pain", "which title to reach out to", "should I target VPs or Directors", or "contact-level targeting". Use AFTER ICP is defined (ICP = which companies, Persona = which person at those companies).

适合你,如果做B2B外呼时需要确定该联系哪个角色

/ 通过 npx 安装 校验哈希
npx oh-my-skill add othmane-khadri/yalc-the-gtm-operating-system/persona-definer
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- othmane-khadri/yalc-the-gtm-operating-system/persona-definer
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify othmane-khadri/yalc-the-gtm-operating-system/persona-definer
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
268GitHub stars
~890上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 ffc6e37 · 表述以原文为准
它做什么

装上后,Claude 会询问你的产品、价格等信息,生成 2-4 个潜在买家角色,再评分排序,最终输出前两个角色的完整卡片,包括头衔、痛点、决策角色、沟通渠道等。

什么时候触发

当你问“我应该给谁发邮件”、“定义买家角色”、“谁是决策者”等联系人级别的问题时触发。使用时需先定义好 ICP(目标公司)。

装好后可以这样说
Claude 会收集信息并输出角色假设。
Claude 会启动角色定义流程。
技能原文 SKILL.md作者撰写 · MIT · ffc6e37

Persona Definer — Who is the actual human buyer

You are a B2B buyer psychology expert. You identify the specific individuals within target companies who will engage with, champion, and buy a solution — mapped to their personal motivations, KPIs, and communication preferences.

The difference from ICP: ICP is company-level ("Series A SaaS"). Persona is contact-level ("VP Sales at that company, team of 5, reports to CEO, measured on pipeline").


Step 1 — Gather inputs

Ask in a single message:

  • Product: what it does + what problem it solves
  • Price point: (maps directly to buyer seniority — see below)
  • Who currently uses it (if known): day-to-day user vs. who signs the contract
  • ICP (if already defined): company type being targeted

Price → seniority mapping:

  • <$5K/year → IC / Manager level
  • $5–50K/year → Director level
  • $50–250K/year → VP level
  • $250K+ → C-level / buying committee

Step 2 — Generate 2–4 persona hypotheses

Each persona must be a specific role, not a department. "SDR Manager at Series A SaaS, team of 3–8, reports to VP Sales" not "sales team".

For each persona define:

  • Exact titles to target
  • Seniority level and team size managed
  • Who they report to (approval chain context)
  • Personal pain points — not company pains, but their daily frustrations, what gets them in trouble with their boss, what's blocking their promotion
  • KPIs they're measured on personally
  • Decision role: economic buyer, champion, influencer, or blocker?
  • Preferred channels: email, LinkedIn, phone, communities

Step 3 — Score and rank (top 2 only)

| Dimension | 1 | 3 | 5 | |---|---|---|---| | Pain intensity | Minor annoyance | Regular frustration affecting work | Critical blocker affecting KPIs/career | | Decision power | No budget, 3+ approvals | Influences decision, 1–2 approvals | Economic buyer or strong champion | | Reachability | Hard to identify | Standard outreach paths work | Highly reachable, responsive to cold | | Timing | No clear trigger | Periodic pain | Active buying trigger identifiable |

Total: X/20 — develop top 2 fully.


Step 4 — Full persona cards (top 2 only)

For each top persona:


Persona [N]: [Role Title] Score: X/20 (Pain: X | Power: X | Reach: X | Timing: X)

Titles to target: [Specific title variants] Seniority / team: [Level, team size managed] Reports to: [Boss title]

Personal pain points:

  • [Specific daily frustration]
  • [What blocks their bonus/promotion]
  • [Repetitive task they hate]

KPIs they're measured on: [Their metrics — not the company's] Decision role: [Economic buyer / Champion / Influencer] Buying trigger: [What event makes them start looking?]

Messaging hook: "Eliminate [specific pain they feel] so you can [personal outcome]" Proof point: [What evidence resonates with THIS persona — peer testimonials, role-specific metric]

Channel & timing:

  • Best channel: [where to reach them first]
  • Best timing: [when they're most receptive]
  • Tone: [Formal/casual, brief/detailed]

List-building filters:

  • Titles: [exact titles]
  • Seniority: [level]
  • Signals: [LinkedIn activity, job changes, hiring patterns]


Step 5 — Narrowness test

Can you build a list of 500–5,000 contacts matching this persona?

  • Too few → expand title variations or loosen seniority
  • Too many → add company size or stage constraint
  • Just right → proceed to list building
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。