composio-community/awesome-gtm-skills/persona-builder

Claude Code and agent skill by composio-community/awesome-gtm-skills

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Build buyer personas grounded in real customer interviews — goals, pains, JTBD, information diet, objections. Use on "build personas for <product>", "who is <role> really?", or "tighten my buyer persona".

Install

npx vskill@latest install composio-community/awesome-gtm-skills/persona-builder

SKILL.md

Buyer Persona Builder

Personas are only useful if they change decisions. Build them from interview evidence, not archetypes.

Workflow

  1. Name the role (e.g., "VP Platform Engineering at 200-800 person SaaS"). Resist building multiple personas before you've validated one.
  2. Source evidence. Ask the user for: 5+ customer interviews, sales call recordings/notes, support tickets from this role, public content they've written/read.
  3. If they can't supply evidence, do not invent. Either (a) go interview 5 people, or (b) build a hypothesis persona clearly marked as such.
  4. Extract patterns, not averages. A pattern appears in ≥ 3/5 interviews.
  5. Write the persona to ./personas/<role>.md.

Persona template

# <Role> at <company profile>  ·  Source: <n> interviews + <m> calls
 
## One-line
A <title> responsible for <scope> who gets promoted/fired on <top 1-2 metrics>.
 
## Jobs to be done (ranked by frequency × importance)
1. <JTBD> — evidence: "<verbatim quote>"
2. …
3. …
 
## What they're measured on
- <KPI 1>
- <KPI 2>
 
## Pains (ranked)
1. <Pain> — frequency: <n>/<m> interviews — verbatim: "<quote>"
2. …
 
## Current workarounds
- How they solve it today: <tools + process>
- What they dislike about it: …
 
## Buying behavior
- Who they involve: <roles>
- How they evaluate: <criteria + process>
- How long it takes: <weeks/months>
- What typically kills a deal: <common objection>
 
## Information diet
- Communities: <Slack groups, subreddits, Discord>
- Newsletters/podcasts: …
- Who they trust: <named peers or thought leaders>
- Who they ignore: <anti-pattern sources>
 
## Language (use these words, avoid those)
Use: "<their phrase>"
Avoid: "<industry jargon they don't use>"
 
## Best channels to reach
Warm: <warm-intro patterns that actually work>
Cold: <which cold channel has pulled response>
Don't bother: <channel with 0 response rate>
 
## Not-this-persona (disqualifiers)
If the prospect <X>, they're a different persona — route to <Y> or disqualify.

Guardrails

  • If two "personas" have the same JTBD and buying process, collapse them into one.
  • No demographic fluff (hobbies, car, weekend routine) — only include if it changes a GTM decision.
  • Mark claims with evidence counts. Unsourced claims should be removed, not softened.
  • Refresh every 6 months. Roles drift; tech stacks change; personas decay.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

See the full security report

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

See evaluation results

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/composio-community/awesome-gtm-skills/persona-builder/badge)](https://verified-skill.com/skills/composio-community/awesome-gtm-skills/persona-builder)

Something wrong with this skill or its page? Tell us.