competitors-analysis

1# Competitors Analysis
2 
3Build competitor intelligence that can be shared, re-run, and audited later. This
4skill has two layers:
5 
61. **Repository evidence**: clone or update the competitor code under the durable
7   competitors workspace, then cite facts from actual files and commits.
82. **Landscape synthesis**: explain which product choices the evidence changes,
9   including trade-offs and what would overturn the judgment. Keep positioning,
10   pricing, strengths and gaps as supporting evidence.
11 
12This skill intentionally subsumes lightweight "competitor scan" workflows. A scan
13is useful for the landscape table, but it is not enough for technical conclusions.
14 
15## Resolve the analysis target (read this first)
16 
17The executing agent resolves two separate inputs: the **code source to analyze**
18and the **our-product context used for comparison**. A repository URL identifies
19the first; a separately typed product name is not required to profile it.
20 
211. Honor the current request's explicit product/market and exclusions first.
22   If the caller requests a standalone profile, do not add an our-product comparison.
232. Otherwise, read the current project's `AGENTS.md` / `CLAUDE.md` and follow its
24   product-contract or research entry to confirm the product and analysis scope.
25   The caller's current project is valid context for this invocation. A directory
26   basename alone is not enough; record the authoritative file used to identify it.
27…