Agent-Engineer-Master/skill-engineer / strategy/industry-analysis/assess-moat-sources
assess-moat-sources
UnverifiedAssesses which of Helmer's 7 Powers (scale economies, network economies, counter-positioning, switching costs, branding, cornered resource, process power) protect incumbents in a defined industry, how durable each is over the analysis horizon, and which Power combination the winning archetype must hold. Output: moat-sources.md with per-Power present/absent + intensity, benefit + barrier decomposition for each present Power, durability rating (erosion timeframe + vector), buildability for a new entrant or roll-up, winner-archetype Power profile, durability risks, and reconciliation against value-chain-profit-pools.md if present. Sub-skill of analyze-industry; invocable standalone. Triggers on 'assess moat for [industry]', '7 powers analysis of [industry]', 'how durable is the moat in [industry]', 'moat durability [industry]', 'will the moat hold'. Do NOT use for single-company moat (use build-company-model), customer-lock-in only (use analyze-demand), or share analysis (use map-competitive-arena).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.5 KB |
| evals/evals.json | config | 5.7 KB |
| references/anti-patterns.md | markdown | 5.3 KB |
| references/buildability-assessment.md | markdown | 4.7 KB |
| references/durability-assessment.md | markdown | 4.3 KB |
| references/edge-cases.md | markdown | 3.3 KB |
| references/learnings.md | markdown | 1.2 KB |
| references/power-diagnostics.md | markdown | 4.9 KB |
| references/seven-powers-canonical.md | markdown | 8.2 KB |
| scripts/validate_moat.pyexecutable | script | 12.8 KB |
references/power-diagnostics.md
View on GitHub# Per-Power Diagnostic Questions
For each of the 7 Powers, answer these diagnostics before marking **present / absent / nascent**. Each present-Power assertion in the output must reference a passing diagnostic.
## 1. Scale Economies — diagnostic
- What is the minimum efficient scale (MES) in this industry / stage? (Express in $ revenue or unit volume.)
- What is the cost penalty (unit cost % gap) for a player at 50% of MES?
- Among new entrants over the last 5 years, how many reached MES? If none — why?
- Is the cost curve still declining at the largest player's scale, or has it flattened?
**Present test:** MES is large relative to feasible entrant scale AND sub-MES cost penalty is binding (>5% margin compression).
## 2. Network Economies — diagnostic
- Same-side or cross-side network effect? (Buyer-buyer, seller-seller, buyer-seller.)
- Does utility per user increase monotonically with N? (Plot if possible.)
- Is HHI rising over time? Is the #1 player's share increasing?
- Could a niche entrant seed liquidity and grow out? (If yes → network effect is weak / local.)
- Is there a multi-homing tax? (Users on multiple networks → weaker lock-in.)
**Present test:** documented utility curve AND winner-take-most concentration trend AND failed niche-out attempts.
## 3. Counter-Positioning — diagnostic
- Name the incumbent who CANNOT copy. What asset would copying cannibalise?
- Has the incumbent tried and failed, or visibly avoided?
- Is the entrant's new model structurally cheaper or better — quantified?
- What is the incumbent's plausible response window? (Once they DO copy, Counter-Positioning expires.)
**Present test:** named incumbent with named cannibalisation asset + evidence of avoidance OR failed copy attempt.
## 4. Switching Costs — diagnostic
- Estimate the customer's switching cost in $ per account AND hours of internal effort.
- What is the typical contract length / lock-in mechanism?
- What % of new revenue comes from net-new logos vs. expansion in the install base?
- What is the gross churn rate? (Below 5% annual usually signals real switching costs.)
- Are switching costs financial (real $), procedural (re-implementation effort), or relational (sunk-cost / training)? Which?
**Present test:** quantified switching cost > 1× annual contract value OR gross churn <5% AND >70% revenue from existing logos.
## 5. Branding — diagnostic
- Is there a measurable price premium vs an objectively-identical generic offering? (Quantify in %.)
- How long did the brand take to build? Decades → durable; <5 years → fragile.
- Is the brand category-defining or interchangeable with 2-3 peers? (Top-of-mind unprompted recall.)
- Does the brand carry trust/safety associations OR information-asymmetry associations? (Latter erodes faster under AI.)
**Present test:** quantified price premium >10% on identical-spec product AND >10-year build history.
## 6. Cornered Resource — diagnostic
- Name the resource. Name the legal / contractual / geographical / scarcity mechanism that corners it.
- How long does the cornering last? (Patent expiry, lease term, regulatory review cycle, depletion rate.)
- Could a well-funded competitor licence, acquire, or substitute equivalent access? At what cost?
- Is access preferential AND on attractive terms (not just exclusive)?
**Present test:** named resource + named mechanism + cornering duration > horizon OR multi-year remaining OR substitution-cost-prohibitive.
## 7. Process Power — diagnostic
- Name the specific process — NOT "operational excellence" but the named routine (e.g., Toyota's andon-cord-driven kaizen loop; ASML's vendor-managed inventory).
- How many years has the process compounded?
- Has any competitor poached senior leaders from the holder? Did the process transfer? (No transfer = evidence of Process Power.)
- Is the process tacit (embedded in routines / culture) or codified (documented and licensable)?
**Present test:** named process + multi-year compounding + failed replication attempt (poaching or licensing) within the last 5 years.
## Nascent vs Present vs Absent
| State | Definition |
|-------|-----------|
| **Present** | Power exists today; benefit + barrier both demonstrable. |
| **Nascent** | Conditions exist for Power to emerge within horizon, but benefit + barrier not yet both binding. |
| **Absent** | One or both of benefit / barrier missing AND no credible path within horizon. |
The output must mark all 7 Powers in one of these three states. None silently omitted.
## Anti-patterns (REJECTED)
The validator rejects any Power assertion whose justification uses these phrases as load-bearing:
- "first-mover" (alone)
- "differentiation" / "differentiated"
- "adds value" / "value-added"
- "is critical" / "mission-critical"
- "expertise" (alone)
- "relationships" (alone)
- "high quality" / "superior product"
- "complexity" (alone)
- "operational excellence" / "execution" (alone)
Pair these with a named Power if they are part of the evidence chain — never let them stand alone.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |