Agent skill · research science · daymade
competitors-analysis
Clones and audits competitor repositories into evidence-based intelligence with file:line citations. Use to track competitors, add a competitor repo, review competitor code, compare capabilities, build a competitor landscape, or check for code updates: 竞品分析 / 竞品 / competitor scan / analyze competitor / compare with X / latest competitor code. Not for market research without code (use deep-research).
Why this skill is useful
Adds specific commands and workflows for competitor analysis that the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. About 9k tokens when loaded. Last updated 2026-08-07. 1,320 stars on the source repository.
What this skill does
Competitors Analysis Build competitor intelligence that can be shared, re-run, and audited later. This skill has two layers: 1. Repository evidence: clone or update the competitor code under the durable competitors workspace, then cite facts from actual files and commits. 2. 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. 1. 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. 2. Otherwise, read the current project's AGENTS.md / CLAUDE.md and 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. 3. 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. 4. For Discover or Landscape, use the explicit request or confirmed current project to establish the scope. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daymade/competitors-analysis