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/learnings.md

View on GitHub
# Learnings — assess-moat-sources

Captured lessons from skill use. Add a dated entry per invocation that surfaced something worth keeping.

## Seed entries (from build, 2026-05-18)

- **Power Progression is load-bearing.** A claim that a 2-year-old company has Process Power should fail diagnosis — Process Power requires multi-year compounding. Map every present-Power claim against the industry/company stage.
- **AI is asymmetric, not uniform.** Helmer's 2026 commentary is clear: AI erodes Switching Costs and Branding (info-asymmetry side), reinforces Cornered Resource (data) and Process Power (codification first-mover). Reject one-line dismissals of AI in moat assessment.
- **The benefit + barrier discipline catches 80% of bad Power claims.** Forcing the writer to articulate both for each present Power eliminates the vague "moat" assertions.
- **Cross-skill reconciliation is where consistency lives or dies.** value-chain-profit-pools and moat-sources name the same Helmer Power for the same industry, or one of them is wrong.
- **Roll-up archetype questions need explicit buildability framing.** "Is this Power buildable by a new entrant?" and "by a roll-up?" are different questions with different answers per Power.
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