> Research a company or idea, define the Ideal Customer Profile, and route to the right next step — either mapping the TAM or finding leads/prospects directly. The entry point for any "find me leads", "map my market", or "who should I sell to" request. Auto-loads when a user provides a company URL or idea and asks for leads or market mapping.
npx skills add https://github.com/gooseworks-ai/goose-skills --skill icp-identification
Research a company or idea, define the Ideal Customer Profile, and route to the right next step. This is the entry point for any "find me leads" or "map my market" request — it sits upstream of all lead-finding and TAM-building skills and ensures we understand the business, define the target, and pick the right approach before executing.
When triggered, collect these inputs from the user:
If the user provides a company URL, research it using web tools before asking follow-up questions. Don't ask questions you can answer from the website.
Intake principle: Every answer here should help you populate a search filter (title, industry, headcount range, region) or an exclusion filter (titles to skip, industries to ignore, company types to avoid). If a user's answer is too vague to become a filter value, probe deeper. Don't ask generic strategy questions — ask questions that sharpen the search.
Using web search and the company URL, investigate:
Output: Synthesize findings into a brief (5-10 bullet points) and present to the user for validation. Example:
> Research Summary:
> - Company sells X to Y
> - Main competitors: A, B, C
> - Typical buyer: VP/Director level at mid-market companies
> - Purchase triggers: scaling team, switching from legacy tool, new budget cycle
> - Pricing suggests mid-market / enterprise buyer
Ask the user: *"Does this match your understanding? Anything to correct or add?"*
Based on research + user input, propose a structured ICP:
| Dimension | Recommendation | Reasoning |
|-----------|---------------|-----------|
| Job Titles | e.g., VP Sales, Head of Revenue Ops | Direct buyers of sales tools |
| Seniority | e.g., VP, Director | Budget authority at this deal size |
| Company Size | e.g., 51-200 employees | Sweet spot for this product |
| Industry | e.g., SaaS, FinTech | Highest product-market fit |
| Region | e.g., US, SF Bay Area | Current market focus |
| Signals | e.g., recently hired, posted about pain | Timing indicators |
Present as a table. Ask user to confirm, adjust, or refine. Iterate until they approve.
Define what to filter OUT. These map directly to "not in" / exclusion parameters in search tools:
| Dimension | Exclude | Reasoning |
|-----------|---------|-----------|
| Titles to exclude | e.g., Intern, Coordinator, Assistant, Student | No budget authority or decision power |
| Industries to exclude | e.g., Government, Education, Non-profit | Product doesn't serve these verticals |
| Company types to exclude | e.g., Agencies, consultancies, sole proprietors | Not a fit for the product model |
| Company size to exclude | e.g., 1-10 employees, 10,000+ | Too small to need it / too large to buy it |
| Specific companies to exclude | e.g., existing customers, competitors, partners | Already in pipeline or not appropriate |
Present exclusions alongside the inclusion table. Ask user to confirm both.
Important: The ICP definition becomes the input context for all downstream skills. Be specific — vague ICPs produce vague leads.
Search precision warning: Downstream tools (Apollo and similar databases) match on the exact title strings, industry tags, and keywords you pass them. Overly broad or stuffed filters (e.g., 15 keyword tags) return noisy results. Each filter value should be specific and intentional. When in doubt, use fewer, more precise values and let exclusions do the narrowing.
Once ICP is locked, ask the user:
> *"Now that we have the ICP defined, would you like to:*
> 1. Map your TAM — Build a scored Total Addressable Market: discover all companies matching your ICP, score and tier them, and build a persona watchlist for the best-fit accounts. This is the strategic, market-first approach.
> 2. Find leads/prospects now — Go straight to finding individual people to contact. This is the tactical, results-now approach.
>
> *TAM mapping is best when you want a full picture of your market, ongoing signal monitoring, and a systematic account-based approach. Lead finding is best when you need contacts to reach out to immediately."*
If the user chooses TAM mapping, hand off to the TAM builder skill with the ICP definition. The TAM builder will:
When to recommend TAM path:
If the user chooses lead finding, present ranked strategies based on what's available in the skill graph:
| # | Strategy | Skill Used | Best For | Effort |
|---|----------|-----------|----------|--------|
| 1 | Database search — Search people DB by title, industry, region, company size | apollo-lead-finder | High volume, broad ICP | Low |
| 2 | Pain language — Find people posting about problems your product solves | pain-language-engagers | Warm leads with expressed need | Medium |
| 3 | Competitor audiences — Find people engaging with competitor content | competitor-post-engagers | Leads already in-market | Medium |
| 4 | KOL audiences — Find leads from industry influencer audiences | kol-discovery → kol-engager-icp | Niche, high-quality leads | Medium |
| 5 | Hiring signals — Find companies hiring roles your product replaces/supports | job-posting-intent | Companies with budget & urgency | Medium |
| 6 | Event attendees — Find leads from industry events | get-qualified-leads-from-luma | Engaged, in-market leads | Low |
| 7 | Apollo database search — Search Apollo's 210M+ contact database (free search, paid enrichment) | apollo-lead-finder | Broadest coverage, cost-controlled enrichment | Low |
Recommendation logic:
Recommend 1-2 strategies based on the ICP and company stage. Ask user to pick which to execute.
Once user selects their path and strategy(ies):
SKILL.mdWhen transitioning to a downstream skill, carry forward:
ICP Context (from icp-identification):
Include:
- Titles: [list]
- Seniority: [list]
- Company size: [range]
- Industries: [list]
- Region: [list]
- Signals: [list]
- Product: [what the user sells]
- Competitors: [identified competitors]
Exclude:
- Titles to exclude: [list]
- Industries to exclude: [list]
- Company types to exclude: [list]
- Company size to exclude: [ranges]
- Companies to exclude: [specific names, if any]
This ensures downstream skills skip redundant intake questions and start executing immediately. Both inclusion and exclusion criteria must be passed — exclusions are what prevent noisy search results.
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.
Efficient database search tool for bioRxiv preprint server. Use this skill when searching for life sciences preprints by keywords, authors, date ranges, or categories, retrieving paper metadata, downloading PDFs, or conducting literature reviews.
Query and analyze scholarly literature using the OpenAlex database. This skill should be used when searching for academic papers, analyzing research trends, finding works by authors or institutions, tracking citations, discovering open access publications, or conducting bibliometric analysis across 240M+ scholarly works. Use for literature searches, research output analysis, citation analysis, and academic database queries.
Access USPTO APIs for patent/trademark searches, examination history (PEDS), assignments, citations, office actions, TSDR, for IP analysis and prior art searches.
Multiagent AI system for scientific research assistance that automates research workflows from data analysis to publication. This skill should be used when generating research ideas from datasets, developing research methodologies, executing computational experiments, performing literature searches, or generating publication-ready papers in LaTeX format. Supports end-to-end research pipelines with customizable agent orchestration.
Automated LLM-driven hypothesis generation and testing on tabular datasets. Use when you want to systematically explore hypotheses about patterns in empirical data (e.g., deception detection, content analysis). Combines literature insights with data-driven hypothesis testing. For manual hypothesis formulation use hypothesis-generation; for creative ideation use scientific-brainstorming.
Take gooseworks-ai/icp-identification from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.