competitive-analysis
Use when performing a structured teardown of a specific competitor's activity system, moat, or vulnerability profile—requires at least one named rival to analyze.
npx skills add majiayu000/claude-skill-registry --skill competitive-analysis-joellewis-skill-library --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## Overview Competitive analysis is not a list of features; it is a forensic audit of a rival's "Activity System" to find where their internal logic is brittle. This skill prevents the "Arrogance Trap" identified in the GE and Boeing collapses by forcing an evidence-based assessment of moats and vulnerabilities. ## Iron Law `NO COMPETITIVE CLAIM WITHOUT EVIDENCE FROM AT LEAST TWO INDEPENDENT SOURCES` Unverified claims about being "10x better" or having "no competitors" are the primary signals of impending strategic failure. ## State Machine ```dot digraph competitive_analysis_flow { "Start" [shape=doublecircle]; "Step 1: Activity Mapping" [shape=box]; "Gate: Moat Audit" [shape=diamond]; "Step 3: Vulnerability Check" [shape=box]; "Step 4: Evidence Gate" [shape=diamond]; "Done" [shape=doublecircle]; "Start" -> "Step 1: Activity Mapping"; "Step 1: Activity Mapping" -> "Gate: Moat Audit"; "Gate: Moat Audit" -> "Step 3: Vulnerability Check" [label="moat verified"]; "Gate: Moat Audit" -> "Step 1: Activity Mapping" [label="unclear value"]; "Step 3: Vulnerability Check" -> "Step 4: Evidence Gate"; "Step 4: Evidence Gate" -> "Done" [label="2+ sources found"]; "Step 4: Evidence Gate" -> "Ste
- Overview
- Iron Law
- State Machine
- When to Use This Skill
- When NOT to Use This Skill
- Core Process
- Step 1: Map the Activity System
- Step 2: Perform the Monopoly Audit
- Step 3: Audit the "Operating System"
- Step 4: Verify with Independent Evidence (The Iron Law)
- Cross-Skill Invocations
- Rationalization Table
- Red Flags
- Diagnostic Checklist
What does the competitive-analysis skill do?
Use when performing a structured teardown of a specific competitor's activity system, moat, or vulnerability profile—requires at least one named rival to analyze.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill competitive-analysis-joellewis-skill-library --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 majiayu000/claude-skill-registry, a repository with 534 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.