competitors-analysis
Analyzes competitor projects by examining actual source code rather than relying on assumptions.
Install
mkdir -p .claude/skills/competitors-analysis && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5642" && unzip -o skill.zip -d .claude/skills/competitors-analysis && rm skill.zipInstalls to .claude/skills/competitors-analysis
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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 "竞品分析".Key capabilities
- →Clone competitor repositories
- →Extract project metadata
- →Analyze technical stacks
- →Synthesize competitive landscapes
How it works
It clones repositories into a durable workspace and performs evidence-based analysis by citing specific file lines and commits to support technical claims.
Inputs & outputs
When to use competitors-analysis
- →Analyze competitor tech stack
- →Extract project metadata from repositories
- →Compare architectural patterns
- →Track project version history
About this skill
Competitors Analysis
Build competitor intelligence that can be shared, re-run, and audited later. This skill has two layers:
- Repository evidence: clone or update the competitor code under the durable competitors workspace, then cite facts from actual files and commits.
- Landscape synthesis: explain which product choices the evidence changes, including trade-offs and what would overturn the judgment. Keep positioning, pricing, strengths and gaps as supporting evidence.
This skill intentionally subsumes lightweight "competitor scan" workflows. A scan is useful for the landscape table, but it is not enough for technical conclusions.
Resolve the analysis target (read this first)
The executing agent resolves two separate inputs: the code source to analyze and the our-product context used for comparison. A repository URL identifies the first; a separately typed product name is not required to profile it.
- Honor the current request's explicit product/market and exclusions first. If the caller requests a standalone profile, do not add an our-product comparison.
- Otherwise, read the current project's
AGENTS.md/CLAUDE.mdand follow its product-contract or research entry to confirm the product and analysis scope. The caller's current project is valid context for this invocation. A directory basename alone is not enough; record the authoritative file used to identify it. A delegated caller should pass the project path and relevant entry when available. - A supplied repository URL without a confirmed our-product context selects a standalone Profile. Continue repository analysis; omit comparison and opportunities specific to our product. A missing customer segment does not block code facts or sourced positioning from the repository's own docs.
- For Discover or Landscape, use the explicit request or confirmed current project to establish the scope. If comparison context remains unknown, complete any supplied repository profiles and report the exact missing context to the caller. An interactive host may ask only for the unresolved comparison input; a noninteractive fork reports it without blocking independent profiles.
Stop only when neither an analysis target nor an actionable current-project
scope is available. Report that missing input to the caller. Do not invent a
task, browse $COMPETITORS_BASE to choose an unrelated product, or start discovery
from a self-generated market. A fork receiving neither a task request nor
caller-bound project scope must stop; its inability to ask is not a reason to
reject a supplied repository URL.
Entry Router
Resolve scope above before selecting a mode. A bare repository URL selects Profile, using the confirmed current project for comparison when available. Known competitors are optional for a scoped Discover request.
Use the user's wording and historical qualifiers to choose the path. A request to recap earlier work selects the inventory route before keyword-based discovery:
| User intent | Mode | What to do |
|---|---|---|
| "recap competitors already studied", "回顾已分析的竞品", historical cumulative list | Landscape inventory | Follow historical inventory; reconcile existing records without requiring new profiles or synthesis |
| "find competitors", "竞品有哪些", broad market query for new discovery | Discover | Search GitHub and web sources, shortlist candidates, clone only relevant repositories |
| "add competitor <url>" | Ingest | Clone the repository, record remote + commit, then produce a first profile |
| A repository URL or supplied code package, "analyze competitor", "review this repo" | Profile | Bind the source, read code, write a cited technical profile; compare with the confirmed current product when applicable |
| "compare", "landscape", "opportunities" | Landscape | Ensure each competitor has a profile, then synthesize gaps and opportunities |
| "latest code", "有没有更新" | Update | Pull/fetch existing competitors and report changed commits before analysis |
Before saving source profiles, resolve the user's selected destination. When the request explicitly selects a team collection, read collection destination routing and use its existing producer/review entry. Keep project-specific adoption judgments in the existing project research entry. Without that selection, retain the current project-backed learning and durable source layout below.
Durable Source Layout
Use a durable workspace, not /tmp. The default base is:
COMPETITORS_BASE="${COMPETITORS_BASE:-$HOME/workspace/competitors}"
Directory convention:
$COMPETITORS_BASE/
└── {product-slug}/
├── {owner-repo}/
└── ...
Use owner-repo for GitHub repositories so forks and similarly named projects do
not collide. Derive product-slug from the explicitly named or authoritatively
confirmed current product. If neither applies, use standalone for a supplied
repository URL; this is a storage namespace, not an invented market.
Reuse the matching product directory and clone after checking its remote.
Do not browse other product directories to manufacture the analysis scope.
Preflight
Bind the requested edition to the supplied source before comparing capabilities.
For Git, record the remote and immutable analyzed commit. For an archive or app
bundle, record its origin (or unknown), exact package/member path, content digest,
and evidenced edition/version (or unknown). Keep separately distributed editions
separate; mark each requested edition as found or unresolved. A digest identifies
bytes, not the requested edition, latest release, or completeness of the collection.
Reuse the bound local package; do not clone a substitute repository or copy an
archive merely to satisfy the Git storage convention. Consult prior analysis only
when the request calls for history or reuse.
Apply the following commands to Git sources only.
Before a fetch, clone or other repository write, resolve the caller's configured
COMPETITORS_BASE and its actual filesystem target. Honor an explicit external
volume; an unavailable target is a storage gap, not permission to create a second
internal copy.
When the user or current evidence identifies an active copy/migration, coordinate
with its existing owner before writing either tree. Continue analysis from verified
objects with git --no-optional-locks --no-lazy-fetch ... show / cat-file; retain missing-object
and freshness gaps while other profiles proceed. Resume updates after the owner's
handoff, without taking over copying, deletion or path switching.
An interrupted fetch can change FETCH_HEAD, refs or object packs despite a
failure exit. If it overlaps a migration, inspect the affected paths and give the
owner the exact delta for synchronization and readback. Do not infer zero writes
from the exit status or independently delete partial objects.
For first ingestion or an explicit freshness/update request, establish these facts from commands, not memory:
repo="$COMPETITORS_BASE/{product-slug}/{owner-repo}"
test -d "$repo/.git"
git -C "$repo" remote -v
git -C "$repo" fetch --all --prune
git -C "$repo" log -1 --format='%H%x09%cI%x09%s'
For synthesis or continuation, reuse verified profiles and their pinned commits. Confirm the matching remote and required objects locally; do not fetch or repeat unchanged checks merely because the context was compressed. Refresh only for requested freshness, changed inputs, missing evidence, or an unresolved concern. Record the analyzed commit rather than describing it as current upstream.
If the repository is missing, clone it first. Prefer SSH for GitHub when possible:
mkdir -p "$COMPETITORS_BASE/{product-slug}"
git clone --depth 1 <git-ssh-url> "$COMPETITORS_BASE/{product-slug}/{owner-repo}"
If SSH fails for a public repository, report the failure and retry with the repository's HTTPS URL only when that keeps the work moving.
Discovery Workflow
For Discover or an open-ended Landscape, start from the workflow and business problem being replaced. Treat caller-named products as seeds; examine relevant alternatives with different ways of organizing the same work. For agent coordination, these might include persistent personal/team assistants, task platforms, native parent/subagent teams or messaging/task primitives. Select only categories that could change the user's choice; do not turn them into a mandatory market-wide checklist. Preserve the explicit scope of a standalone Profile or closed comparison.
Use gh search repos for GitHub repository discovery. Search multiple query
phrases; do not trust one keyword.
gh search repos "product keywords" \
--limit 30 \
--archived=false \
--json fullName,url,description,stargazersCount,forksCount,openIssuesCount,language,pushedAt,updatedAt,defaultBranch
For each candidate, record:
| Field | Source |
|---|---|
| Repository name and URL | gh search repos / gh repo view |
| Description | GitHub API or README line citation after clone |
| Activity | pushedAt, latest commit, release notes if present |
| Stars/forks/issues | GitHub API with retrieval date |
| Why it is relevant | user's product scope + repository evidence |
Clone only candidates that are relevant to the user's product or analysis goal. For broad markets, first present a shortlist with evidence and then analyze the strongest set.
Repository Fact Gathering
Before making mechanism-level claims or our-product gap judgments, read
references/mechanism_evidence.md. Follow its
entry-path, lifecycle and evidence-depth checks while reading the bound source;
apply its execution boundary before running competitor code. A standalone Profile
continues without an our-product baseline.
Read files in this order an
Content truncated.
When not to use it
- →When the target repository is not publicly accessible
- →When the analysis does not require source code inspection
Prerequisites
Limitations
- →Requires local cloning of repositories
- →Technical claims must be supported by file:line citations
How it compares
It enforces an evidence-based approach using actual source code, avoiding the assumptions common in manual competitive research.
Compared to similar skills
competitors-analysis side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| competitors-analysis (this skill) | 1 | 6mo | Review | Advanced |
| literature-review | 559 | 5mo | Review | Advanced |
| openalex-database | 48 | 11mo | Review | Intermediate |
| market-research-reports | 38 | 11mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by daymade
View all by daymade →You might also like
literature-review
K-Dense-AI
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). This skill should be used when conducting systematic literature reviews, meta-analyses, research synthesis, or comprehensive literature searches across biomedical, scientific, and technical domains. Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles (APA, Nature, Vancouver, etc.).
openalex-database
davila7
Query and analyze scholarly literature using the OpenAlex database. This skill should be used when searching for academic papers, analyzing research trends, finding works by authors or institutions, tracking citations, discovering open access publications, or conducting bibliometric analysis across 240M+ scholarly works. Use for literature searches, research output analysis, citation analysis, and academic database queries.
market-research-reports
davila7
Generate comprehensive market research reports (50+ pages) in the style of top consulting firms (McKinsey, BCG, Gartner). Features professional LaTeX formatting, extensive visual generation with scientific-schematics and generate-image, deep integration with research-lookup for data gathering, and multi-framework strategic analysis including Porter's Five Forces, PESTLE, SWOT, TAM/SAM/SOM, and BCG Matrix.
scientific-brainstorming
davila7
Research ideation partner. Generate hypotheses, explore interdisciplinary connections, challenge assumptions, develop methodologies, identify research gaps, for creative scientific problem-solving.
exa-search
benjaminjackson
Search the web for content matching a query with AI-powered semantic search. Use for finding relevant web pages, research papers, news articles, code repositories, or any web content by meaning rather than just keywords.
scientific-critical-thinking
davila7
Evaluate research rigor. Assess methodology, experimental design, statistical validity, biases, confounding, evidence quality (GRADE, Cochrane ROB), for critical analysis of scientific claims.