competitive-research
Competitors, their pricing, flows and reviews, with table stakes split from differentiators.
Scope and positioning lean on a picture of the market, and a competitor table filled from memory looks as confident as a real one. Here every price and quote has a link, and what could not be found goes on a list of gaps.
- 2026
- Claude Code
- Web search, a browser tool
- MIT
View on GitHub (opens in a new tab)
git clone https://github.com/VladPolyakov-art/competitive-research ~/.claude/skills/competitive-researchWhat it writes
Fixed file names, so the other skills in the kit find them without asking. Each file also gets a row in research/INDEX.md.
- research/competitive-analysis.md
- Competitor cards, feature matrix, voice of users, threats, knowledge gaps and sources.
- research/competitive-analysis/screenshots/
- Screenshots of live sites, when a browser tool is available.
How it works
- Direct, indirect, workarounds3-5 direct competitors and 2 indirect ones, including spreadsheets, chat apps and paper. The ones you name are always in.
- No source, no factA price, rating or quote needs a page that was opened. Vendor comparison pages are flagged as interested sources.
- Public part onlyIt does not register, log in or fill in forms on competitor sites. Behind a login it uses docs, pricing pages and reviews.
What the agent does
- ReconnaissanceReads your brief and any sibling files, then asks only what is missing.
- Competitor listDirect and indirect competitors, each with one line on why it is there.
- CardsPositioning, pricing as seen that day, key flows, strong and weak UX.
- Voice of usersRepeated complaints and requests from reviews and forums, each with a link.
- MatrixYes, partial, no or unknown per feature, then table stakes and differentiators.
- Threats and gapsWhat could hurt the product, and a numbered list of what public sources do not show.
Works with the kit
None of these is required. With an empty research/ folder it works from what you give it, and when a sibling’s file is there, it reuses it instead of redoing the work.
Reads
- deep-researchMarket facts and competitor names already found.
- proto-personasWho the user is, in their own words.
- ux-auditObserved UX of a competitor.
Read by
- ux-auditTakes its product list and URLs to audit.
- deep-researchDigs where its gaps are, without repeating it.
- proto-personasNamed competitors and review pains.
- simulated-interviewRealistic pains and the tools a persona uses today.
- feature-researchThe starting point for how others solve a feature.
Part of the Product research kit: six skills, one research/ folder and one set of evidence tags.