charlieviettq/awesome-agent-skill / .claude/skills/biz-pestel
"biz-pestel"
Verified"Apply PESTEL framework to scan the macro-environment across Political, Economic, Social, Technological, Environmental, and Legal dimensions. Use this skill when the user needs to assess external macro factors affecting a business, industry, or market — especially before entering a new country, launching a product, or evaluating regulatory risk. Also use when the user mentions 'macro analysis', 'external environment', or 'what trends should we watch'.".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.0 KB |
| examples/sample_scenario.md | markdown | 9.8 KB |
| references/data-sources.md | markdown | 15.6 KB |
| references/framework-comparison.md | markdown | 9.4 KB |
references/framework-comparison.md
View on GitHub# Framework Comparison: PESTEL vs. Adjacent Strategy Tools
## The Level-of-Analysis Problem
The most common mistake is applying the wrong framework at the wrong level. Before picking a tool, identify **what level you're analyzing**:
| Level | Question | Primary Tool |
|-------|----------|--------------|
| Macro-environment | What external forces affect the whole market? | PESTEL |
| Industry | How competitive is this industry? | Porter's Five Forces |
| Company | Where are our strengths and risks? | SWOT |
| Portfolio | Where should we invest or divest? | BCG Matrix |
These levels nest: PESTEL feeds Five Forces feeds SWOT. Running them out of order wastes effort.
---
## PESTEL vs. Porter's Five Forces
### What each measures
**PESTEL** — forces *outside* the industry that no competitor controls. A new data privacy law affects every firm equally. A 2% rate hike hits every borrower. These are givens; firms adapt or don't.
**Porter's Five Forces** — forces *inside* the competitive structure of a specific industry. Buyer power, supplier power, threat of entrants, threat of substitutes, rivalry. These differ across industries and can be influenced by individual firms.
### The handoff point
PESTEL factors become Five Forces inputs when they shift competitive structure:
```
PESTEL observation:
"Taiwan government requires 90-day local data residency (Legal, High impact)"
Flows into Five Forces as:
Threat of New Entrants ↓ — compliance cost raises barrier for foreign entrants
Supplier Power ↑ — local cloud providers gain leverage over foreign ones
Rivalry ↑ — incumbents with existing local infrastructure have
temporary advantage, intensifying competitive response
```
**Decision rule:**
- If the factor affects *all firms in the market equally* → PESTEL
- If the factor changes *bargaining relationships or barriers* between specific groups → Five Forces
- If the factor affects *one firm's position* → SWOT
### Worked example: EV market in Southeast Asia (2025)
| Factor | PESTEL or Five Forces? | Reason |
|--------|----------------------|--------|
| Regional governments offering EV purchase subsidies | PESTEL (Political) | Affects all EV sellers equally |
| ASEAN battery raw material export controls tightening | PESTEL (Political + Legal) | Macro policy, not company-specific |
| Chinese OEMs entering at 30% lower price point | Five Forces (Rivalry + New Entrants) | Specific competitive dynamic within the industry |
| Battery suppliers consolidating to 3 global firms | Five Forces (Supplier Power) | Structural shift in bargaining relationships |
| Consumer trust in EV safety varies by country | PESTEL (Social) if industry-wide; Five Forces (Buyer Power) if it's affecting switching behavior between specific brands | Context-dependent — see rule above |
---
## PESTEL vs. SWOT
### Structural relationship
SWOT has two halves:
- **External half** (Opportunities + Threats) — these come from PESTEL and Five Forces
- **Internal half** (Strengths + Weaknesses) — these come from internal audit (resources, capabilities, financials)
PESTEL is the *upstream input* to the Opportunities/Threats cells of SWOT. Running SWOT without a PESTEL scan typically produces vague O/T entries like "regulatory changes" or "technology disruption" — too generic to act on.
### Mapping PESTEL → SWOT
```
PESTEL factor → SWOT entry
────────────────────────────────────────────────────
E: Vietnam GDP growing 6.5%, rising → Opportunity: addressable market
middle-class consumer spending expanding faster than forecast
(World Bank, 2024)
L: Food safety Decree 15/2018 → Threat: 6-month approval cycle
requires in-country lab testing delays market entry; competitors
for foreign food products already registered gain 1-season lead
T: Cold chain underdeveloped outside → Threat (if you rely on cold chain)
major cities (30% coverage) OR Opportunity (if you can build
refrigerated logistics as moat)
```
The same PESTEL factor can map to Opportunity or Threat depending on the company's internal position — which is precisely why SWOT needs PESTEL *and* an internal audit.
### When to skip PESTEL and go straight to SWOT
If the scope is entirely internal ("audit our operations", "assess our team capabilities"), PESTEL adds no value. PESTEL is relevant only when the analysis has an external, market-facing dimension.
---
## PESTEL vs. STEEP / STEEPLE / PEST
These are variants, not competing frameworks:
| Acronym | Dimensions | When to prefer |
|---------|-----------|----------------|
| PEST | Political, Economic, Social, Technological | Quick scan, 4 dimensions easier for workshops |
| STEEP | Social, Technological, Economic, Environmental, Political | Environmental-first ordering, used in sustainability contexts |
| STEEPLE | + Legal + Ethical | When ethical/CSR dimension needs explicit treatment (pharma, AI) |
| PESTEL | Political, Economic, Social, Technological, Environmental, Legal | Standard; Legal and Environmental are separated for regulatory-heavy sectors |
**Practical rule:** Use PESTEL by default. Add Ethical as a 7th dimension only when:
- Operating in pharma, AI, financial services, or extractive industries
- The assignment explicitly requires ESG or stakeholder ethics assessment
Do not use PEST when Legal and Environmental factors are material — you will lose them.
---
## PESTEL vs. Scenario Planning
PESTEL is a *current-state scan*. Scenario planning asks *what if macro factors shift in combinations*. They complement each other:
```
Step 1 — PESTEL scan
Identify current state of each dimension + direction of change
Example: "Interest rates high but likely to drop 2026"
Step 2 — Identify 2 high-uncertainty, high-impact axes
(typically drawn from PESTEL Political and Economic)
Axis A: Geopolitical stability (stable ↔ fragmented)
Axis B: Regional economic growth (accelerating ↔ stagnating)
Step 3 — Build 4 scenarios from 2×2 matrix
Quadrant 1: Stable + accelerating → "Golden decade"
Quadrant 2: Stable + stagnating → "Managed decline"
Quadrant 3: Fragmented + accelerating → "Turbulent growth"
Quadrant 4: Fragmented + stagnating → "Crisis mode"
Step 4 — Test strategy robustness across all 4 scenarios
```
PESTEL without scenario planning assumes the current trajectory holds. Use scenario planning when:
- Time horizon > 3 years
- Political or technological uncertainty is rated High
- Strategy commits significant capital that is hard to reverse
---
## Quick-Selection Decision Tree
```
Is the question about external forces affecting a market?
│
├── YES → Are the forces about ALL firms or the competitive structure?
│ │
│ ├── All firms equally → PESTEL
│ │
│ └── Bargaining / barriers between specific groups → Porter's Five Forces
│
└── NO → Is the question about one company's position?
│
├── Internal capabilities + external position → SWOT
│ (run PESTEL first to populate O/T cells)
│
└── Capital allocation across product lines → BCG Matrix
```
---
## Combined Usage: Recommended Sequence for Market Entry Analysis
For a full market entry assessment, use frameworks in this order to avoid rework:
1. **PESTEL** — Scan the target country's macro-environment. Identify material factors per dimension (2-4 each). Rate impact × likelihood. Flag top 5.
2. **Porter's Five Forces** — Analyze the specific industry in that country. Use PESTEL outputs to calibrate threat of entry (Legal/Political barriers), supplier power (supply chain concentration from Economic/Political), substitutes (Technological).
3. **SWOT** — Place the entering company against findings from steps 1-2. Opportunities and Threats cells are populated from PESTEL + Five Forces. Strengths and Weaknesses from internal audit.
4. **Scenario Planning** (optional) — If PESTEL reveals ≥2 high-uncertainty dimensions, build 4 scenarios before finalizing strategy.
Skipping step 1 and going directly to SWOT is the most common failure mode in market entry analyses — it produces generic threats ("political instability", "competition") without grounding in observable evidence.
---
## Boundary Cases
### "Data privacy regulation" — PESTEL or Legal competitive advantage?
GDPR-equivalent regulation is **PESTEL (Legal)** when:
- It applies to all market participants equally
- You are assessing whether to enter the market
It shifts to **Five Forces (Barrier to Entry)** when:
- Incumbents have already built compliant infrastructure
- Compliance cost is a structural barrier new entrants must overcome
Both statements can be simultaneously true. Record it in PESTEL first; then note the Five Forces implication explicitly.
### "Competitor launched AI product" — PESTEL or Five Forces?
One competitor's product launch is **Five Forces (Rivalry)** — it's a competitive action within the industry.
If AI adoption is becoming an industry-wide baseline (e.g., "80% of firms now use LLM-based customer service per Gartner 2025"), it crosses into **PESTEL (Technological)** — a macro-level shift affecting all players' cost and capability baseline.
Rule of thumb: one firm's action → Five Forces. Industry-wide diffusion → PESTEL.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |