Skip to content

Agent-Engineer-Master/skill-engineer / strategy/industry-analysis/assess-moat-sources

assess-moat-sources

Unverified

Assesses 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).

references/edge-cases.md

View on GitHub
# Edge Cases — assess-moat-sources

## Multi-Power compounds

Many durable franchises hold MULTIPLE Powers stacked (e.g., Apple = Branding + Switching Costs + Scale + Process Power). The output must enumerate each Power separately with its own benefit/barrier/durability — not collapse them into "Apple has a moat."

## Industries with no identifiable Power

Some industries are structurally unprotected (commodity manufacturing without scale, services without switching costs, fragmented professional services). The valid finding is: "No Power identifiable for any player in this industry; expect persistent ROIC near cost of capital + arbitrage from any pricing anomaly." This flows into a "do not invest for franchise economics" conclusion. Do not invent a Power to fill the slot.

## "Local" Network Economies

Local network effects (city-by-city marketplaces like rideshare) are weaker than global. The diagnostic should distinguish: is the network global (Facebook), continental (Uber-style city-by-city), or hyperlocal (single-venue effects)? Local networks are durable per locality but vulnerable to multi-homing and locality-by-locality competition.

## Regulatory exclusivity in transition

Patents about to expire, licences with finite term, regulatory exclusivity under political review — these are Cornered Resource for the remaining term only. Output must flag the expiry/review date and re-rate durability accordingly.

## Process Power vs flywheel

A "flywheel" (reinforcing loop in user activity → data → product → user) is typically Network Economies + Cornered Resource (data), NOT Process Power. Process Power is about internal operating routines, not external compounding loops. Watch for this conflation.

## Counter-Positioning that becomes Network/Scale

The standard pattern: a Counter-Positioning entrant (Netflix DVD vs Blockbuster) wins, reaches scale, and the durable Power BECOMES Scale or Network Economies (Netflix streaming → content scale). Counter-Positioning is the entry Power; the long-term franchise rests on a different Power. Output should articulate this transition for high-growth industries.

## Two-sided platform asymmetry

In two-sided platforms, switching costs and network economies often sit on one side only (e.g., merchants on Stripe have switching costs; consumers do not). Output must specify WHICH SIDE holds the Power, not assert it globally.

## Roll-up of Process Power holders

A roll-up acquiring a Process Power holder typically LOSES the Power post-close (senior-leader exits, culture dilution, integration disruption). Buildability assessment for roll-up of Process Power = NO by default, requires explicit case for why this acquisition will be different.

## Cross-Power erosion cascade

Erosion of one Power can cascade. Example: AI erodes Branding (info-asymmetry); reduced brand pull raises CAC; raised CAC erodes Scale Economies (advertising scale was a cost-share Power); now both Powers fade. Named-risks section should consider these cascades, not treat each Power's erosion in isolation.

## "Moat-light" archetypes

Some compounders hold no single strong Power but combine several medium ones (e.g., distributors with modest switching costs + density-based scale + local relationships). These are valid but the output must mark each Power as medium-intensity explicitly — not aggregate them into one undifferentiated "moat."
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall