competitive-advantage

Analyzes and stress-tests competitive advantages using a structured moat evaluation framework.

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/wkentaro/skills --skill competitive-advantage-wkentaro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: competitive-advantage
Source: https://github.com/wkentaro/skills/tree/main/skills/in-progress/competitive-advantage
Command: npx skills add https://github.com/wkentaro/skills --skill competitive-advantage-wkentaro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It helps you determine why a product, company, project, or career actually wins and whether that advantage can survive imitation, substitution, or market change, replacing vague claims with evidence-based moat analysis. ## Core Features & Use Cases - Moat Test Framework: Evaluates each claimed advantage across six dimensions: value, evidence, resistance, accumulation, capture, and durability. - Strategy Stack Design: Builds a coherent set of two to four reinforcing advantages with explicit causal links and flywheel loops. - Adversarial Audit: Attacks the stack by identifying counterstrategies, substitutes, decay risks, and value-capture leaks. - Use Case: A founder asks whether their open-source project's community is a real moat; the skill classifies it as an edge, capability, or moat and names the cheapest counterstrategy a competitor could use. ## Quick Start Use the competitive-advantage skill to analyze whether my product's advantages are defensible moats or just temporary edges.

Frequently Asked Questions about competitive-advantage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze whether a competitive advantage is a real moat?▼

Apply the six-dimension moat test: value, evidence, resistance, accumulation, capture, and durability. An advantage qualifies as a moat only when it demonstrates resistance to imitation or substitution over a stated time horizon; otherwise it is classified as an edge or capability.

What is the difference between an edge, a capability, and a moat?▼

An edge is a current advantage with value and evidence but weak or unknown resistance to copying. A capability is a repeatable ability to produce an outcome. A moat is an edge whose benefit demonstrably resists imitation or substitution over the relevant time horizon.

How do I build a strategy stack for my product?▼

Choose two to four compatible advantages, draw explicit causal arrows between them, and close the loop into a flywheel where evidence supports one. Resolve tensions between opposing strategies, such as affordability versus luxury, by separating them by customer, layer, or phase.

Can this framework analyze open-source projects or careers, not just companies?▼

Yes, the framework applies to products, companies, open-source projects, careers, and communities. You define the arena by naming the contested resource, the real alternatives including non-consumption and substitutes, and the time horizon.

What are common mistakes when claiming a moat?▼

Common failures include treating a visible feature as a moat, collecting catalog labels without causal mechanisms, citing current scale as the explanation, ignoring value capture, and analyzing statically without considering alternatives, environment, and time horizon.