本文へ移動
cccskills
無料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).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

Step 2 of the suggested chain: /company-context → icp-research → /competitor-research → /win-loss → /expert-pov → /tov-guidelines → /brand-kit → /positioning → /messaging → /funnel-strategy → /goals.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

brand-kit

無料

Extracts a company's visual identity from screenshots (best) or its website (fallback) and writes a DESIGN.md brand file: machine-readable tokens for colours, typography, spacing, corner radius and logo usage, plus short prose explaining how and when to use each, and a list of do's and don'ts. Any later page, deck, carousel or ad can read the tokens instead of guessing. Triggers: "brand kit", "brand guidelines", "extract our brand", "design tokens", "colours and fonts from", "visual identity", "DESIGN.md". Not for tone of voice (use /tov-guidelines) or messaging (use /messaging).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Researches a company from its website and public sources and writes a company profile: what it sells, who buys it, traction, funding, team, hiring, tech stack, key people, red flags and the gaps you still need to fill, every claim tagged with a source and a confidence level. Use it as the first file in a marketing context folder, or to prep a discovery call or qualify a prospect. Triggers: "company research", "company background", "company context for", "qualify this prospect", "discovery call prep", "account brief", or a company URL handed over for research. Not for competitor analysis (use /competitor-research) or customer profiles (use /icp-research).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

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).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Draws out a founder's or expert's point of view: what they believe about their market that others don't, the hot takes they'd defend, the stories behind them, and their taste. Generates interview questions, works from answers, a live call or existing content, and ends with ranked One Big Idea candidates for thought leadership and positioning. Triggers: "expert POV", "founder POV", "one big idea", "OBI", "contrarian beliefs", "what makes our founder different", "thought leadership foundation", "founder interview questions". Feeds /positioning and /tov-guidelines. Not for writing posts or articles, and not for brand voice rules (use /tov-guidelines).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

Works out a company's go-to-market motion (product-led, sales-led or hybrid) from its website and pricing, then maps the funnel stage by stage: a definition, strategy, leading inputs the team controls, lagging outputs with targets, cadence and owner for each stage, MQL, SQL and PQL criteria, post-sale stages, closed-lost re-entry paths and backward funnel maths from a revenue target. Triggers: "funnel strategy", "funnel stages", "pipeline stages", "PLG vs SLG", "lead qualification criteria", "map our sales process", "how do leads flow". Feeds /goals. Not for setting the target itself (use /goals).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

goals

無料

Turns a target someone has already committed to (a board plan, an annual plan, a contract) into a plan the team can measure: KPIs in three tiers with a guardrail for each, a baseline from real data, monthly pacing with lag and seasonality, and two or three channels chosen from how your ICP actually searches and buys. Writes context/goals/MMYY-scope.md and context/goals/measurement.md. It never invents the target. Triggers: "set our goals", "what are our KPIs", "revenue target and pacing", "which channels and what targets", "write the scope file", "are we on track". Run after /funnel-strategy. Not for designing funnel stages (use /funnel-strategy).

日本語の概要は準備中です。原文の説明を表示しています。

matteotitta/repo-structure-in-house632026年10月14日 更新

matteotitta のスキルをすべて見る

このスキルの問題を報告する