Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Porters Five Forces

ASecurity

Porter's Five Forces — analyze the competitive intensity and attractiveness of an industry. Use when evaluating a new market entry, understanding why margins are under pressure, designing a defensive strategy, or auditing strategic positioning at industry level.

847 stars
0 votes
0 copies
1 views
Added 5/29/2026
ai-agentspythongobashapiperformance

Works with

api

Security Analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned 5/29/2026

$npx -y skills add borghei/Claude-Skills --skill porters-five-forces --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Porters Five Forces?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Porters Five Forces
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/borghei-porters-five-forces/badge)](https://www.skillsdirectory.com/skills/borghei-porters-five-forces)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: porters-five-forces
description: >
  Porter's Five Forces — analyze the competitive intensity and
  attractiveness of an industry. Use when evaluating a new market entry,
  understanding why margins are under pressure, designing a defensive
  strategy, or auditing strategic positioning at industry level.
license: MIT + Commons Clause
metadata:
  version: 1.0.0
  author: borghei
  category: project-management
  domain: strategy-frameworks
  updated: 2026-05-27
  python-tools: five_forces_scorer.py
  tech-stack: porters-five-forces, industry-analysis, competitive-strategy
---

# Porter's Five Forces

Michael Porter's framework for analyzing the structural attractiveness
of an industry. Reveals where profit pools form, why some markets are
chronically unprofitable, and where strategic positioning has leverage.

## When to use this skill

- **Market entry** decision (which industry to play in)
- Diagnosing **chronic margin pressure** (why are we squeezed?)
- **Strategic positioning** (where to invest, where to defend)
- **Competitive response** planning
- **M&A target evaluation** (industry attractiveness)
- **Pre-fundraise** industry framing

## The 5 forces

1. **Threat of new entrants** — how easily can newcomers join?
2. **Bargaining power of suppliers** — how concentrated/critical are inputs?
3. **Bargaining power of buyers** — how concentrated/price-sensitive are customers?
4. **Threat of substitute products** — what alternatives could replace the category?
5. **Competitive rivalry** — how intense is competition between existing players?

Plus (Porter's later addition):
6. **Complementors** (the "sixth force") — do partners increase total industry value?

## Scoring rubric

Each force is rated **low / medium / high** based on specific factors:

### 1. Threat of new entrants — high when:
- Low capital requirements
- No regulatory barriers
- No proprietary tech / patents
- Low switching costs
- No economies of scale
- No brand loyalty
- Access to distribution is easy
- Network effects absent

### 2. Supplier power — high when:
- Few suppliers / concentrated supply base
- Suppliers are critical / cannot be substituted
- Switching cost is high
- Suppliers can forward-integrate
- Industry is not a large customer for supplier

### 3. Buyer power — high when:
- Few buyers / concentrated demand
- Buyers purchase in large volumes
- Product is undifferentiated
- Switching cost is low
- Buyers can backward-integrate
- Buyers have full information
- Buyers face thin margins (price pressure)

### 4. Threat of substitutes — high when:
- Many substitutes exist
- Substitutes have favorable price-performance
- Switching cost to substitute is low
- Buyer propensity to substitute is high
- Substitute industry is growing fast

### 5. Competitive rivalry — high when:
- Many similar-sized competitors
- Low growth industry (zero-sum)
- High fixed costs (drive volume)
- Low differentiation
- High exit barriers
- Strategic stakes high

## Workflow

### Step 1 — Define the industry
Industry definition is the most-frequent source of error.
- "Software" is too broad
- "B2B SaaS" is too broad
- "Mid-market HR analytics SaaS" is workable
- "Enterprise revenue intelligence tools (Gong, Outreach, Salesloft-tier)" is precise

### Step 2 — Score each force
Use the rubric. Each force gets low / medium / high + evidence.

### Step 3 — Identify the dominant force(s)
Usually 1-2 forces dominate. They drive the industry's profit pool.

### Step 4 — Translate to strategy
Each force suggests strategic moves:

| Force | High = unfavorable | Strategy implications |
|-------|---------------------|------------------------|
| New entrants | Easy entry | Build barriers (brand, scale, network, switching cost) |
| Supplier power | Concentrated | Diversify, integrate backward, build alternative supply |
| Buyer power | Concentrated | Diversify customer base, differentiate, integrate forward |
| Substitutes | Strong substitutes | Differentiate, raise switching cost, defend value prop |
| Rivalry | Intense | Differentiate, niche down, exit, consolidate |

### Step 5 — Run `five_forces_scorer.py`
Audit for: missing evidence, generic factors, missed sub-factors, no
strategy implications drawn.

```bash
python3 project-management/strategy-frameworks/porters-five-forces/scripts/five_forces_scorer.py \
  --input forces.json --format markdown
```

## Common engagements

### "Should we enter market X?"
1. Define X precisely.
2. Score each force.
3. Identify dominant force.
4. Assess: can we differentiate against the dominant force?
5. If yes, structure entry to counter that force; if no, don't enter.

### "Why are our margins under pressure?"
1. Score industry today vs 3-5 years ago.
2. Identify the force(s) that shifted (usually buyer power or rivalry).
3. Identify which factor specifically caused the shift.
4. Address: product differentiation, switching cost, customer concentration, etc.

### "Audit our strategic position"
1. Score industry forces.
2. For each high force, identify how we currently counter it.
3. Identify weak counters; recommend reinforcement.

## Anti-patterns to avoid

- **Industry defined too broadly.** Yields generic analysis.
- **Industry defined too narrowly.** Misses substitute threats.
- **Each force = "medium".** No analysis happened.
- **No evidence cited.** Just opinion.
- **No strategy implications.** Just a score; not actionable.
- **Static analysis.** Industries evolve; refresh every 12-18 months.
- **Mixing internal capabilities with industry analysis.** Five Forces is industry-level; capabilities are firm-level (see SWOT).

## References

- `references/five-forces-deep.md` — each force, factors, examples
- `references/five-forces-and-strategy.md` — translating to strategic moves

## Related skills

- `project-management/strategy-frameworks/swot-analysis` — firm-level positioning
- `project-management/strategy-frameworks/ansoff-matrix` — growth options
- `project-management/strategy-frameworks/business-model-canvas` — operational view
- `marketing/competitive-teardown` — competitor-specific analysis
- `c-level-advisor/ceo-advisor` — strategic context

Attribution

borgheiborghei
View sourceSee grades on GitHubMore from borghei →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →