icp-builder
Skill13 starsChanged 22 days agoMITView on GitHub
Use this skill when you need to define or sharpen an ideal customer profile (ICP) for B2B sales: starting outbound, the reply rate is low, the pipeline is full of bad-fit deals, or leadership asks who we should really sell to. Analyses closed-won and closed-lost deals, finds the firmographic, technographic and situational traits that predict a win, and produces a one-page ICP with must-haves, nice-to-haves, disqualifiers and list-building filters. Works for founders with five customers and for teams with hundreds.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- adidacta/pmf-detectivetheir own version, first seen Oct 13, 2026
- NEON-Rutger/B2B-revops-skillstheir own version, first seen Oct 5, 2026
- veneris-io/outbound-skillstheir own version, first seen Sep 7, 2026
- crustdata/skillstheir own version, first seen Sep 4, 2026
- OpenClaudia/openclaudia-skillstheir own version, first seen Jun 11, 2026
Used with
Projects with it also use page-cro, launch-strategy and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
silvainfmSkillpage-cro
When the user wants to optimize, improve, or increase conversions on any marketing page — including homepage, landing pages, pricing pages, feature pages, or blog posts. Also use when the user says "CRO," "conversion rate optimization," "this page isn't converting," "improve conversions," or "why isn't this page working." For signup/registration flows, see signup-flow-cro. For post-signup activation, see onboarding-cro. For forms outside of signup, see form-cro. For popups/modals, see popup-cro.
Also in 3 projects that use this
silvainfmSkilllaunch-strategy
When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.
Also in 3 projects that use this
indranilbanerjeeSkillkeyword-research
Research keywords via the connected data source: intent, gaps. Grouping → keyword-cluster. \"what keywords should we target\"
Also in 3 projects that use this
AnthropicSkillemail-sequence
Design and draft multi-email sequences with full copy, timing, branching logic, exit conditions, and performance benchmarks. Use when building onboarding, lead nurture, re-engagement, win-back, or product launch flows, when you need a complete drip campaign with A/B test suggestions, or when mapping a sequence end-to-end with a flow diagram.
Also in 3 projects that use this
AnthropicSkillcontent-strategy
Analyzes sales data from PayPal and QuickBooks to find top performers and slow movers, layers in seasonality, and produces a prioritized 30-day content brief: what to push, what offers to run, what to hold. Strategic output only — no calendars or assets. Use when the user asks what to post, wants a content plan, asks what's selling, or what to promote this month.
Also in 3 projects that use this
SupabaseSkillcopywriting
Write or audit UI copy (buttons, labels, empty states, error messages, tooltips, form text) anywhere in the monorepo. Load it before shipping or reviewing any user-facing text — including when copy is incidental to the task, like a new feature that adds buttons, toasts, dialogs, or validation messages.
Also in 3 projects that use this
- +1 more from silvainfm
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- OpenClaudia/openclaudia-skills★ 731same name
- NEON-Rutger/B2B-revops-skills★ 58same name
- robertbstillwell/marketing-skills★ 26same name
- adidacta/pmf-detective★ 18same name
- ilya-a11y/growthband-outbound-skills★ 13same name
- crustdata/skills★ 11same name
- guerrilla2799/marketing-skills★ 9same name
- veneris-io/outbound-skills★ 2same name
- oivanfelipe/claude-skills★ 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 repository77 other files it gives its agents.
- AGENTS.mdAGENTS.md
- abm-account-planSkill
- account-research-briefSkill
- account-tieringSkill
- aeo-answer-optimizerSkill
- breakup-emailSkill
- buyer-persona-builderSkill
- buying-committee-mapperSkill
- buying-signal-scoringSkill
- call-coaching-scorecardSkill
- campaign-performance-analyzerSkill
- case-study-writerSkill
- churn-win-backSkill
- closed-lost-reactivationSkill
- cold-call-scriptSkill
- cold-email-sequenceSkill
- cold-email-writerSkill
- comparison-page-writerSkill
- competitive-battlecardSkill
- competitor-teardownSkill
- crm-hygiene-auditSkill
- customer-interview-guideSkill
- deal-qualificationSkill
- deliverability-auditSkill
- discovery-call-prepSkill
- domain-warmup-planSkill
- email-authentication-setupSkill
- email-copy-reviewSkill
- event-follow-upSkill
- expansion-opportunity-finderSkill
- first-line-personalizationSkill
- follow-up-email-writerSkill
- funding-signal-outreachSkill
- gtm-global-rulesSkill
- hiring-signal-outreachSkill
- job-change-playsSkill
- lead-list-builderSkill
- lead-magnet-builderSkill
- lead-scoring-modelSkill
- linkedin-comment-strategySkill
- linkedin-connection-noteSkill
- linkedin-message-sequenceSkill
- linkedin-post-writerSkill
- linkedin-profile-optimizerSkill
- list-cleaningSkill
- lookalike-account-finderSkill
- meeting-booking-replySkill
- messaging-matrixSkill
- multichannel-cadenceSkill
- mutual-action-planSkill
- negotiation-playbookSkill
- no-show-recoverySkill
- objection-handlerSkill
- outbound-ab-testSkill
- outbound-mathSkill
- outreach-compliance-checkSkill
- pipeline-reviewSkill
- post-engagement-outreachSkill
- proposal-follow-upSkill
- prospect-research-briefSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
8
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 16
Use this when the question is "who should we sell to?".
- Distinctive: line 20
Ask for as much as exists, then work with what you get:
- Distinctive: line 25
If there are fewer than 10 customers: the founder's notes on the best five conversations, plus the best five failures.
- Distinctive: line 51
Every trait becomes a filter a list builder can run: industry codes, headcount ranges, job titles, keywords in job listings, technologies …
- Distinctive: line 76
MUST base every trait on deal data or explicit notes, and say which.
- Distinctive: line 77
MUST include at least three disqualifiers.
- Distinctive: line 78
NEVER mix the economic buyer and the end user into one persona.
- Distinctive: line 79
NEVER present a trait with fewer than five supporting accounts as proven.
“Common” is measured: kept by at least 6 in 10 of the 9 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
Use this when the question is "who should we sell to?". It produces a one-page ICP that a rep, a marketer and a list builder can all act on the same day.
Inputs
Ask for as much as exists, then work with what you get:
- Closed-won deals for the last 12 to 24 months: company, size, industry, region, deal value, cycle length, who signed, why they bought.
- Closed-lost and churned accounts with the reason.
- The product's core job and price range.
- If there are fewer than 10 customers: the founder's notes on the best five conversations, plus the best five failures.
The play
1. Rank customers by value, not by count
Sort won deals by a blend of revenue, cycle speed and retention. The top 20% is the real ICP; the long tail is noise. A segment with many small, slow, churn-prone deals looks big on a pie chart and loses money.
2. Find the traits that separate winners from losers
For each trait, compare the share among top customers with the share among lost or churned ones. Traits worth keeping show a gap of at least 20 points. Look at four layers:
| Layer | Examples |
| Firmographic | Industry, headcount band, revenue band, region, business model |
| Technographic | Tools they already run, data maturity, stack that integrates with yours |
| Situational | Hiring for a role, new leader in seat, funding, expansion, a regulation deadline |
| Behavioural | How they buy: committee size, procurement, self-serve trial or demo |
Situational traits usually predict timing better than firmographics predict fit. Read references/icp-scoring.md for the comparison table and the scoring weights.
3. Write the pain in the buyer's words
Pull phrases from call notes, emails and reviews. "We lose two days a month reconciling payouts" beats "operational inefficiency".
4. Set disqualifiers
Hard noes save more time than must-haves. Typical ones: below a headcount that can afford the price, a region you cannot serve, a tech stack you cannot integrate with, a business model where the pain does not exist.
5. Translate it into filters
Every trait becomes a filter a list builder can run: industry codes, headcount ranges, job titles, keywords in job listings, technologies detected. Flag traits that cannot be filtered and must be checked by research.
Output format
ICP: <one-line name, e.g. "Multi-location restaurant groups, 5-50 sites">
Why they buy: <pain in their words> | Trigger: <what makes now the moment>
Must-haves: <3-5 traits>
Nice-to-haves: <2-4 traits that raise priority>
Disqualifiers: <3-5 hard noes>
Buyer: <title that signs> Champion: <title that feels the pain> Users: <who uses it>
Filters: <list-builder ready criteria>
Confidence: <high / medium / low and why: sample size, data gaps>What good looks like
- Narrow enough that a rep can name 50 target accounts from memory after reading it. "B2B SaaS companies" is not an ICP.
- It includes a trigger. Fit without timing produces polite "not right now" replies.
- Disqualifiers are as specific as the must-haves.
- The confidence note is honest: an ICP built from six customers says so and lists what to test next.
- The common mistake is describing the customers you want instead of the customers who bought, renewed and expanded.
Rules
- MUST base every trait on deal data or explicit notes, and say which.
- MUST include at least three disqualifiers.
- NEVER mix the economic buyer and the end user into one persona.
- NEVER present a trait with fewer than five supporting accounts as proven; mark it as a hypothesis.
Example prompts
- "Here are our last 40 closed-won and 25 closed-lost deals. Build our ICP."
- "We have 7 customers. Help me write a first ICP and tell me what to test."
- "Our reply rate dropped to 1%. Check whether our ICP is too broad."
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.

