skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
victor-shulga/outbound-engine-skills61 installs

persona-builder

Use when asked to build a buyer persona, profile a specific role, or understand how to message a particular decision-maker type

How do I install this agent skill?

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

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is designed to build buyer personas by analyzing LinkedIn data and call transcripts. It requires several third-party tools (MCPs) to scrape external data. The primary security risk is indirect prompt injection, as the agent processes untrusted content from social media and external websites.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

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.

Required tools

Install these before running the skill. It still runs without the ones marked Required, but the result gets noticeably worse: the persona is written from general knowledge of the title instead of the words real people in that role use.

ToolUsed forRequired?Without it
AI Ark, Icypeas or MoltSets (MCP)finding 5–10 people with this title at ICP companiesRequiredyou supply the profiles by hand
Apifyreading their LinkedIn profiles, posts and activity for language patternsRequiredpower phrases and tone are generic, not taken from the persona
Web search or Firecrawl (MCP)job descriptions for the role: what success looks likeRecommendedprimary KPI is inferred from the title
Call recorder transcriptshow this role talks about the problem on real callsRecommendedpains and objections stay hypotheses

Inputs to provide:

  • 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

Terms and plain-language output

<!-- glossary:start terms=persona,primary-kpi,power-phrases,decision-maker,hook -->

Rules for every document a client or their team will read (review, roast, canvas, offer cards, instruction):

  1. Open with «Словник цього документа»: only the terms that actually appear in it, at most 10, each as «термін: що це простими словами». Like the definitions section of a contract.
  2. No internal codes or letter scales in the text (A/B/C, D L T E, BLEND numbers without words, Own/Shared/Generic, Z1.4, GATE 2.5, T1–T6). Write the meaning instead: «є цифра з клієнтом», not «A».
  3. Use the plain form from the table below. English stays only for tool names and for copy that ships in English (promises, hooks, subject lines). If the document is in another language, translate the plain form, never the internal term.
  4. Do not score what cannot exist yet. A block that depends on work not done (signal catalog, case studies, a previous step) gets «пропущено: спершу потрібно <що саме>», not a score.
  5. Every section of a review opens with one concrete action («до наступного дзвінка: …»), then at most five lines of why. No paragraph that only restates the framework.
Internal term (this skill)Write for the readerWhat it means
persona, persona documentпортрет покупцяопис типової людини, що купує: посада, задачі, болі, заперечення, де її шукати; будуємо лише з реальних даних.
Primary KPIголовний показник посадиЦифра, за якою цю людину оцінює керівництво; з неї варто починати розмову.
power phrases / red flag phrasesслова, що чіпляють · слова, після яких перестають читатиМова самої посади, яку беремо в лист, і шаблонні фрази продавців, яких уникаємо.
decision makerОПР (особа, що приймає рішення)той, хто підписує: власник, операційний директор, керівник напряму
hook, cold hookгачокперший рядок листа, через який людина читає далі
<!-- glossary:end -->

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

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/victor-shulga/outbound-engine-skills/persona-builder">View persona-builder on skillZs</a>