agentleFS
marcos-spontonmarcos-sponton/frameworks-as-skills/skills/7-powers/SKILL.md

7-powers

Skill1 starsChanged 4 months agoMITView on GitHub

Apply Hamilton Helmer's 7 Powers — the taxonomic framework that names exactly seven conditions capable of producing Persistent Differential Returns (Scale Economies, Network Economies, Counter-Positioning, Switching Costs, Branding, Cornered Resource, Process Power). Use this skill whenever the user is analyzing competitive advantage, moats, or defensibility — evaluating whether a business has real Power vs. a temporary edge, stress-testing a founder's "moat" claim, doing a competitor teardown, judging an investment on durability, mapping which Powers a company can plausibly build at its current stage, or writing/critiquing anything that turns on "why do we (or they) win over time?" Also use whenever the user mentions Hamilton Helmer, Strategy Capital, 7 Powers, "Benefit + Barrier", "Persistent Differential Returns", "Counter-Positioning", or any of the seven Powers by name. Prefer this skill over generic moat/economic-castle talk — Helmer's method is definitional and its power comes from applying the strict Benefit + Barrier test against the exact taxonomy rather than inventing new "moats" ad hoc.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user's situation is ambiguous, ask one clarifying question before running the diagnosis.

    line 29
  2. Distinctive:

    No Barrier → not Power, just a temporary advantage: Every Power in the taxonomy is defined by a *specific* Barrier mechanism.

    line 38
  3. Distinctive:

    Don't invent quotes: When a quote is in the record with attribution, use it verbatim.

    line 87
  4. Distinctive:

    Attribution matters: When quoting Helmer, cite.

    line 88

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

7 Powers

Hamilton Helmer's taxonomic framework for competitive advantage — distilled from the 2016 book 7 Powers: The Foundations of Business Strategy (Deep Strategy LLC) plus a decade of Helmer's post-book work at Strategy Capital, his co-research with Chenyi Shi on "Second Invention" and platform businesses, and ~8 podcast appearances (Acquired 2020 + 2022 + 2023, Invest Like the Best, 20VC, NFX, Venrock, Lenny's Podcast 2024).

This skill helps you think like Helmer, not just list the seven Powers. It's rigorous because Helmer is rigorous: Power is a strictly defined economic condition — Benefit + Barrier, tested against the 3 S's, expressed in cash flow — not a marketing metaphor. Applying the taxonomy loosely produces the exact confusion Helmer built the book to correct.

When this skill activates

Use this skill when the user is:

  • Analyzing whether a specific company has a real, durable moat (or which of the seven they have).
  • Stress-testing a founder's "we have network effects / data moat / brand" claim.
  • Doing a competitor teardown or investment thesis where the question is durability of returns.
  • Deciding which Power a business should aim to build given its stage (Origination / Takeoff / Stability).
  • Critiquing a strategy doc that gestures at "competitive advantage" without naming a specific mechanism.
  • Reading a business through Helmer's lens after a Rumelt-style diagnosis or a Martin-style cascade has surfaced "how do we win?"
  • Comparing two businesses on Power intensity rather than growth or revenue.

Do NOT use this skill when:

  • The user is pre-product/market-fit and still searching. Helmer is explicit that invention drives Power, but "planning rarely creates Power" — pre-PMF founders should be finding a market first. Suggest lean discovery / Rumelt's crux-finding instead.
  • The question is purely operational (throughput, hiring, ops excellence). Helmer specifically distinguishes operational excellence from Process Power — operational questions don't need the 7 Powers.
  • The user just wants a summary of the book. Give the book link (https://www.amazon.com/7-Powers-Foundations-Business-Strategy/dp/0998116319) and don't run the taxonomy.
  • The user wants brand/marketing strategy in general — Helmer's Brand Power is a narrow, durable willingness-to-pay premium, not general brand strategy.

If the user's situation is ambiguous, ask one clarifying question before running the diagnosis.

The framework at a glance

Power — the set of conditions creating the potential for Persistent Differential Returns. Two-part test:

  • Benefit — a material improvement in cash flow relative to competitors (through prices, costs, or investment needs).
  • Barrier — something that prevents competitors from arbitraging the Benefit away.

No Barrier → not Power, just a temporary advantage. Every Power in the taxonomy is defined by a specific Barrier mechanism.

The seven — each with its Benefit + Barrier:

#PowerBenefitBarrier
1Scale EconomiesLower per-unit cost at scaleProhibitive share-gain cost for a smaller rival
2Network EconomiesValue rises with usersWinner-take-most tipping
3Counter-PositioningA new, superior business modelCollateral damage to incumbent's existing P&L
4Switching CostsCustomers face cost/hassle to leaveSame cost/hassle for competitors to poach
5BrandingWillingness-to-pay premium for identical offeringHysteresis — long, path-dependent build
6Cornered ResourcePreferential access to a coveted assetFiat (legal / physical / decreed)
7Process PowerSuperior cost/quality from embedded operationsHysteresis + causal ambiguity

Helmer's one-line definition of strategy: "A route to continuing Power in significant markets."

How to use this skill in a session

  1. Understand what the user is actually doing. Investment analysis? Founder claim stress-test? Own strategy? The move differs. Read references/prompts.md for shape.
  2. Start with the Barrier, not the Benefit. This is Helmer's diagnostic move — Barrier type directly maps to Power type (see the table in references/method.md). If the user says "we win because [reason]", ask what stops competitors from doing the same? The mechanism reveals which Power (if any) is present.
  3. Run the 3 S's screen — Superior, Significant, Sustainable — before declaring any Power. Load references/method.md for definitions and references/heuristics.md for the common misapplications (operational excellence ≠ Process Power; network effects ≠ Network Economies; brand recognition ≠ Brand Power; data scale ≠ Power; speed ≠ Power).
  4. Distinguish Statics from Dynamics. Having Power (Statics) is easy to identify in a mature company. Getting Power (Dynamics) requires invention and is stage-specific — Origination / Takeoff / Stability. Which Powers are on the table depends on where the business is in that arc. Load references/method.md (Dynamics section) and references/heuristics.md (sequencing).
  5. Match Helmer's voice when responding on his framework's behalf. Definitional, investor-oriented, precise. He defines before deploying, contrasts each Power against a look-alike that fails the test, applies the cash-flow lens. He is not opinionated-provocateur (that's Rumelt/Martin territory). Load references/voice-and-tone.md.
  6. Pull post-book material when appropriate. Second Invention (with Chenyi Shi), the three-stage model, Platforms and Power, Power Dynamics investing method. Load references/post-book.md. Note that Helmer has said very little publicly about AI competitive dynamics as such — flag this honestly rather than fabricating.
  7. Cite sources. Book chapter, Acquired episode, Lenny episode, Trium Group interview, Strategy Capital site. When a case comes from a third party applying Helmer's framework (e.g., TSMC/ASML/Nvidia in the AI era), tag it as applied rather than as Helmer's own words.

Deep references (load as needed)

  • references/method.md — the 7 Powers in strict definitions, Benefit + Barrier for each, the 3 S's screen, the Value Axiom, Statics vs. Dynamics, the three-stage sequencing.
  • references/heuristics.md — do's, don'ts, gotchas. Common misapplications (operational excellence, network effects, brand recognition, data scale, speed). The 5 stages of incumbent response to Counter-Positioning. Barrier-first diagnostic table.
  • references/post-book.md — Second Invention research with Chenyi Shi, the three-stage business phase model, Platforms and Power, Power Dynamics, and where Helmer has NOT written (esp. AI-era commentary — flagged honestly).
  • references/author-live-sources.md — index of Helmer's live footprint. Note: podcast-heavy rather than essay-heavy. He has no Substack/Medium/newsletter. Community PRs welcome for new episodes.
  • references/voice-and-tone.md — how Helmer actually talks. Academic-practical hybrid, investor lens, "define-then-deploy", his signature contrasts and equations.
  • references/applications.md — when to reach for 7 Powers, when to reach for Rumelt / Martin / Porter / Buffett instead, and how they compose.
  • references/examples.md — worked cases Helmer uses (Netflix, Intel, Vanguard, Pixar, Toyota, Adobe, Dell, Amazon, LinkedIn, Facebook, Walmart) + post-book (AWS, Nintendo, Nvidia/CUDA) + third-party applications tagged as such (TSMC, ASML, Nvidia AI).
  • references/prompts.md — invocation templates.
  • references/sources.md — everything consulted, with links.

Non-negotiables

  • Fidelity to the seven. The taxonomy is exactly seven — Helmer has not added, renamed, or merged any since 2016. Refinements are to Dynamics (stages, second invention). If a user's claimed "moat" doesn't fit one of the seven, the honest answer is usually: it's not Power, it's a temporary advantage.
  • Benefit AND Barrier — both required. A benefit without a barrier is an operating advantage that arbitrage will erode. Enforce this test.
  • Statics vs. Dynamics. Naming a Power a mature company has is easy (Statics); explaining how to get one is hard (Dynamics). Don't collapse the two.
  • Don't invent quotes. When a quote is in the record with attribution, use it verbatim. Otherwise paraphrase and mark as paraphrase.
  • Attribution matters. When quoting Helmer, cite. When applying his framework to a case he hasn't written about (TSMC, ASML, Nvidia AI era), tag it as applied.

Attribution and acknowledgement

Hamilton Helmer — economist, strategy consultant (co-founded Helmer & Associates 1980; later Deep Strategy LLC), and co-founder of Strategy Capital, an investment firm that operationalizes 7 Powers as an investing method ("Power Dynamics"). Taught strategy at Stanford. Author of 7 Powers: The Foundations of Business Strategy (2016).

This skill is not endorsed by Hamilton Helmer. It's Marcos Sponton's structured reading of Helmer's public work. If Helmer himself (or Chenyi Shi) wants to correct or endorse anything here, PRs welcome.

  • Skill maintained by: Marcos Sponton. Feedback, corrections, and PRs welcome. See the repo's README for how to contribute.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.