Apply Porter's Five Forces framework to assess industry competitive dynamics and attractiveness. Use this skill when the user needs to analyze an industry's profitability structure, evaluate market entry barriers, assess supplier or buyer bargaining power, or understand competitive intensity — even if they say 'industry analysis' or 'is this market worth entering' without naming Porter's explicitly.
npx skills add https://github.com/asgard-ai-platform/skills --skill biz-porters-five-forces
Porter's Five Forces assesses industry-level competitive dynamics by examining five structural forces that determine profitability. Unlike SWOT (company-level) or PESTEL (macro-level), this framework operates at the industry level — it answers "is this industry attractive?" not "is this company strong?"
Trigger conditions:
When NOT to use:
IRON LAW: Industry-Level, Not Company-Level
Each force describes the INDUSTRY structure, not a specific company's position.
"Our supplier raised prices" is a company event.
"Suppliers in this industry are concentrated with few alternatives" is an industry force.
NEVER analyze a single company's situation — analyze the structural conditions
all players in the industry face.
IRON LAW: All Five Forces, Every Time
Analyze ALL five forces before drawing conclusions. Skipping forces produces
misleading assessments. An industry with low rivalry but high substitute threat
is very different from one with low rivalry and no substitutes.
Before analyzing forces, clearly define:
Getting the boundary wrong invalidates the entire analysis.
Rate each force as High / Medium / Low pressure on industry profitability:
1. Threat of New Entrants — How easy is it for new players to enter?
2. Bargaining Power of Suppliers — Can suppliers dictate terms?
3. Bargaining Power of Buyers — Can customers dictate terms?
4. Threat of Substitutes — Can other products fulfill the same need?
5. Industry Rivalry — How intense is competition among existing players?
Synthesize the five forces into an overall assessment:
Based on the analysis:
# Porter's Five Forces: {Industry} in {Geography}
## Industry Definition
- Industry: ...
- Geographic scope: ...
- Time horizon: ...
## Five Forces Assessment
| Force | Pressure | Key Drivers |
|-------|----------|-------------|
| Threat of New Entrants | High/Med/Low | {top 2-3 drivers} |
| Supplier Power | High/Med/Low | {top 2-3 drivers} |
| Buyer Power | High/Med/Low | {top 2-3 drivers} |
| Threat of Substitutes | High/Med/Low | {top 2-3 drivers} |
| Industry Rivalry | High/Med/Low | {top 2-3 drivers} |
### 1. Threat of New Entrants: {rating}
{Analysis with evidence}
### 2. Bargaining Power of Suppliers: {rating}
{Analysis with evidence}
### 3. Bargaining Power of Buyers: {rating}
{Analysis with evidence}
### 4. Threat of Substitutes: {rating}
{Analysis with evidence}
### 5. Industry Rivalry: {rating}
{Analysis with evidence}
## Overall Assessment
- Industry attractiveness: High / Medium / Low
- Dominant force: {which force most constrains profitability}
- Profitability outlook: ...
## Strategic Implications
1. ...
2. ...
Scenario: Five Forces for the Taiwan bubble tea industry
| Force | Pressure | Reasoning |
|-------|----------|-----------|
| New Entrants | High | Low capital requirements (~NT$500K to open a shop), minimal regulatory barriers, many franchise options available |
| Supplier Power | Low | Tea leaves and tapioca are commodity inputs with many suppliers; no single supplier has pricing power |
| Buyer Power | High | Zero switching costs for consumers, hundreds of options within walking distance, high price sensitivity |
| Substitutes | Medium | Coffee, convenience store drinks, and home-brewed tea serve similar "afternoon drink" need, but bubble tea has strong cultural preference |
| Rivalry | High | Saturated market with thousands of shops, low differentiation among mid-tier brands, frequent price wars |
Overall: Low attractiveness — high entry threat + high rivalry + high buyer power squeeze margins.
Scenario: Same bubble tea industry
What went wrong:
references/framework-comparison.mdIntegration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take asgard-ai-platform/biz-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.