Agent skill · Documentation

competitive-analysis

Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations. For a one-off teardown of a single rival use competitor-teardown; for a recurring market briefing use competitive-intelligence-mon

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill competitive-analysis --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 7 KB
Bundled scripts: none
Path: skills/competitive-analysis/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Competitive Analysis Skill Create structured competitive analyses for product decision-making. ## Reads from / Writes to the Brain If a [`professional-brain`](../professional-brain/SKILL.md) (`brain/`) exists, ground in it instead of re-asking for what you already know: - **Read first:** `knowledge/` (market + positioning) and competitor `entities/`. Run `python3 ../professional-brain/scripts/brain_query.py ./brain "<competitor or market>"` and carry each fact's provenance tag through — a competitor claim from a press release is `[external]`, not `[data]`. - **📥 Propose to the Brain:** after producing, propose recording new competitor facts to `knowledge/` (`[external]`) and creating/updating competitor `entities/`. Show them, get a yes, then write with `../professional-brain/scripts/brain_write.py … --commit` (append-only, dry-run by default). ## Required Inputs Ask the user for these if not provided: - **Your product or company** (what you're comparing against) - **Competitors to analyze** (or ask to identify the top 3-5) - **Analysis focus** (full landscape / feature comparison / pricing / positioning / win-loss) - **Audience** (product team / leadership / sales / board) ## P

What's inside
Steps it walks through
  1. Reads from / Writes to the Brain
  2. Required Inputs
  3. Process
  4. Output Structure
  5. 1. Executive Summary
  6. 2. Competitor Profiles
  7. 3. Feature Comparison Matrix
  8. 4. Pricing Comparison
  9. 5. Market Positioning Map
  10. 6. Win/Loss Analysis
  11. 7. Strategic Recommendations
  12. Anti-Patterns
  13. Deeper Materials
  14. Scoring Rubric (0–40)
Ships with 3 files
  • references/feature-matrix-honesty.md
  • references/worked-example.md
  • templates/landscape-doc.md
More from pm-claude-skills
All skills →
About this skill
What does the competitive-analysis skill do?

Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations. For a one-off teardown of a single rival use competitor-teardown; for a recurring market briefing use competitive-intelligence-mon

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill competitive-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going