Free Agent Skill
Moat Analysis
Assess whether a competitive advantage is durable (a real "moat") or temporary, by checking it against the standard sources of durable advantage — switching costs, network effects, economies of scale, brand/trust, and regulatory or IP protection — rather than taking "we're ahead right now" at face value
Use when: The user is evaluating a business, a product's competitive position, a startup idea, an investment, or their own company's defensibility, especially when the current advantage is described in terms of being first, faster, or better rather than structurally harder to copy
Install this skill
Cursor, Claude Code and Codex
- Create a folder named `moat-analysis`.
- Save the skill content below as `SKILL.md` inside that folder.
- Place the folder in `.cursor/skills/` for Cursor or `.claude/skills/` for Claude Code (or the equivalent path for Codex).
- Describe the task normally. Your agent loads the skill when its description matches.
Use this in ChatGPT or Claude (no code)
- Copy or download SKILL.md from this page (or put it in a folder named
moat-analysis). - Zip that folder so the archive contains
moat-analysis/SKILL.md. - In ChatGPT (Business, Enterprise, Edu or Healthcare), upload the zip under workspace Skills. In Claude.ai, add a Skill from the zip where your plan supports Skills.
- Describe the task in plain language — the skill loads when its description matches.
---
name: moat-analysis
description: Assess whether a competitive advantage is durable (a real "moat") or temporary, by checking it against the standard sources of durable advantage — switching costs, network effects, economies of scale, brand/trust, and regulatory or IP protection — rather than taking "we're ahead right now" at face value. Use whenever the user is evaluating a business, a product's competitive position, a startup idea, an investment, or their own company's defensibility, especially when the current advantage is described in terms of being first, faster, or better rather than structurally harder to copy.
---
# Moat Analysis
"We're ahead" and "we have a moat" are different claims. Being first or
currently better is often temporary — a moat is a structural reason a
competitor with equal resources and full knowledge of your position still
can't easily catch up.
## The five structural sources of durable advantage
Check the advantage in question against these, specifically:
**Switching costs.** Would a customer face real cost, risk, or effort to
leave — not just mild preference for the incumbent? Data lock-in,
retraining cost, and integration depth create this; a slightly better UI
does not.
**Network effects.** Does the product get better *for each user* as more
users join, in a way a new entrant can't shortcut? Beware fake network
effects — lots of users isn't the same as the product getting structurally
better because of them.
**Economies of scale.** Does unit cost meaningfully drop as volume grows,
in a way a smaller competitor structurally can't match without first
reaching the same scale?
**Brand / trust.** Would customers pay a premium or default to this
option specifically because of accumulated trust, in a category where
trust is hard to earn quickly (health, finance, safety)? Brand recognition
alone, without a trust-sensitive category, is weaker than it looks.
**Regulatory or IP protection.** Is there a real legal barrier (patent,
license, regulatory approval) that a well-funded competitor can't simply
route around or wait out?
## How to run the analysis
1. State the advantage as currently described by the user.
2. Check it against each of the five sources above — most real advantages
are a combination of one or two, not all five.
3. For each one that seems to apply, ask the stress-test question: "if a
well-funded, competent competitor knew exactly what we're doing and
copied it starting today, what specifically stops them?" A good answer
names a structural reason. A weak answer names a temporary lead
("we're just further along," "we move faster").
4. Be honest about "moats" that are really just current execution
advantages — those are real and valuable, but they erode, and should be
treated differently (as something to keep re-earning) than a structural
moat (something to defend once built).
## Output
Name which of the five sources actually apply, flag any claimed advantage
that's really just a temporary lead, and state plainly whether the
overall position looks durable or needs continued execution to hold.
More free skills
Prompt Refiner
Turns a vague request into an executable brief without silently inventing missing requirements.
Decision Framer
Separates the real choice from noise, then tests options against explicit criteria and uncertainty.
Meeting to Actions
Converts messy notes into decisions, owned actions, deadlines and unresolved questions.
Agent Charter
Write a one-page charter for an AI agent or bot staff member: one job, anti-jobs, what needs human approval, what is never allowed, and how it proves work
Calibrated Forecasting
Turn a vague prediction or unstated confidence level into an explicit, calibrated probability estimate, using superforecasting practices — breaking questions into sub-questions, checking base rates, updating in small increments as new information arrives, and tracking predictions against outcomes
Decision Memo
Structure a real, consequential decision as a written narrative memo — full sentences and paragraphs rather than bullet points, forcing the logic to be checked rather than gestured at, plus explicit classification of whether the decision is reversible (a "two-way door") or not (a "one-way door")
Teachback
Test and build genuine understanding of a concept using teachback — explain it as simply as possible, notice exactly where the simple explanation breaks down, and treat that break point as the thing to actually go learn
First Principles
Rebuild a problem from fundamental truths (physics, economics, unit costs, what's actually true regardless of convention) rather than by analogy to how things are normally done
Focus and Tradeoffs
Cut a bloated plan, roadmap, or list of priorities down to the one or two things that actually matter — real focus means saying no to a thousand things
Jobs to Be Done
Diagnose what "job" a customer is actually hiring a product, service, or workaround to do, using the Jobs-to-be-Done framework — progress in a specific circumstance, forces of progress, switch interview, job statements, and desired-outcome scoring
Mental Models
Apply a latticework of cross-disciplinary thinking tools (inversion, second-order effects, incentives, circle of competence, opportunity cost, base rates) to frame a vague or general problem
Negotiation Prep
Prepare for a high-stakes negotiation or hard conversation using tactical-empathy techniques — labeling emotions, calibrated open-ended questions, mirroring, and getting to genuine "that's right" rather than a grudging "yes."
Postmortem / Retro
Extract a specific, reusable lesson after something succeeded or failed, following the principle that pain plus reflection equals progress — outcomes only compound into better judgment if they're deliberately converted into a written, checkable lesson rather than just felt and moved past
Premortem
Run a premortem — imagine a plan has already failed and work backward to explain why, which surfaces risks that forward planning misses because it counteracts the social and psychological pressure to seem confident
More skills on the way.
Subscribe to How I Grok Bot for new free skills and practical notes on running AI agent workflows.