ideal-customer-profile
Skill2 starsChanged 3 months agoMITView on GitHub
Identify the Ideal Customer Profile (ICP) from research data with demographics, behaviors, JTBD, and needs. Use when defining your ICP, analyzing PMF survey data, or understanding who your best customers are.
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
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
- Distinctive: line 116
Before state (current situation and frustrations)
- Distinctive: line 125
Use $ARGUMENTS to pass:
- Distinctive: line 150
Use quantitative and qualitative data together
- Distinctive: line 152
Look for non-obvious demographic patterns (outliers can be high-value)
- Distinctive: line 155
Use ICP to evaluate all new sales opportunities
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ideal Customer Profile
Overview
Identify your Ideal Customer Profile (ICP) from research and survey data. This skill synthesizes customer research to define the customer most likely to find value, retain, and expand with your product.
When to Use
- Defining ICP from product-market fit survey data
- Targeting high-value customer segments
- Analyzing customer success and expansion patterns
- Prioritizing sales and marketing efforts
- Evaluating new customer opportunities for fit
- Refining target market definition
ICP Framework Components
Demographics
Who are they from a firmographic and personal perspective?
- Company size (employees, revenue)
- Industry or vertical
- Geographic location
- Job title and department
- Years of experience in role
- Education and background
- Organizational structure and reporting
Behaviors
How do they work and make decisions?
- How they discover and evaluate solutions
- Buying process and decision-making timeline
- Technical literacy and product adoption speed
- Collaboration style (solo decision vs committee)
- Change management and adoption style
- Tool switching frequency
- Community involvement and peer influence
Jobs to Be Done (JTBD)
What are they trying to accomplish?
- Primary job/goal they're trying to achieve
- Secondary jobs that support the primary job
- Emotional jobs (how they want to feel)
- Social jobs (status and perception)
- Jobs they avoid or want to eliminate
- Frequency and importance of each job
- Success metrics for completing job
Needs and Pain Points
What problems does your product solve?
- Specific pain points they experience
- Current workarounds and limitations
- Impact on productivity or outcomes
- Cost or time burden of the problem
- Emotional frustration levels
- Barriers to solving the problem
- Available budget to solve
- Competing priorities
How It Works
Step 1: Gather Customer Data
Collect research about actual and potential customers:
- Product-market fit survey responses
- Customer interview transcripts
- Trial or freemium user behavior data
- Customer feedback and support tickets
- Churn analysis and customer lifecycle data
- Win/loss analysis from sales
- Competitor customer analysis
Step 2: Segment by Value
Identify customer cohorts and their value:
- Highest LTV (lifetime value) customers
- Fastest time-to-value customers
- Lowest churn rate customers
- Highest expansion/upsell customers
- Most enthusiastic/engaged customers
- Best reference/case study potential
- Most aligned with product vision
Step 3: Profile Demographics
Extract firmographic patterns:
- Common company sizes (employee count, revenue)
- Industry verticals and sub-verticals
- Geographic concentrations
- Typical department and reporting structure
- Budget holders and budget available
- Company stage (startup, growth, enterprise)
- Company culture indicators
Step 4: Identify Behaviors
Map decision-making and adoption patterns:
- How they discovered your product (channel)
- Evaluation process and timeline
- Key stakeholders in decision
- Obstacles during sales process
- Product adoption speed and breadth
- Team involvement in onboarding
- Frequency of feature usage
- Support and service needs
Step 5: Define JTBD
Articulate what they're trying to accomplish:
- Primary job/goal (functional job)
- Emotional dimensions (how they want to feel)
- Social dimensions (team and stakeholder impact)
- Success metrics (how they measure success)
- Context and constraints (when, where, with whom)
- Competing jobs and priorities
- Importance ranking of various jobs
Step 6: Document Pain Points and Needs
Synthesize specific problem areas:
- Before state (current situation and frustrations)
- Desired after state (ideal future state)
- Gap size and impact quantification
- Emotional dimensions of the problem
- Resource constraints preventing solutions
- Skepticism or hesitations
- Success criteria for solution
Input Format
Use $ARGUMENTS to pass:
- Research data (surveys, interviews, transcripts)
- Customer success/metrics data
- Product usage analytics
- Sales activity and win/loss data
- Existing customer database
- Competitive intelligence
Output
A comprehensive ICP definition including:
- Firmographic profile (company size, industry, location)
- Behavioral profile (buying patterns, adoption style)
- Complete JTBD mapping (functional, emotional, social jobs)
- Top 5-7 pain points and specific needs
- Quantified impact metrics (cost of problem, value of solution)
- Decision-making process and key stakeholders
- Typical customer journey and timeline
- Go-to-market implications and messaging
- Disqualification criteria (who is NOT a good fit)
- High-value segment within ICP (ideal-of-the-ideal)
Framework
Based on Jobs to Be Done theory by Clayton Christensen and customer profiling methodology. Combines behavioral data with motivational insights to define actionable customer profiles.
Tips
- Use quantitative and qualitative data together
- Interview 10+ high-value customers for pattern identification
- Look for non-obvious demographic patterns (outliers can be high-value)
- Define both ideal ICP and acceptable secondary segments
- Revisit ICP quarterly as you gather more customer data
- Use ICP to evaluate all new sales opportunities
- Share ICP across entire organization (marketing, sales, product)
- Remember: ICP should drive focus, not exclude all others
Further Reading
Other versions10 projects use a version of this.
Word for word · 7
- skytiger6724/qwen-skills★ 2100% same
- yuusakuri/agent-skills★ 2100% same
- daviszhen/agent-skills★ 1100% same
- miovrag/claude-skills★ 1100% same
- xeroc/skills★ 1100% same
- maeng777/claude-skills★ 0100% same
- vijaysuperpositionist/skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 3
- NadavShanun-design/opengtm★ 4same name
- burnoutscript/sales-skills★ 0same name
- Usermuse/em-plugin★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository383 other files it gives its agents.
- 37signals-waySkill
- ab-test-analysisSkill
- advisor-orchestrator-workerSkill
- ai-ml-engineeringSkill
- algorithmic-artSkill
- analyze-feature-requestsSkill
- animation-vocabularySkill
- apple-designSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- improve-animationsSkill
- pick-ui-librarySkill
- prototypeSkill
- review-animationsSkill
- ansoff-matrixSkill
- api-and-interface-designSkill
- api-design-best-practicesSkill
- app-store-changelogSkill
- auth-authorizationSkill
- beachhead-segmentSkill
- blue-ocean-strategySkill
- brainstorm-experiments-existingSkill
- brainstorm-experiments-newSkill
- brainstorm-ideas-existingSkill
- brainstorm-ideas-newSkill
- brainstorm-okrsSkill
- brand-guidelinesSkill
- browser-testing-with-devtoolsSkill
- bug-hunt-swarmSkill
- business-modelSkill
- canvas-designSkill
- ci-cd-and-automationSkill
- claude-apiSkill
- clean-architectureSkill
- clean-codeSkill
- cli-creatorSkill
- code-review-and-qualitySkill
- code-review-skillSkill
- code-simplificationSkill
- cohort-analysisSkill
- cold-start-problemSkill
- commit-archaeologistSkill
- competitive-battlecardSkill
- competitor-analysisSkill
- contagiousSkill
- context-engineeringSkill
- continuous-discoverySkill
- architecture-blueprint-generatorSkill
- azure-architecture-autopilotSkill
- cli-masterySkill
- codeqlSkill
- conventional-commitSkill
- create-implementation-planSkill
- csharp-asyncSkill
- diagnoseSkill
- dotnet-best-practicesSkill
- draw-io-diagram-generatorSkill
- git-commitSkill
- github-actions-efficiencySkill
- java-springbootSkill
- The first 60 shown.
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
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.

