persona-mapping

persona-mapping is a skill for Claude Code from Frontal-so/outbound-skills. It costs 138 tokens per session (700 once invoked), scanned A, original, MIT.

A method for mapping the people involved in a company purchase. It distinguishes roles such as the internal advocate, budget approver, daily user, technical reviewer, and blocker.

In plain words
What is it for?
Use it to identify buying-committee members, record their responsibilities and priorities, choose who to contact, and adapt messages for each role.
Why use it?
It prevents campaigns from treating everyone at a target company the same when each person has different concerns and influence.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to identify buying-committee members, record their responsibilities and priorities, choose who to contact, and adapt messages for each role.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/frontal-so/outbound-skills/persona-mapping
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Frontal-so/outbound-skills --skill persona-mapping
Clone the repo
git clone --depth 1 https://github.com/Frontal-so/outbound-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for persona-mapping

README.md
[![agentmods](https://agentmods.dev/badge/skills/frontal-so/outbound-skills/persona-mapping/github.svg)](https://agentmods.dev/skills/frontal-so/outbound-skills/persona-mapping)
Your own site
<a href="https://agentmods.dev/skills/frontal-so/outbound-skills/persona-mapping"><img src="https://agentmods.dev/badge/skills/frontal-so/outbound-skills/persona-mapping/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for persona-mapping

Your own site · 80×15
<a href="https://agentmods.dev/skills/frontal-so/outbound-skills/persona-mapping"><img src="https://agentmods.dev/badge/skills/frontal-so/outbound-skills/persona-mapping.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 138 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 700 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00138 $0.00700
Opus 5 $0.00069 $0.00350
Sonnet 5 $0.00028 $0.00140
Haiku 4.5 $0.00014 $0.00070

Measured 12d ago against content hash e2472d678a17, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

persona-mapping scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

master-skills/list-building/.claude/skills/persona-mapping/SKILL.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:

  1. Different JTBDs highlighted
  2. Different pain points addressed
  3. Stage-appropriate content (awareness vs consideration)
  4. 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.

Read the full file on GitHub · 69 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 69 lines · 138 tokens per session scan A e2472d678a17

Subscribe to this mod's changes

persona-mapping is a skill published in the GitHub repository Frontal-so/outbound-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 138 tokens to every session and 700 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

audience-icp-filter

Filter an existing audience or lead list against your ICP and split it into ready-to-sequence segments. Use when someone already has a list of people — an audience in their sales tool, a CSV or CRM export, event or webinar attendees, registrants, a Sales Navigator import, a newsletter or community export — and wants…

LaGrowthMachine/gtm-system · 228 tokens

team-performance-dashboard

Generate your Team Performance Dashboard from your La Growth Machine data: a head-of-sales cockpit that ranks each sender (rep) on reply rate, your success event (signups/meetings/deals) and conversion, surfaces hot leads going cold, and turns your best reps' campaigns into a coaching playbook for the rest. Pulls only…

LaGrowthMachine/gtm-system · 235 tokens

weekly-performance-advisor

Generate your Weekly Performance Advisor dashboard from your La Growth Machine data: a two-tab cockpit (To do + Weekly performance) that flags campaigns to fix, sorts replies by urgency, and tracks reply volume week over week. It pulls only YOUR live LGM data, scores each running campaign against baked 3-zone…

LaGrowthMachine/gtm-system · 215 tokens

outreach-icp-finder

Find your PROVEN ideal customer profile from your own outreach data — who actually replies, accepts and shows interest — then find more like them. Reads La Growth Machine via its MCP, or a CSV export from any outreach tool (lemlist, Instantly, Smartlead, HeyReach, Apollo, Waalaxy…). Use when someone asks which job…

LaGrowthMachine/gtm-system · 234 tokens

objection-analyzer

Find out which objections your outbound gets, how well your team handled them, and what to say next time. Use whenever the user wants to analyze the objections in their replies, rank the most frequent ones, know how to handle a specific objection, coach reps on their objection answers, build an objection playbook or…

LaGrowthMachine/gtm-system · 215 tokens

sales-nav-search-builder

Generate a precise LinkedIn Sales Navigator search URL from a natural-language ICP description — for sales prospecting, outbound outreach, lead generation, and B2B targeting. Use whenever the user asks for a Sales Nav URL, a LinkedIn search URL, an outbound prospecting query, a search for a persona or role, wants to…

LaGrowthMachine/gtm-system · 221 tokens