Token导航 LogoToken导航

Agent Skill · 研究检索

champion-identifier-skill(冠军识别技能)

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

champion-identifier-skill 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 70,176。

总安装 212周安装 9GitHub Stars 12下载 74核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/scientiacapital/skills --skill champion-identifier-skill

这个 Skill 是做什么的

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

识别目标公司最可能成为内部 champion 的人员。基于公司阶段、痛点和决策风格进行分析。输出带评分的候选人列表和针对性接触方案。champion-identifier-skill 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/champion-identifier-skill

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

champion-identifier-skill 怎么安装?

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

champion-identifier-skill 支持哪些 AI 工具?

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

champion-identifier-skill 需要什么权限?

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

champion-identifier-skill 是免费的吗?

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

champion-identifier-skill 用的人多吗?

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

champion-identifier-skill 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
champion-identifier-skill

冠军识别技能 · 本页

21212只读未明确有提醒

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

SKILL.md 原文

Champion Identifier

<quick_start> Trigger: "Find potential champions at [Company]" or "Who should I connect with at [Company] to champion our tool?" Input: Target company name, your solution/product, any existing contacts Output: Ranked champion candidates with scores (0-60), outreach templates, org chart, and multi-threading strategy </quick_start>

<success_criteria>

  • Company context analyzed (stage, news, pain points, decision style)
  • 3-4 champion candidates identified and scored on 6 dimensions
  • Each candidate has outreach strategy (warm intro or direct)
  • Multi-threading plan with coverage map provided
  • Warning signs and red flags documented
  • Champion development plan with phased actions included </success_criteria>

What Makes a Great Champion?

The Champion Profile:

  • Has Pain: Directly affected by the problem you solve
  • Has Power: Can influence decision or control budget
  • Has Gain: Personally benefits when you win (promotion, bonus, easier life)
  • Is Accessible: You can reach them and build relationship
  • Is Willing: Open to new solutions and vendors

Champion vs. Coach vs. Blocker:

  • Champion: Actively sells for you internally, has skin in the game
  • Coach: Helpful but passive, gives you intel but won't advocate
  • Blocker: Opposes your solution (loves incumbent, risk-averse, loses if you win)

Scoring Framework

Scoring Dimensions (0-10 each):

  1. Role Relevance - How directly does their role relate to your solution?
  2. Influence Level - Can they affect the buying decision?
  3. Accessibility - Can you reach them? Warm intro possible?
  4. Change Agent - Track record of adopting new solutions?
  5. Personal Stake - Do they personally gain if you win?
  6. Engagement Potential - Likely to respond to outreach?

Total Champion Score: 0-60 points

  • 50-60: Ideal champion candidate
  • 40-49: Strong potential champion
  • 30-39: Possible champion with work
  • Below 30: Not likely to champion

Output Format

# Champion Identification: [Company Name]

**Company**: [Company Name] | **Industry**: [Industry] | **Size**: [Employees]
**Your Solution**: [What you sell] | **Analysis Date**: [Date]

---

## Target Account Overview

**Company Context**:
- Stage: [Startup/Growth/Enterprise] | Recent News: [Funding/Growth/Changes]
- Likely Pain Points: [Based on stage and industry]
- Decision-Making Style: [Committee/Top-down/Consensus]

**Your Connection**:
- Existing Contacts: [X] | Mutual Connections: [X] 2nd degree
- Inbound Interest: [Yes/No] | Competitive Intel: [Competitor?]

---

## Champion Candidates (Ranked)

### #1 IDEAL CHAMPION: [Name]
**Champion Score**: 54/60

**Profile**: [Name] | [Title] | [Department] | [Tenure] years

**Scoring**: Role Relevance: 10/10 | Influence: 9/10 | Accessibility: 8/10
Change Agent: 9/10 | Personal Stake: 10/10 | Engagement: 8/10

**Why They're Ideal**:
- Pain: [Specific pain points their role experiences]
- Gain: [Career/team/personal impact when you win]
- Help: Can give insight into process, intro to EB, advocate internally

**Outreach Strategy**:
Best Approach: [Warm intro via X / Direct outreach]

Warm Intro Message:
> Hey [Mutual], I'm trying to connect with [Name] at [Company].
> We help [companies like theirs] with [problem]. Would you be
> comfortable making an intro?

Direct Outreach:
> Subject: [Company] - [Specific Problem]
> Hi [First Name], I noticed [observation] and thought you might
> be dealing with [problem]. We helped [similar company] reduce
> [metric] by [X%]. Worth a quick call?

**Personalization Hooks**:
- Recent Activity: [LinkedIn posts, job change, etc.]
- Shared Interests: [University, conference, group]
- Best Opening: "Hi [Name], saw you recently [activity]..."

### #2 STRONG POTENTIAL: [Name]
**Champion Score**: 47/60

