Agent skill
persona-mapping
Map buying committee personas within target accounts for ABM and outbound campaigns.
Filed under Positioning and messaging.
From Frontal-so/outbound-skills · 73 skills · 4 · pushed 2026-07-14
What it does when it runs
Map buying committee personas within target accounts for ABM and outbound campaigns. Use when the user asks about persona mapping, buying committee identification, persona-based messaging, JTBD mapping, champion vs economic buyer targeting, persona prioritization, or campaign naming for persona tracking. Triggers on "persona mapping", "buying committee", "champion", "economic buyer", "technical evaluator", "persona", "JTBD", "jobs to be done", "who to target at account", "persona messaging", "persona budget allocation", "campaign naming convention". Do NOT use for general ICP definition (use define-icp) or cold email writing (use cold-email skill).
Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- frontal.so
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/Frontal-so/outbound-skills.git /tmp/outbound-skills git -C /tmp/outbound-skills sparse-checkout set "master-skills/list-building/.claude/skills/persona-mapping" mkdir -p ~/.claude/skills/persona-mapping cp -R "/tmp/outbound-skills/master-skills/list-building/.claude/skills/persona-mapping/." ~/.claude/skills/persona-mapping/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from Frontal-so/outbound-skills/blob/27cd847be5ce7e9b749b1d672cbfb29935d911db/master-skills/list-building/.claude/skills/persona-mapping/SKILL.md, which is licensed MIT (repository). 315 words, 8 headings.
Persona Mapping
You help users identify, segment, and target personas within accounts — mapping who to reach, what they care about, and how messaging differs.
Reference
Read {SKILL_BASE}/resources/abm/persona-mapping-framework.md for the complete framework.
Buying Committee Roles
| Role | Function | Budget Priority |
|---|---|---|
| Champion | Internal advocate who drives evaluation | 40-50% |
| Economic Buyer | Signs the check, cares about ROI | 20-30% |
| End User | Daily user, cares about UX/workflow | 15-20% |
| Technical Evaluator | Assesses integration, security, compliance | 5-10% |
| Blocker/Gatekeeper | Can veto but rarely initiates | Monitor only |
Persona Attributes to Capture
For each persona, define:
- Title patterns and seniority
- Function/department
- Jobs-to-be-done (JTBD)
- Pain points
- Success metrics
- Content preferences
- Buying role
LinkedIn Targeting Approaches
- Approach 1: Contact list upload — precise but expensive, 30-70% match rate
- Approach 2 (recommended): Company list + native LinkedIn filters — cheaper, 95-100% match rate
Campaign Naming Convention
[Campaign Name] - [Persona] - [Ad Type] - [JTBD/Intent] - [ABM Stage]
Example: Analytics-CMO-SingleImage-Attribution-Aware
Messaging Matrix
Each persona needs:
- Different JTBDs highlighted
- Different pain points addressed
- Stage-appropriate content (awareness vs consideration)
- Role-appropriate CTA (champion gets demo, end user gets trial)
Examples
Example 1: "Who should I target at my ABM accounts?" → Read persona-mapping-framework.md. Map buying committee: start with Champions (40-50% budget), then Economic Buyers (20-30%).
Example 2: "How do I tailor messaging for different personas?" → Build messaging matrix: different JTBD, pain points, and CTAs per persona. Champion gets ROI narrative, End User gets ease-of-use.
Example 3: "How should I name my campaigns for persona tracking?" → Use naming convention: [Campaign]-[Persona]-[AdType]-[JTBD]-[Stage]. Enables intent detection from campaign engagement data.
Part of Frontal — free, open GTM skills for your AI agent. Browse the library →
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- persona-classification by louisblythe · 136
- customer-journey-mapping by thatrebeccarae · 119
- apollo-filter-mapping by impecablemee · 66
- persona-development by kenny589 · 63
- trigger-mapping by kenny589 · 63
- icp-persona by realjaymes · 55
- buyer-persona by jbalbu01 · 14
- persona-based-discovery by zime-ai · 14
Need help setting it up?
This page tells you what persona-mapping does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.