Read an industry's structure through Porter's Five Forces with documented signals per rating, ending at the profit pool. Use when weighing market entry or when margins erode and nobody can say why.
npx skills add https://github.com/deanpeters/Product-Manager-Skills --skill porters-five-forces
Read an industry's structure through Porter's Five Forces, with evidence: **search plan →
force-by-force ratings with signals → profit-pool implication → next-step options.** Each force —
competitive rivalry, threat of new entrants, threat of substitutes, buyer power, supplier power — is
rated weak/moderate/strong and justified with documented signals, because a rating without signals is
vibes. The analysis closes where it should have been aiming all along: **where the profit pool sits
and who is squeezing it.** Five forces is an argument about where margin goes, not a diagram for
slide four.
Works best with: the industry or segment, named as precisely as you can ("clinical data
management SaaS," not "healthcare"), and the decision this analysis should support.
Also useful: a geographic boundary if the structure differs by region, and a
market-landscape-scan in session — the forces read builds on
it and searches only gaps.
Input supplied inline with the invocation — text after the skill name, a pasted context dump, or an
appended ARGUMENTS: line — counts as answers already given. Use it against the question budget;
don't re-ask.
Arriving empty-handed? That works too. The skill opens with at most 3 questions (segment,
decision, boundary) and proceeds on labeled assumptions if they go unanswered.
Example invocation: `Five forces on mid-market field-service management software, North America —
decision: whether we enter or partner.`
autonomous-investigationcontract — question budget of 3, search-plan gate, Fact/Inference/Assumption labels, Just Enough
Mode (2-4 signals per force), stable schema, 4-option Final Step. Disciplines: FININT
(concentration, margins, filings) + OSINT (analyst coverage, trade press) per
intelligence-collection-disciplines.
not by how hard incumbents work. Rivalry sets the intensity of margin competition; entry threat
caps pricing; substitutes cap value; buyer power extracts margin downstream; supplier power
extracts it upstream. Structure explains what negotiation skill cannot: **pricing power is
structural.**
signals — concentration data, switching costs, entry examples and how they fared, substitute
adoption curves, margin trends. Forces-with-signals is the difference between naming a framework
and using one.
*the* substitute threat; assess it explicitly in the substitutes force rather than letting the
analysis pretend it's 2015. Supplier power gets the same modern read: cloud, model, and platform
dependencies are supplier concentration.
swot-analysis reads one company's position within it.
run the landscape scan and revisit.
coverage, trade press, pricing pages, funding databases), fact/inference separation. Continue
unless revised. If a landscape scan is in session, build on it; search only gaps.
~~~markdown
As-of date: | Boundary: | Decision supported:
~~~
A copy/paste fill-in version of this schema, with quality checks, lives in template.md.
market-landscape-scan to name the players behind each forceansoff-matrix)Accept 1, 2, 3, 4, 1 and 3, Verbose Mode, or a custom path.
A rating that survives "how do you know?" (fictional):
> ## 4. Buyer Power — strong
> - Signals: top 10 buyers account for ~60% of segment spend — Fact ([trade association data,
> URL]); three publicized incumbent-to-rival switches in 18 months with no reported penalty —
> Fact ([press coverage, URLs]); public rate cards make pricing fully transparent — Fact
> ([vendor pricing pages]); one major buyer built the capability in-house — Fact ([their
> engineering blog, URL])
> - What it means here: buyers can credibly threaten to leave or build, so list-price integrity is
> an illusion in this segment — discounting pressure is structural, not a sales-discipline problem.
The profit-pool close doing its job: rivalry moderate, entrants weak, substitutes strong (AI
agents absorbing the low-complexity tier), buyers strong, suppliers moderate. The pool sits in the
regulated high-complexity tier — the only place two strong forces don't reach — Inference. For
the entry decision: enter *only* via the regulated tier; the volume tier's margin is already spoken
for by buyers below and AI substitution above.
See examples/sample.md for a complete worked five-forces read (fictional
FSM-software market) that builds on the market-landscape-scan example and lands at a profit-pool
close that changes the decision. examples/sample-industrial.md
shows the forces inverting in an industrial market — read both to see the framework adapt instead
of recite.
with URLs, or the whole exercise is a diagram.
eats the category's low end. Name it and rate it, even when the rating is "weak — for now."
what the structure does to everyone who plays. The forces are about margin physics, not rosters.
the analysis; everything above it is evidence assembly.
confident noise. Say "still forming," scan the landscape, revisit in two quarters.
autonomous-investigation (Workflow) — the governing protocolintelligence-collection-disciplines (Component) — FININT/OSINT sources behind the signalsmarket-landscape-scan (Workflow) — who plays; this skill asks what the structure does to themswot-analysis (Workflow) — one company's position within the structureansoff-matrix (Workflow) — growth options informed by the profit-pool readmarket-intelligence/porters-five-forces-prompt.md in thehttps://github.com/deanpeters/product-manager-prompts repo.
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
Take deanpeters/porters-five-forces from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.