ideal-customer-profile

phuryn/pm-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/phuryn/pm-skills --skill ideal-customer-profile
0 commentsdiscussion
summary

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.

skill.md

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

how to use ideal-customer-profile

How to use ideal-customer-profile on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add ideal-customer-profile
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/phuryn/pm-skills --skill ideal-customer-profile

The skills CLI fetches ideal-customer-profile from GitHub repository phuryn/pm-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/ideal-customer-profile

Reload or restart Cursor to activate ideal-customer-profile. Access the skill through slash commands (e.g., /ideal-customer-profile) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.656 reviews
  • Dev Khan· Dec 28, 2024

    Keeps context tight: ideal-customer-profile is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Henry Thompson· Dec 20, 2024

    I recommend ideal-customer-profile for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Alexander Park· Dec 16, 2024

    ideal-customer-profile is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Hana Chawla· Dec 12, 2024

    Solid pick for teams standardizing on skills: ideal-customer-profile is focused, and the summary matches what you get after install.

  • Henry Garcia· Dec 8, 2024

    ideal-customer-profile has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Noah Martinez· Nov 27, 2024

    ideal-customer-profile fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Chinedu Sanchez· Nov 19, 2024

    Keeps context tight: ideal-customer-profile is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Chinedu Gill· Nov 11, 2024

    ideal-customer-profile reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Charlotte Verma· Nov 3, 2024

    We added ideal-customer-profile from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Chinedu Gupta· Oct 22, 2024

    ideal-customer-profile fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

showing 1-10 of 56

1 / 6