| name | competitors-analysis |
| description | Analyze competitor repositories with evidence-based approach. Use when tracking competitors, creating competitor profiles, or generating competitive analysis. CRITICAL - all analysis must be based on actual cloned code, never assumptions. Triggers include "analyze competitor", "add competitor", "competitive analysis", or "竞品分析". |
| zh_description | Analyze competitor repositories with evidence-based approa。 |
| version | 1.0.0 |
| author | seaworld008 |
| source | in-house |
| source_url | |
| tags | ["analysis", "competitors", "growth", "marketing"] |
| created_at | 2026-03-04 |
| updated_at | 2026-03-20 |
| quality | 5 |
| complexity | intermediate |
| context | fork |
| agent | general-purpose |
| argument-hint | [product-name] [competitor-url] |
Competitors Analysis
Evidence-based competitor tracking and analysis. All analysis must be based on actual code, never assumptions.
When to Use
Use this skill when the user wants to:
- analyze a competitor repository with evidence
- create or update a competitor profile
- compare a competing product's technical stack or architecture
- track competitor changes over time using cloned code
Usage
Recommended flow:
clone repo locally
-> inspect source files and metadata
-> cite every factual claim
-> write profile from evidence only
-> run post-analysis verification
CRITICAL: Evidence-Based Analysis Only
在开始分析之前，必须完成以下检查：
Pre-Analysis Checklist
如果以上任何一项未完成，停止分析，先完成克隆操作。
Forbidden Patterns (禁止的表述)
| 禁止 | 原因 |
|---|
| "推测..."、"可能..."、"应该..." | 没有证据支持 |
| "架构图（推测版）" | 必须基于实际代码 |
| "未公开"、"未披露" | 如果不知道就不要写 |
| 不带来源的技术细节 | 无法验证 |
Required Patterns (必须的表述)
| 正确格式 | 示例 |
|---|
| 技术细节 + (来源: 文件:行号) | "使用 better-sqlite3 (来源: package.json:88)" |
| 直接引用 + 来源 | > "description text" (README.md:3) |
| 版本号 + 来源 | "版本 1.3.3 (package.json:2)" |
Analysis Workflow
Step 1: Clone Repository (必须)
mkdir -p ~/Workspace/competitors/{product-name}
~/Workspace/competitors/{product-name}
git git@github.com:org/repo.git
