메뉴
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".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Generate a targeted lead list with Apollo — filter by title, company size, industry, tech stack — and export to CSV/HubSpot/Sheets. Use when the user says "build me a prospect list", "find 100 VPs of X", or "source leads for the campaign".
Build a competitive battlecard — when to land-grab vs. when to walk away, key wedges, objection handling, landmines to set. Use on "build a battlecard against <competitor>", "how do we beat <X>", or "compete review".
Check Google Calendar availability and book meetings — find slots across time zones, send invites, hold prep time. Use on "find time with X", "book a demo", "check my availability next week".
Write high-response cold emails — short, specific, prospect-centric. Use when the user asks to "write a cold email", "rewrite my outbound", or "this email is getting no replies". Produces 3 variants with rationale.
Run a cold email outreach campaign via Gmail. Use when the user wants to send personalized cold emails to a list of prospects, draft outbound sequences, or launch a small outreach batch from a CSV/sheet of leads. Proactively invoke when the user mentions "send cold emails", "outreach campaign", or "blast my leads".
Prep for a discovery call — research the account, the attendee, set hypothesis for their pains, write the question stack, define success. Use on "prep for my discovery call", "research this account before tomorrow", or "what should I ask <prospect>?".
| name | persona-builder |
| description | 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". |
| allowed-tools | ["Read","Write","AskUserQuestion"] |
Personas are only useful if they change decisions. Build them from interview evidence, not archetypes.
./personas/<role>.md.# <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.