Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问许可证需确认审计提醒

icp-identificationICP 鉴定

Agent Skill

icp-identification 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

196

周安装

8

GitHub Stars

630

下载量

63
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:icp-identification(ICP 鉴定)
来源仓库:https://github.com/gooseworks-ai/goose-skills
仓库路径:skills/icp-identification
安装命令:
npx skills add https://github.com/gooseworks-ai/goose-skills --skill icp-identification
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/gooseworks-ai/goose-skills --skill icp-identification

简介

用于查找、检索和筛选与 ICP(目标客户画像)识别相关的工具或方法。

  • 适合在用户分层或精准营销场景中提供支持。icp-identification 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 需结合企业实际数据验证识别模型的适用性。
  • 可通过 npx 命令从 GitHub 仓库安装,适用于 Claude、Cursor 等平台。
  • 建议优先选择提供示例数据集或评估指标的项目。

SKILL.md

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 to Auto-Load

  • User says "find me leads", "help me find prospects", "who should I sell to", or similar
  • User provides a company URL and asks for leads/prospects
  • User describes an idea/product and wants to find customers
  • User asks "who is my ICP?" or "help me define my target market"
  • User asks to "map my TAM", "size my market", or "build a target account list"

Phase 0: Gather Context

When triggered, collect these inputs from the user:

  1. Company URL or describe your idea/product
  2. What does the product/service do? (skip if URL provided — we'll research)
  3. Who are your current customers? (if any — ask for specific company names, titles of buyers/champions, and how they found the product. These examples calibrate search filters far better than abstract descriptions.)
  4. What's your price point / deal size? (helps determine buyer seniority)
  5. Who is NOT a fit? — Ask about industries, company types, company sizes, or roles that are explicitly wrong for this product. Prompt with examples: *"Are there industries that definitely don't work? Company sizes too small or too large? Titles that look right but never buy?"* Even rough exclusions prevent noisy search results downstream.

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.

Phase 1: Research

Using web search and the company URL, investigate:

  1. Company research — What do they sell? Who do they sell to? Value proposition. Pricing model.
  2. Market analysis — What category/space? Market size signals. Growth stage.
  3. Competitor identification — Who are the top 3-5 competitors? How are they positioned?
  4. Buyer signals — Who buys this kind of product? What titles? What triggers a purchase?

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?"*

Phase 2: Define ICP

Based on research + user input, propose a structured ICP:

DimensionRecommendationReasoning
Job Titlese.g., VP Sales, Head of Revenue OpsDirect buyers of sales tools
Senioritye.g., VP, DirectorBudget authority at this deal size
Company Sizee.g., 51-200 employeesSweet spot for this product
Industrye.g., SaaS, FinTechHighest product-market fit
Regione.g., US, SF Bay AreaCurrent market focus
Signalse.g., recently hired, posted about painTiming indicators

Present as a table. Ask user to confirm, adjust, or refine. Iterate until they approve.

Exclusion Criteria (Equally Important)

Define what to filter OUT. These map directly to "not in" / exclusion parameters in search tools:

DimensionExcludeReasoning
Titles to excludee.g., Intern, Coordinator, Assistant, StudentNo budget authority or decision power
Industries to excludee.g., Government, Education, Non-profitProduct doesn't serve these verticals
Company types to excludee.g., Agencies, consultancies, sole proprietorsNot a fit for the product model
Company size to excludee.g., 1-10 employees, 10,000+Too small to need it / too large to buy it
Specific companies to excludee.g., existing customers, competitors, partnersAlready 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.

Phase 3: Choose Path — TAM or Leads?

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."*

Path A: Map the TAM

If the user chooses TAM mapping, hand off to the TAM builder skill with the ICP definition. The TAM builder will:

  1. Search for companies matching the ICP filters
  2. Score and tier them by fit
  3. Build a persona watchlist for best-fit accounts

When to recommend TAM path:

  • User wants a systematic, account-based approach
  • Market is well-defined but user doesn't know which companies are in it
  • User plans to run ongoing outbound (not a one-shot campaign)
  • User wants to prioritize accounts by fit before reaching out
  • User asks about "market sizing", "target account list", or "account-based"

Path B: Find Leads/Prospects → Lead-Finding Skills

If the user chooses lead finding, present ranked strategies based on what's available in the skill graph:

#StrategySkill UsedBest ForEffort
1Database search — Search people DB by title, industry, region, company sizeapollo-lead-finderHigh volume, broad ICPLow
2Pain language — Find people posting about problems your product solvespain-language-engagersWarm leads with expressed needMedium
3Competitor audiences — Find people engaging with competitor contentcompetitor-post-engagersLeads already in-marketMedium
4KOL audiences — Find leads from industry influencer audienceskol-discoverykol-engager-icpNiche, high-quality leadsMedium
5Hiring signals — Find companies hiring roles your product replaces/supportsjob-posting-intentCompanies with budget & urgencyMedium
6Event attendees — Find leads from industry eventsget-qualified-leads-from-lumaEngaged, in-market leadsLow
7Apollo database search — Search Apollo's 210M+ contact database (free search, paid enrichment)apollo-lead-finderBroadest coverage, cost-controlled enrichmentLow

Recommendation logic:

  • Early-stage / broad ICP → Start with database search (volume) + pain language (warmth)
  • Established with known competitors → Competitor audiences + database search
  • Niche market → KOL audiences + event attendees
  • High urgency / budget signals matter → Hiring signals + database search

Recommend 1-2 strategies based on the ICP and company stage. Ask user to pick which to execute.

Phase 4: Hand Off

Once user selects their path and strategy(ies):

  1. Load the corresponding skill's SKILL.md
  2. Pass the ICP definition as context — titles, industries, regions, company size, signals
  3. Begin that skill's Phase 0 (intake) with ICP already populated — don't re-ask questions the ICP already answers
  4. If multiple strategies selected, execute sequentially — complete one before starting the next

Handoff format

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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.96%
按下载量换算23

Claude

29.02%
按下载量换算18

Cursor

16.99%
按下载量换算11

Gemini CLI

9.89%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills