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

competitor-intel竞争对手英特尔

Agent Skill

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

总安装

4,725

周安装

193

GitHub Stars

141

下载量

1,513
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

用于查找、检索和筛选相关信息。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

  • 适合在关键词搜索或任务场景中快速定位候选结果。
  • 可结合来源仓库 README 继续核验具体用法。
  • 安装前建议确认权限范围、维护状态及是否会触发联网或文件操作。
  • competitor-intel 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

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.


适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

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 复核。

安装前确认

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

来源信息

继续浏览同类 Skills