Skip to content
cccskills
FreePublished on GitHub

icp-research

Builds an ideal customer profile from evidence: case studies, testimonials, customer logos, solutions pages, reviews and any sales notes you have. Produces market sizing layers, firmographic segments, a champion and an economic buyer persona, a negative ICP, intent signals, customer proof points and a voice-of-customer section in the buyers' own words, every claim sourced. Triggers: "ICP research", "ideal customer profile", "who are our customers", "customer segments", "buyer personas", "who should we target". Run after /company-context. Not for competitor analysis (use /competitor-research) or call transcript patterns (use /win-loss).

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md5.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

ICP research

Work out who actually buys, who signs, who uses it and who isn't a fit, from what customers have said and done in public and in your own records. The output is the ICP file every later skill reads before it writes a word.

When to use it

  • Building the context folder, right after /company-context.
  • Before positioning or messaging work, when nobody can say who the best customers are in one sentence.
  • When sales keeps chasing deals that don't close and you suspect the target is too broad.

Don't use it to analyse sales calls (/win-loss) or competitors (/competitor-research).

Inputs

Required: the company website URL. If it's missing, ask.

Recommended: context/company/ from /company-context; links to case studies and testimonials; a customer list or CRM export (strip names and emails first); sales notes on wins and objections; any existing ICP document to check against.

If a recommended input is missing, run from what you have and list what's missing in the data gaps section.

Paths. Write to context/icp/MMYY-icp.md. Agency or consultant? Swap context/ for clients/<client>/context/ throughout.

Tools. Web search and page fetching are enough. Exa or Firecrawl help if you have them. Review sites (G2, Capterra) and the company's LinkedIn page are useful public sources.

Steps

  1. Find the evidence pages. Customers, case studies, testimonials, solutions or industry pages, pricing, integrations, review sites. Produces: a source list with URLs and access dates.
  2. Extract raw data per customer. Company name, industry, size, region, role of the person quoted, the problem they described, the outcome they reported, tools they mention. Produces: a customer evidence table.
  3. Normalise the attributes. Put size, industry and region into consistent bands so you can count them.
  4. Find the segments. Count which industries, sizes and regions repeat. A segment needs several customers behind it, not one logo. Produces: 2 to 4 candidate segments with counts.
  5. Size the market in layers. Total market, the part you can serve, the part you can realistically win, and the ICP as the best slice of that. Show the maths and mark estimates. Each layer must be smaller than the one above.
  6. Build two personas. The champion (who feels the pain and pushes for the purchase) and the economic buyer (who signs). Cover goals, pains, triggers, objections and how each one judges success. They must read differently.
  7. Write the negative ICP. Who looks like a fit but isn't, and the signals that disqualify them.
  8. List intent signals and buying triggers. Observable events that show a company is ready: a new hire, funding, a tool change, a regulation, a growth milestone.
  9. Collect proof points. Named customers with outcomes and URLs. Only customers referenced in public or in data the user gave you.
  10. Synthesise voice of customer. Exact phrases customers use for their problem and their outcome. Quote, don't paraphrase.
  11. Recommend the priority segment. Rank the segments and say why the first one wins.
  12. List data gaps and what would fill them (interviews, CRM fields, win-loss).

Output shape

Open with a 3-line TLDR and a short block of open questions. Then:

  1. Header: date, website, confidence score 1 to 5.
  2. Market sizing layers with the maths.
  3. Firmographics: industry, size, region, tech stack patterns.
  4. Personas: champion, economic buyer, and users or influencers if relevant.
  5. Negative ICP.
  6. Customer proof points.
  7. Voice of customer.
  8. Segment definitions, ranked, with intent signals.
  9. Recommendations.
  10. Data gaps.
  11. Sources with URLs, dates and confidence.

Sort roles as champion, economic buyer, user, influencer. Sort sizes from largest to smallest.

What good looks like

  • Every customer named is public or came from the user's own data.
  • Quotes are verbatim and attributed to a role.
  • The champion and the economic buyer have different pains and different success measures.
  • The negative ICP excludes real companies someone might chase.
  • Segment claims show their count ("6 of 14 case studies"). Small samples are flagged once, not repeated in every section.
  • The confidence score matches the evidence: mostly high-confidence sources score 4 or 5, mostly estimates score 1 or 2.

