Token导航 LogoToken导航

Agent Skill · 研究检索

competitor-intel(竞争对手英特尔)

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

competitor-intel 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,674 个 Skill 里排第 21,898。

总安装 4,725周安装 193GitHub Stars 141下载 1,513核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/ognjengt/founder-skills --skill competitor-intel

这个 Skill 是做什么的

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

用于查找、检索和筛选相关信息。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。适合在关键词搜索或任务场景中快速定位候选结果。可结合来源仓库 README 继续核验具体用法。安装前建议确认权限范围、维护状态及是否会触发联网或文件操作。

competitor-intel 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/competitor-intel

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

competitor-intel 怎么安装?

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

competitor-intel 支持哪些 AI 工具?

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

competitor-intel 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

competitor-intel 是免费的吗?

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

competitor-intel 用的人多吗?

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

competitor-intel 安全吗?

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

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

值得选的地方

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

竞争对手英特尔 · 本页

4,725141需要联网未明确有提醒

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

SKILL.md 原文

Competitor Intel

Purpose

Provide data-backed competitive intelligence by researching real signals across the web—no assumptions, no made-up numbers.


Execution Logic

Check $ARGUMENTS first to determine execution mode:

If $ARGUMENTS is empty or not provided:

Respond with: "competitor-intel loaded, proceed with competitor name and any context (website, industry, etc.)"

Then wait for the user to provide their requirements in the next message.

If $ARGUMENTS contains content:

Proceed immediately to Task Execution (skip the "loaded" message).


Task Execution

When user requirements are available (either from initial $ARGUMENTS or follow-up message):

1. Check for Business Context (Optional)

Check if FOUNDER_CONTEXT.md exists in the project root.

  • If it exists: Read it to understand your company's positioning, strengths, and goals—this informs the leverage strategies.
  • If it doesn't exist: Proceed with analysis focused purely on competitor weaknesses.

2. Extract Input

From the user's requirements, extract:

  • Competitor name (required)
  • Competitor website (if provided)
  • Industry/vertical (if provided)
  • Specific areas of interest (if provided)

3. Research Phase — MANDATORY WEB SEARCH

This skill REQUIRES web search. Do not proceed without searching.

Execute web searches across these sources:

Business Metrics Research

Search for verified data only. Query patterns:

  • "[Competitor]" revenue OR MRR OR ARR site:crunchbase.com
  • "[Competitor]" funding raised valuation site:crunchbase.com
  • "[Competitor]" employees headcount site:linkedin.com
  • "[Competitor]" revenue growth OR metrics
  • "[Competitor]" pricing customers
  • "[Competitor]" CEO OR founder interview revenue
  • "[Competitor]" Series A OR Series B OR funding
Traffic & SEO Research

Search for web traffic and search presence signals:

  • "[Competitor]" site:similarweb.com (traffic estimates, top pages, traffic sources)
  • "[Competitor]" site:ahrefs.com (backlinks, domain rating, organic keywords)
  • "[Competitor]" site:semrush.com (traffic, keyword rankings, ad spend)
  • "[Competitor]" site:trends.google.com (search interest over time)
  • [Competitor website domain] site:builtwith.com (tech stack, tools used)
Technical & Product Research

Search for product and development signals:

  • "[Competitor]" site:github.com (open source activity, tech stack, hiring signals)
  • [Competitor GitHub org] (commit frequency, contributors, project activity)
  • "[Competitor]" API OR integration OR developer
Advertising Research

Search for ad strategy and spend signals:

  • Search Meta Ads Library: https://www.facebook.com/ads/library/ for [Competitor]
  • "[Competitor]" ads site:facebook.com/ads/library
  • "[Competitor]" advertising spend OR ad budget
  • "[Competitor]" marketing campaign
Weakness & Sentiment Research

Search for complaints, issues, and struggles:

  • "[Competitor]" reviews site:g2.com
  • "[Competitor]" reviews site:capterra.com
  • "[Competitor]" reviews site:trustpilot.com
  • "[Competitor]" complaints OR issues OR problems
  • "[Competitor]" "doesn't work" OR "broken" OR "terrible"
  • "[Competitor]" layoffs OR firing OR cuts
  • "[Competitor]" lawsuit OR sued
Signal Research (for predictions)

Search for hiring, product, and strategic signals:

  • "[Competitor]" hiring site:linkedin.com
  • "[Competitor]" job openings
  • "[Competitor]" new feature OR launch OR release
  • "[Competitor]" roadmap OR upcoming
  • "[Competitor]" partnership OR integration
  • "[Competitor]" site:twitter.com OR site:x.com (founder/company posts)

4. Compile Verified Metrics

From research, extract ONLY verified numbers with sources:

  • MRR/ARR (if disclosed)
  • Funding raised (total and rounds)
  • Valuation (if known)
  • Employee count
  • Customer count
  • Churn rate (if disclosed)
  • Growth rate (if disclosed)
  • Pricing tiers

CRITICAL RULE: If a metric cannot be found with a source, mark it as "Not publicly available" — DO NOT estimate or assume.

5. Identify Leverage Opportunities

Analyze collected data to find 3 actionable weak spots:

Look for patterns in:

  • Product gaps: Features users complain about, missing integrations
  • Service failures: Support complaints, response times, bugs
  • Pricing friction: Users complaining about cost, hidden fees, poor value
  • Trust issues: Security concerns, data breaches, broken promises
  • Operational struggles: Layoffs, leadership changes, funding difficulties
  • Marketing weaknesses: Poor ad execution, weak positioning, low engagement

