mcpField
P
persona-builder

persona-builder

github.com/victor-shulgaMarketing & growth140 installsUpdated 3d ago
Repository

About persona-builder

A skill for marketing and sales teams to build buyer personas for specific roles. It uses ICP context and available role data to identify goals, pressures, and buying preferences, then turns the findings into writing guidance.

Key features

  1. 01Researches target roles by title
  2. 02Identifies KPIs, pain points, and internal risks
  3. 03Reviews existing tools and buying preferences
  4. 04Turns research into copy guidance

Use cases

  1. 01Creating separate personas for sales roles
  2. 02Adapting marketing copy to job contexts
  3. 03Preparing role context for sales sequences

MCP support

The process uses LinkedIn via MCP to review 5–10 profiles matching the ICP and role.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/victor-shulga/outbound-engine-skills --skill persona-builder

After installing, type/persona-builderin Claude Code to confirm it loaded.

Details

From the project README

Persona Builder

Build a detailed buyer persona for a specific role — what they care about, how they think, what they fear, and how to write to them.

What you need

  • Role title(s) to profile
  • ICP context (company type, size, industry)
  • Any available data: call recordings, LinkedIn profiles, job descriptions for this role

Process

  1. Research the role using LinkedIn via MCP: look at 5–10 profiles matching the ICP for this title
  2. Read their posts and activity for language patterns
  3. Review job descriptions for this role to understand what success looks like for them
  4. Identify:
    • Primary KPI they're measured on
    • Biggest daily frustration
    • What they're trying to prove to leadership
    • What makes them look bad internally
    • What vendors/tools they already use
    • How they prefer to buy (self-serve research vs. demo vs. committee)
  5. Translate all of the above into copy guidance: tone, vocabulary, what to lead with, what to avoid

Output format

Persona: [Title]
ICP context: [Company type / size]

ROLE PROFILE
Primary KPI: [what they're measured on]
Biggest pain: [the thing that keeps them up]
What they want to prove: [internal motivation]
What makes them look bad: [risk/fear driver]
Current tools: [typical stack for this role]
Buying style: [how they prefer to evaluate]

MESSAGING GUIDE
Lead with: [the angle that resonates first]
Avoid: [what sounds like every other vendor]
Tone: [direct and blunt / peer-to-peer / analytical / etc.]
Power phrases: [words/phrases this persona responds to]
Red flag phrases: [words that make them tune out]

EXAMPLE OPENER
"[A first line that would immediately resonate with this persona]"

Notes

  • Build one persona file per role — reuse across all sequence-writer calls
  • Language should come from the persona's own vocabulary, not your product vocabulary
  • "What makes them look bad" is the most important field — fear of failure drives more decisions than hope of gain
  • VP Sales and Head of Sales sound similar but often have completely different concerns — profile them separately

Comments

Markdown supported