Mistakes to avoid

  • Inventing customer names or composite quotes.
  • Personas built from imagination ("Marketing Mary, 34, loves podcasts").
  • Market sizing that grows as it narrows, or a top-down number with no maths.
  • Calling one big logo a segment.
  • Writing the same caveat in every section. Say it once and point to it.

Chain

Part of the free five-skill chain: icp-research → /competitor-research → /tov-guidelines → /positioning → /messaging. The other six context skills (company context, win-loss, founder POV, brand kit, funnel and goals) are in the paid context plugin ($19.99, link in the README).

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Researches one B2B SaaS competitor across 13 dimensions (company, product, ICP, pricing, reviews, content, launches, search and AI visibility, tech stack, hiring, go-to-market, social, paid ads) and writes a sourced dossier with an executive summary, a threat level, strengths and weaknesses, and a data gaps section. Run it once per competitor, then compare. Triggers: "competitor analysis", "competitor research on", "what is [competitor] doing", "compare us to", "competitive landscape", "battlecard prep". Run after /company-context and /icp-research. Not for researching your own company (use /company-context).

The English summary is being prepared. Showing the original description.

matteotitta/repo-structure-in-house68Updated Oct 21, 2026

level

Free

Score your Claude Code environment on a fun 0-10 ladder (Tourist → Swarm) calibrated to the quickstart's 4 systems — Context, Skills, Integrations, Orchestration. Two front doors - an interactive quiz (zero setup, shareable) or a silent scan of your repo. Outputs a next-level roadmap plus a branded HTML dashboard or a paste-anywhere ASCII card. The default mastery skill of this quickstart. Triggers - "level", "what's my claude code level", "claude code level quiz", "assess my setup", "how good is my setup", "claude code maturity"

The English summary is being prepared. Showing the original description.

matteotitta/repo-structure-in-house68Updated Oct 21, 2026

Builds a product messaging library from your positioning, your website and customer evidence: a description, the status quo and alternatives, pain points with their knock-on consequences, capabilities, functional, emotional and social benefits, branded features, the cost of doing nothing, common objections with responses, and core messaging blocks (tagline, elevator pitch, value props, proof, per-audience lines). Every claim sourced. Triggers: "product messaging", "messaging library", "messaging framework", "value props", "capabilities and benefits", "what are our differentiators in words". Run after /positioning. Not for choosing the position itself (use /positioning).

The English summary is being prepared. Showing the original description.

matteotitta/repo-structure-in-house68Updated Oct 21, 2026

Develops B2B SaaS positioning from your ICP, competitor and win-loss evidence. Maps what buyers compare you to, chooses between leading with a category or a problem, picks a primary and secondary anchor and up to three defensible differentiators, lays out 2 to 4 worked positioning options with a comparison canvas so you can decide, then locks the chosen one and tests it (clarity ladder, guarantee test). Triggers: "positioning", "how do we position", "what category are we in", "how do we differentiate from", "our homepage is confusing", "positioning options". Run before /messaging. Not for taglines or a messaging library (use /messaging).

The English summary is being prepared. Showing the original description.

matteotitta/repo-structure-in-house68Updated Oct 21, 2026

Extracts a company's tone of voice from its own content and turns it into rules a writer or an AI can follow. Phase 1 analyses 15 to 20 pages for sentence, paragraph, word and structure patterns with frequency counts; after the user reviews it, Phase 2 writes the guidelines: tone attributes with before and after examples, a We are / We are not table, tone by context, vocabulary to use and avoid, and open questions. Triggers: "tone of voice", "brand voice", "voice guidelines", "writing style guide", "extract voice from our website", "TOV". Not for visual identity (use /brand-kit) or messaging (use /messaging).

The English summary is being prepared. Showing the original description.

matteotitta/repo-structure-in-house68Updated Oct 21, 2026

See all skills by matteotitta

Report a problem with this skill