For each weakness, formulate an actionable strategy your company can execute.

6. Predict Next Moves

Based on all signals, predict what the competitor will likely do next:

Signals to interpret:

  • Hiring patterns: Engineering = product push, Sales = growth mode, Support = scaling issues
  • Job postings: Reveal technology bets, market expansion, new products
  • Funding status: Recent raise = aggressive expansion, No raise in 2+ years = potential trouble
  • Content/PR: Topics they're pushing indicate strategic focus
  • Partnership announcements: Reveal market positioning and gaps
  • Founder activity: Where they speak, what they post, who they meet

7. Format Output

Structure findings according to Output Format section.


Writing Rules

Hard constraints. No interpretation.

Core Rules

  • Every metric MUST include a source link or be marked "Not publicly available"
  • No estimations, assumptions, or "likely" numbers for metrics
  • Strategies must be actionable (specific steps, not vague advice)
  • Predictions must cite the signals that support them
  • Use neutral, analytical tone—not competitive trash talk
  • Date all findings (data freshness matters)

Source Rules

  • Prioritize primary sources (company announcements, founder interviews, SEC filings)
  • Crunchbase, LinkedIn, G2, Capterra are acceptable secondary sources
  • News articles are acceptable if they cite primary sources
  • Avoid unverified Twitter/X claims unless from official company accounts

Strategy Rules

  • Each strategy must exploit a verified weakness
  • Each strategy must include concrete next steps
  • Strategies should be achievable within 30-90 days
  • Avoid strategies that require significant capital unless user has it

Output Format

# Competitor Intel: [Competitor Name]
**Generated:** [Date]
**Sources searched:** [Count] sources across Crunchbase, LinkedIn, G2, Capterra, news, social

---

## 1. Verified Business Metrics

| Metric | Value | Source | Date |
|--------|-------|--------|------|
| Funding Raised | $X | [Source](url) | [Date] |
| Valuation | $X | [Source](url) | [Date] |
| Employee Count | X | [Source](url) | [Date] |
| MRR/ARR | Not publicly available | — | — |
| Customer Count | ~X | [Source](url) | [Date] |
| Churn Rate | Not publicly available | — | — |

**Key Observations:**
- [Insight about their financial health]
- [Insight about their growth trajectory]

---

## 2. Leverage Strategies

### Strategy 1: [Name]
**Weakness exploited:** [What you found]
**Evidence:** [Quote or data point with source]

**Action steps:**
1. [Specific action]
2. [Specific action]
3. [Specific action]

**Expected outcome:** [What this achieves]

---

### Strategy 2: [Name]
**Weakness exploited:** [What you found]
**Evidence:** [Quote or data point with source]

**Action steps:**
1. [Specific action]
2. [Specific action]
3. [Specific action]

**Expected outcome:** [What this achieves]

---

### Strategy 3: [Name]
**Weakness exploited:** [What you found]
**Evidence:** [Quote or data point with source]

**Action steps:**
1. [Specific action]
2. [Specific action]
3. [Specific action]

**Expected outcome:** [What this achieves]

---

## 3. Predicted Next Moves

### Prediction 1: [What they'll likely do]
**Confidence:** High/Medium/Low
**Supporting signals:**
- [Signal 1 with source]
- [Signal 2 with source]

**Implication for you:** [How to prepare/respond]

### Prediction 2: [What they'll likely do]
**Confidence:** High/Medium/Low
**Supporting signals:**
- [Signal 1 with source]
- [Signal 2 with source]

**Implication for you:** [How to prepare/respond]

---

## 4. Information Gaps
Metrics and data that could not be verified:
- [Item 1]
- [Item 2]

**Suggested next steps to fill gaps:**
- [How to find this information]

Quality Checklist (Self-Verification)

Before finalizing, verify ALL of the following:

Research Check

  • I performed web searches (did not rely on training data alone)
  • I searched Crunchbase, LinkedIn, G2/Capterra, and news sources
  • I searched traffic/SEO sources (Similarweb, Ahrefs, Semrush, Google Trends)
  • I checked BuiltWith for tech stack and GitHub for development signals
  • I searched Meta Ads Library for advertising activity
  • I searched for both positive and negative signals

Metrics Check

  • Every metric has a source URL or is marked "Not publicly available"
  • No numbers are estimated or assumed
  • Dates are included for data freshness

Strategy Check

  • All 3 strategies exploit verified weaknesses (not assumptions)
  • Each strategy has concrete, actionable steps
  • Strategies are realistic for a startup to execute

Prediction Check

  • Each prediction cites specific signals
  • Confidence levels are honest (not all "High")
  • Implications are actionable

Output Check

  • Output matches the Output Format exactly
  • Tone is analytical, not inflammatory
  • Information gaps are acknowledged

If ANY check fails → revise before presenting.


Defaults & Assumptions

Use these unless overridden:

  • Assume user is a startup founder analyzing a direct competitor
  • Focus on actionable intelligence (not academic analysis)
  • Prioritize recent data (< 12 months old)
  • Default confidence for predictions: Medium (unless strong signals exist)
  • If industry unknown, infer from competitor's website/positioning

Document any assumptions made in the output.


平台分布

Codex

36.05%
按下载量换算545

Claude

28.45%
按下载量换算430

Cursor

18.26%
按下载量换算276

Gemini CLI

9.18%
按下载量换算139

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills