Individual skill
competitive-moat
Identifies which of the seven structural moats a business actually has, pressure-tests each claim against funded copycats and incumbent pivots, and delivers a moat scorecard with one moat to invest in deliberately. Use when someone asks "what's our moat", "is our product defensible", "a well-funded competitor just launched - what protects us", "investors keep asking about defensibility", or "which moat should we build first". Do NOT use for tracking what competitors are shipping and saying - use competitive-intelligence instead - or for finding unserved market segments - use white-space-analysis instead.
skills/competitive-moat/SKILL.md
Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 24
- Repository last updated
- Oct 13, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude Repository topic
- claude-skills Repository topic
- skill-me Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,677 bytes
Read excerpt
# Competitive Moat Analysis
A moat is a structural reason an advantage compounds rather than erodes. Most "moats" founders cite - features, a head start, proprietary data - are things a funded competitor copies in a quarter, and the costly mistake is building a fundraise or a strategy on one of them. This skill separates real moats from wishful thinking and names the one moat worth building deliberately.
## Operating procedure
Run taxonomy before testing, and testing before measurement - you cannot stress-test a moat you have not precisely named, and you should not bother measuring one that fails the adversary test.
### Step 1: Gather inputs
1. The claimed advantages - everything the founder or team believes protects them, verbatim.
2. Business model and stage - who pays, how much, how customers onboard and leave.
3. Competitive set - the funded startups and the incumbents, with rough war chests.
4. Retention data if available - gross retention by cohort age; label estimates as guesses.