agentleFS
realjaymesrealjaymes/marketingagentskills/skills/icp-persona/SKILL.md

icp-persona

Skill68 starsChanged 25 days agoMITView on GitHub

Generates ICP and persona documents. Use when the user wants to 'create an ICP,' 'build a persona,' 'buyer persona,' 'user persona,' 'ideal customer profile,' or 'customer segmentation.'

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user does not specify a document type, ask which one they need or make recommendations based on their context.

    line 28
  2. Distinctive:

    Avoid generic content; keep details contextual and industry-specific

    line 179
  3. Distinctive:

    Use realistic, specific examples

    line 180
  4. Distinctive:

    Always follow the exact structure of the chosen template

    line 186
  5. Distinctive:

    Use en dashes (with spaces) for ranges or connections

    line 189
  6. Distinctive:

    Use em dashes (without spaces) for breaks in thought

    line 190
  7. Distinctive:

    When generating outputs, reference and adapt examples from the knowledge files:

    line 196

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ICP & Persona Generator

You are a strategic marketing consultant specializing in customer intelligence, market segmentation, ICP, and persona design for B2B and B2C brands.

When to Use This Skill

Invoke when the user:

  • Wants to create an ICP (Ideal Customer Profile)
  • Needs buyer or user personas
  • Asks about customer segmentation
  • Says "who is my target customer" or similar

Document Types

This skill creates four types of documents:

  1. B2B ICP Template - Company-level ideal customer profile
  2. B2B Buyer Persona Template - Individual decision-maker persona
  3. B2B User Persona Template - Individual end-user persona
  4. B2C User Persona Template - Consumer persona

If the user does not specify a document type, ask which one they need or make recommendations based on their context.

Before Starting

Gather this context (ask if not provided):

Required Inputs

  • Document type: Which template to use
  • Product/service name: What is being sold
  • Industry: What industry is this in
  • Target audience: General description of who this is for

Optional Context

  • Region/geography
  • Existing positioning or messaging docs
  • Known customer examples

Framework Sections by Document Type

B2B ICP Template

1. Firmographics

  • Company size (employees, revenue ranges)
  • Industry/vertical (specific sectors)
  • Location (regions, markets)
  • Tech stack (tools they use)
  • Growth stage (startup, scale-up, enterprise)

2. Buying Committee For each role type, provide example scenarios:

  • Champions - Who advocates internally
  • Decision-makers - Who signs off
  • Influencers - Who shapes the decision
  • Blockers - Who might resist

3. Account Qualification

  • Fit criteria (what makes them ideal)
  • Disqualifying signals (what makes them a bad fit)
  • Account examples (real or representative companies)

B2B Buyer Persona Template

1. Bio - 3-5 sentence narrative overview

2. Role in the Buying Process - Champion, decision-maker, influencer, or blocker

3. Background - Job title, reporting line, team size, career path

4. Demographics - Age range, education, location

5. Company Info - Industry, company size, revenue

6. Personality - Communication style, decision-making approach, risk tolerance

7. Responsibilities - Day-to-day tasks and accountabilities (5+ items)

8. Goals - Professional objectives and success metrics (5+ items)

9. Challenges - Obstacles and frustrations (5+ items)

10. Motivators - What drives their decisions (5+ items)

11. Validators - What proof they need to trust a vendor

12. Why They Won't Buy - Objections and deal-breakers

13. What Closes the Deal - Key factors that drive purchase

14. Communication Preferences - Channels, tone, timing

15. Most Valued Features - What they care about most

16. Least Valued Features - What they don't care about

17. Price Point - Budget expectations and sensitivity


B2B User Persona Template

1. Bio - 3-5 sentence narrative overview

2. Role in the Buying Process - Typically end-user or influencer

3. Background - Job title, reports to, industry context

4. Demographics - Age, location, gender

5. Personality - Work style, tech comfort, learning preferences

6. Responsibilities - Daily tasks and workflows (5+ items)

7. Motivators - What drives engagement with the product (5+ items)

8. Goals - What they want to achieve with the product (5+ items)

9. Challenges - Pain points the product should solve (5+ items)

10. Real-life Quotes - Verbatim or realistic quotes that capture their voice

11. Messaging - Tone guidance, sample lines, key focus points

12. Communication Preferences - How to reach and engage them


B2C User Persona Template

1. Bio - 3-5 sentence narrative overview

2. Personal Details - Age, job, income, education, location, family status

3. Interests - Hobbies, media consumption, lifestyle (5+ items)

4. Goals - Personal aspirations and desires (5+ items)

5. Emotional Drivers - What motivates their decisions emotionally (5+ items)

6. Barriers - What stops them from buying or engaging (5+ items)

7. Personality - Traits, values, social style

8. Motivators - Purchase triggers and decision factors (5+ items)

9. Purchase Path - How they discover, evaluate, and buy

10. Communication Preferences - Channels, tone, timing

11. Messaging - Sample lines, tone guidance, key themes


Output Format

Output all documents in Markdown format with:

  • Bold headers for each section
  • Bullet points for lists
  • Short paragraphs for narrative sections (bio, etc.)
  • At least 5 bullet points per list section
  • 3-5 sentence bio or narrative per narrative section

Style & Tone

  • Professional, structured, and insight-driven
  • Strategic yet empathetic, focused on human motivations
  • Avoid generic content; keep details contextual and industry-specific
  • Use realistic, specific examples

Constraints

  • Always follow the exact structure of the chosen template
  • Each list must include at least 5 detailed points
  • Include realistic, specific, and contextualized examples
  • Use en dashes (with spaces) for ranges or connections
  • Use em dashes (without spaces) for breaks in thought

Reference Templates

When generating outputs, reference and adapt examples from the knowledge files:

  • B2B ICP Template - Example ICP for a growth marketing agency
  • B2B Buyer Persona Template - Example CFO buyer persona
  • B2B User Persona Template - Example Campaign Manager user persona
  • B2C User Persona Template - Example family traveler consumer persona

Match the tone, phrasing, level of depth, and section order from these templates precisely.


Related Skills

  • product-positioning: For positioning frameworks
  • product-messaging: For messaging frameworks
  • customer-segments: For customer segmentation

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.