MCPInstall

ideal-customer-profile

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.

Installs
3K
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

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

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads ideal-customer-profile automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

FAQ

What does the ideal-customer-profile skill do?

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.

How do I install ideal-customer-profile?

Run npx skills add https://github.com/phuryn/pm-skills --skill ideal-customer-profile in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ideal-customer-profile/ (personal) or .claude/skills/ideal-customer-profile/ (project).

Which AI agents can use ideal-customer-profile?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is ideal-customer-profile safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains ideal-customer-profile?

It is published by phuryn in phuryn/pm-skills. It has 2,989 recorded installs.

More from phuryn/pm-skills

View all →

create-prd

phuryn/pm-skills

Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

pre-mortem

phuryn/pm-skills

Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.

Marketing & SEO10.2K installs

Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.

outcome-roadmap

phuryn/pm-skills

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

Business & Finance9.9K installs

strategy-red-team

phuryn/pm-skills

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

Testing & QA9.3K installs

competitor-analysis

phuryn/pm-skills

Analyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.

Popular productivity & automation skills

View category →

agent-browser

vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

OfficialProductivity & Automation1.3M installs

lark-doc

open.feishu.cn

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。

lark-base

open.feishu.cn

飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。

lark-drive

open.feishu.cn

飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。

lark-shared

open.feishu.cn

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.

lark-im

open.feishu.cn

飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。