[Profile, scoring breakdown, strengths, concerns, outreach approach]

### #3 GOOD BACKUP: [Name]
**Champion Score**: 42/60

[Similar structure, slightly shorter]

---

## Who NOT to Lead With

### [Name] - [Title]
**Why Not**: [Too senior / Wrong department / Blocker risk]
**But Consider**: [When they might be useful later]

---

## Multi-Threading Strategy

1. **Start With**: Champion #1 - Highest probability
2. **Parallel Outreach**: Champion #2 - Different department
3. **Economic Buyer Access**: Ask Champion #1 to introduce up
4. **Technical Validator**: Connect with [Technical Person]
5. **User Buy-In**: Get feedback from [End User Rep]

**Coverage Map**:
Economic Buyer (Decision): [Name, Title]
  → Champion (Advocate): [Champion #1]
    → Technical (Validate): [Technical Person]
      → Users (Adopt): [User Team]

---

## Account Mapping (DMU)

| Person | Role | Title | Champion Score | Influence | Status |
|--------|------|-------|---------------|-----------|--------|
| [Name] | Champion | [Title] | 54/60 | High | Not contacted |
| [Name] | Economic Buyer | [Title] | N/A | Final | Via Champion |
| [Name] | Technical Buyer | [Title] | 35/60 | Veto | Should engage |
| [Name] | End User | [Title] | 28/60 | Feedback | Include in demo |

---

## Champion Development Plan

### Phase 1: Initial Contact (Week 1)
- [ ] Secure warm intro or send personalized outreach
- [ ] Schedule discovery call
**Success**: Meeting scheduled

### Phase 2: Discovery & Qualification (Week 1-2)
- [ ] Run discovery call, validate pain
- [ ] Assess influence and willingness
- [ ] Get them to open up about process and players
**Success**: They articulate pain clearly and agree to next step

### Phase 3: Value Demonstration (Week 2-3)
- [ ] Tailored demo focused on their pain points
- [ ] Share case study, calculate ROI
**Success**: They say "this would really help us"

### Phase 4: Champion Activation (Week 3-4)
- [ ] Ask: "Would you be comfortable introducing me to [decision maker]?"
- [ ] Provide ammo to sell internally (ROI calc, one-pager)
**Success**: They introduce you to economic buyer

### Phase 5: Deal Progression (Ongoing)
- [ ] Regular check-ins, coaching on internal process
- [ ] Get input on proposal, have them socialize internally
**Success**: Deal moves forward with their help

Discovery Questions

For Discovery Calls:

  1. "Walk me through how [process] works today at [Company]"
  2. "What's working well? What's frustrating?"
  3. "If you could wave a magic wand, what would you fix?"
  4. "Who else is impacted by [problem]?"
  5. "What have you tried? Why didn't it work?"

For Champion Qualification:

  1. "Is this problem on your roadmap to solve?"
  2. "How did buying decisions work in the past?"
  3. "Who typically gets involved?"
  4. "What would success look like for you personally?"
  5. "Would you be comfortable introducing me to [economic buyer]?"

Warning Signs (Not Actually a Champion)

  • Too Agreeable: Says yes to everything but never takes action
  • Can't Get You to Others: Always has excuse why you can't meet boss
  • Doesn't Know Process: Can't describe how buying decisions get made
  • Not Actually Affected: Talks about problem in abstract, no personal examples
  • No Skin in Game: No personal KPIs tied to the problem

Action: Keep them in loop but find the REAL champion who has pain.

Pro Tips

Finding Champions: Look for recent hires (want quick wins), promotions (want to prove themselves), pain posters (share challenges on LinkedIn), change agents (adopt new tools), event speakers (accessible).

Building Relationships: Make them look good internally, arm them with talking points and ROI, coach them on selling you internally, don't put them in awkward political positions.

Best Practices:

  1. Start at Director/VP level (too junior = no power, too senior = too busy)
  2. Multi-thread to reduce single point of failure
  3. Qualify early with validation questions
  4. Give value before asking for introductions
  5. Document champion interactions in CRM

Emit Outcome Sidecar

As the final step, write to ~/.claude/skill-analytics/last-outcome-champion-identifier.json:

{"ts":"[UTC ISO8601]","skill":"champion-identifier","version":"1.0.0","variant":"default",
 "status":"[success|partial|error]","runtime_ms":[estimated ms from start],
 "metrics":{"profiles_analyzed":[n],"champions_identified":[n],"atl_count":[n],"confidence_high":[n]},
 "error":null,"session_id":"[YYYY-MM-DD]"}

Use status "partial" if some stages failed but results were produced. Use "error" only if no output was generated.

平台分布

Codex

40.44%
按下载量换算30

Claude

29.39%
按下载量换算22

Cursor

17.42%
按下载量换算13

Gemini CLI

10.42%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills