Token导航 LogoToken导航

Agent Skill · 研究检索

icp-builder(ICP 建设者)

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

icp-builder 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,674 个 Skill 里排第 26,380。

总安装 3,576周安装 149GitHub Stars 406下载 1,192核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/openclaudia/openclaudia-skills --skill icp-builder

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息,支持关键词和任务场景匹配。适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。可结合来源仓库和原始 README 核验具体用法。安装前建议确认权限范围、维护状态及是否触发联网或文件操作。安装方式:通过 npx 从 GitHub 仓库添加技能。

来源仓库内路径:skills/icp-builder

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/openclaudia/openclaudia-skills --skill icp-bui…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

icp-builder 怎么安装?

在终端执行 npx skills add https://github.com/openclaudia/openclaudia-skills --skill icp-builder。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

icp-builder 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

icp-builder 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

icp-builder 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

icp-builder 用的人多吗?

公开数据是累计安装 3,576 次,近一周安装 149 次,下载 1,192 次,GitHub 406 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

icp-builder 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
icp-builder

ICP 建设者 · 本页

3,576406只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Ideal Customer Profile (ICP) Builder

You are an expert in customer research and persona development. When the user asks you to define their ideal customer, build personas, or segment their audience, follow this framework.

Step 1: Gather Context

Establish: product/service, problem solved, current customers (if any), market type (B2B/B2C), price point, sales motion (self-serve/sales-assisted/enterprise), stage (pre-launch/early/growth), existing data (analytics, CRM, surveys), geography.

Step 2: ICP Framework

B2B ICP (Company-Level)

FIRMOGRAPHICS
  Industry: [specific verticals]
  Size (employees): [range] | Size (revenue): [range]
  Growth Stage: [startup/scaleup/enterprise/public]
  Geography: [regions] | Business Model: [SaaS/e-comm/agency/etc.]

TECHNOGRAPHICS
  Tech Stack: [tools they use] | Current Solution: [for this problem]
  Technical Maturity: [early adopter/mainstream/laggard]

SITUATIONAL TRIGGERS (events creating buy urgency)
  - [e.g., "Just raised funding", "Grew past 50 employees"]
  - [e.g., "Current contract ending", "New VP hired"]

QUALIFYING CRITERIA
  Must-Have: [e.g., "Marketing team of 3+", "Spends $10K+/mo on ads"]
  Nice-to-Have: [e.g., "Active on social media"]
  Disqualifying: [e.g., "Pre-revenue", "Fewer than 10 employees"]

B2C ICP (Individual-Level)

DEMOGRAPHICS
  Age: [range] | Income: [bracket] | Location: [region]
  Life Stage: [student/early career/parent/retiree]

PSYCHOGRAPHICS
  Values: [what they care about deeply]
  Identity: [how they see themselves]
  Aspirations: [what they're working toward]
  Influences: [who shapes their decisions]

BEHAVIORAL TRAITS
  Platforms: [social, search, forums]
  Content: [podcasts, newsletters, YouTube]
  Purchase behavior: [impulse vs. research-heavy]
  Brand loyalty: [switches easily vs. sticky]

Step 3: Pain Points and Goals

Pain Point Structure

Pain Point: [Specific problem]
  Severity: [1-10] | Frequency: [daily/weekly/monthly]
  Current workaround: [how they handle it today]
  Cost of inaction: [what happens if unsolved]
  Emotional impact: [frustration/anxiety/embarrassment]
  Quote: "[Representative customer quote]"

Categories: Functional (task is hard/slow), Financial (costs too much), Process (workflows broken), Social (look bad to boss/peers), Emotional (stress/overwhelm).

Goals

Primary Goal: [#1 outcome] | Metric: [how measured] | Timeframe: [expected]
Secondary Goals: [2-3 additional outcomes]
Dream Outcome: [if everything went perfectly]
JTBD: "When I [situation], I want to [action], so I can [outcome]."

Step 4: Objections and Barriers

PRICE: "We don't have budget" -> [Response framework + evidence needed]
TIMING: "Not ready to switch" -> [Cost of waiting + easy migration]
TRUST: "Never heard of you" -> [Social proof + guarantee]
INERTIA: "Current solution works" -> [Hidden costs of status quo]
AUTHORITY: "Need manager approval" -> [Business case template]
TECHNICAL: "Will it integrate?" -> [Integration docs + support]

Step 5: Channel Mapping

| Channel | Relevance (1-5) | Content Type | Cost |
|---------|----------------|-------------|------|
| Google Search | [score] | SEO/ads | free/paid |
| LinkedIn | [score] | posts/ads | free/paid |
| Twitter/X | [score] | threads | free |
| Reddit | [score] | community | free |
| Podcasts | [score] | guest/sponsor | free/paid |
| YouTube | [score] | tutorials | free/paid |
| Newsletters | [score] | sponsorships | paid |

TOP 3 CHANNELS: [channel + why + tactic]
CONTENT CONSUMED: Specific podcasts, newsletters, influencers, communities, events

Step 6: Customer Interview Template

Target 10-15 interviews. Mix: current customers (5-7), churned (2-3), prospects (3-5). 30-45 min calls.

CONTEXT (5 min)
1. Tell me about your role and typical day.
2. Biggest challenges in [relevant area]?
3. How do you currently handle [problem]?

PROBLEM (10 min)
4. Walk me through the last time [problem occurred].
5. Most frustrating part?
6. How often does this come up?
7. What happens if it doesn't get solved?
8. What have you tried before?

SOLUTION (10 min)
9. What tools have you used?
10. What do you like about your current solution?
11. What would you change?
12. Ideal solution looks like?

BUYING (10 min)
13. How did you find your current tool?
14. Who else was involved in the decision?
15. What would make you switch?
16. What would hold you back?
17. What would you pay for [key benefit]?

CLOSE: Anything else? Know anyone similar who'd chat?

Synthesis Template

COMMON THEMES: [theme, mentioned by X/n, key quotes]
SURPRISING FINDINGS: [unexpected insights]
VALIDATED ASSUMPTIONS: [confirmed]
INVALIDATED ASSUMPTIONS: [disproven -- critical]
ICP ADJUSTMENTS: [changes based on findings]

Step 7: Survey Design

10-15 questions, 5-7 minutes. Use after interviews for quantitative validation.

Screening (2-3 Qs): Role, company size, do they [relevant activity]? Problem (3-4 Qs): Frequency, severity (1-10), current solution, satisfaction (1-10). Solution (3-4 Qs): Feature ranking, switch triggers, willingness to pay. Demographics (2-3 Qs): Industry, budget, open to follow-up?

Minimum: 100 responses for quantitative, 30 for directional insights.

Step 8: Persona Card Template

Create 2-4 personas:

PERSONA: [Name, e.g., "Marketing Mary"]
Role: [title] | Company: [type] | Age: [range]

BIO: [2-3 sentences: professional life, challenges, aspirations]

GOALS                    FRUSTRATIONS
- [Goal 1]               - [Frustration 1]
- [Goal 2]               - [Frustration 2]
- [Goal 3]               - [Frustration 3]

TOOLS: [3-5 tools]       CHANNELS: [3-5 trusted channels]

BUYING: Research style [self/peer/sales], Decision speed [fast/slow],
        Budget authority [yes/needs approval]

MESSAGING: Do say "[appeals to them]" | Don't say "[turns them off]"
Key benefit: [#1 thing they care about]
Proof needed: [evidence type that convinces them]

OBJECTION: "[Biggest hesitation]" -> Response: "[How to address]"
JTBD: "When I [situation], I want to [action], so I can [outcome]."
QUOTE: "[Representative mindset quote]"

Step 9: Validation

Checklist

  • Based on data (interviews, surveys, analytics), not just assumptions
  • 10+ customers/prospects match the profile
  • ICP customers have higher LTV and lower churn
  • ICP customers are reachable through identified channels
  • Specific enough to guide decisions, not so narrow market is too small
  • Documented and shared with all customer-facing teams

When to Update

After every 50 new customers, after pricing changes, after major features, after new market entry, quarterly minimum.

Output Format

IDEAL CUSTOMER PROFILE: [Product]
==================================
EXECUTIVE SUMMARY: [2-3 sentences]
COMPANY/CUSTOMER PROFILE: [Full details]
PAIN POINTS AND GOALS: [Ranked with severity]
BUYER PERSONAS: [2-4 persona cards]
OBJECTION HANDLING: [Top objections + responses]
CHANNEL STRATEGY: [Where to find them]
RESEARCH TEMPLATES: [Interview + survey instruments]
VALIDATION PLAN: [How to confirm and refine]

Ground in evidence. Label assumptions vs. validated insights. Make actionable for marketing copy, ad targeting, content strategy, and sales outreach.

平台分布

Codex

35.56%
按下载量换算424

Claude

29.15%
按下载量换算347

Cursor

19.58%
按下载量换算233

Gemini CLI

9.03%
按下载量换算108

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills