mcpbeat Sign in

Biz Pestel Agent Skill

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'.

11k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
223
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/asgard-ai-platform/skills --skill biz-pestel

What comes with it

35 693 bytes besides the instruction
examples/sample_scenario.md
references/data-sources.md
references/framework-comparison.md

The instruction itself

14 sections, as written by the author

PESTEL Analysis

Overview

PESTEL scans the macro-environment across six dimensions to identify external forces that could impact a business or industry. It operates at the macro level — broader than industry (Porter's Five Forces) or company (SWOT). Use it to surface trends and risks the organization cannot control but must respond to.

When to Use

Trigger conditions:

  • User evaluating a new market or country for expansion
  • User needs to understand regulatory, economic, or social trends
  • User wants to identify macro risks before strategic planning
  • User asks "what external factors should we consider?"

When NOT to use:

  • For company-specific assessment → use SWOT
  • For industry competitive dynamics → use Porter's Five Forces
  • For product portfolio decisions → use BCG Matrix

Framework

IRON LAW: Macro-Level Only

PESTEL factors are MACRO-ENVIRONMENT forces — they affect all players in
a market, not just one company. "Our costs are rising" is not a PESTEL factor.
"Inflation is driving up input costs across the industry" is.

Test: "Does this factor affect ALL companies in this market?"
  YES → Valid PESTEL factor
  NO  → It belongs in SWOT or Five Forces, not PESTEL
IRON LAW: Evidence-Based, Not Speculative

Every PESTEL factor must be grounded in observable data, trends, or events.
"Technology might change" is not a factor. "5G rollout reaching 70% coverage
by 2026 (GSMA data)" is a factor.

Step 1: Define the Scope

  • What entity? Country, region, or market being analyzed
  • For whom? Which business or industry perspective
  • Time horizon: near-term (1-2 years) or medium-term (3-5 years)

Step 2: Scan Each Dimension

For each of the six dimensions, identify 2-4 key factors with evidence:

P — Political: Government stability, trade policy, taxation policy, political risk, corruption, foreign investment rules

E — Economic: GDP growth, inflation, interest rates, exchange rates, unemployment, consumer spending power, commodity prices

S — Social: Demographics, cultural trends, consumer attitudes, lifestyle changes, education levels, urbanization, health consciousness

T — Technological: R&D activity, automation, digital infrastructure, emerging technologies, innovation rate, tech transfer

E — Environmental: Climate change, sustainability regulations, resource scarcity, carbon emissions rules, environmental awareness, natural disaster risk

L — Legal: Employment law, consumer protection, data privacy (GDPR, PDPA), industry-specific regulation, IP protection, antitrust

Step 3: Assess Impact and Likelihood

For each factor:

  • Impact on the business: High / Medium / Low
  • Likelihood of change: High / Medium / Low
  • Direction: Favorable (+) or Unfavorable (−)

Step 4: Prioritize and Connect

  • Rank factors by impact × likelihood
  • Identify cross-dimensional connections (e.g., political instability → economic uncertainty → social unrest)
  • Highlight the top 3-5 factors that require strategic response

Output Format

# PESTEL Analysis: {Market/Country} for {Business Context}

## Scope
- Market: ...
- Perspective: ...
- Time horizon: ...

## PESTEL Factors

| Dimension | Factor | Evidence | Impact | Direction |
|-----------|--------|----------|--------|-----------|
| Political | ... | ... | H/M/L | +/− |
| Economic | ... | ... | H/M/L | +/− |
| Social | ... | ... | H/M/L | +/− |
| Technological | ... | ... | H/M/L | +/− |
| Environmental | ... | ... | H/M/L | +/− |
| Legal | ... | ... | H/M/L | +/− |

### Political
{Detailed analysis}

### Economic
{Detailed analysis}

### Social
{Detailed analysis}

### Technological
{Detailed analysis}

### Environmental
{Detailed analysis}

### Legal
{Detailed analysis}

## Priority Factors
1. {Highest impact factor} — {required response}
2. ...
3. ...

## Cross-Dimensional Connections
- {Factor A} → {Factor B} → {combined implication}

Examples

Correct Application

Scenario: PESTEL for Vietnam market, perspective of a Taiwanese food manufacturer (2025-2028)

| Dimension | Factor | Evidence | Impact | Direction |

|-----------|--------|----------|--------|-----------|

| Political | Vietnam-Taiwan informal trade relations stable; no diplomatic friction | Bilateral trade volume growing YoY | Med | + |

| Economic | Vietnam GDP growth 6.5% (2024), rising middle class | World Bank data, urban consumer spending up 12% | High | + |

| Social | Young population (median age 31), increasing demand for packaged food | UN demographic data, urbanization rate 39% → projected 45% by 2030 | High | + |

| Technological | Cold chain logistics still underdeveloped outside Ho Chi Minh and Hanoi | Only 30% of food supply chain has cold storage (VCCI report) | High | − |

| Environmental | Government tightening plastic packaging regulations | Decree on solid waste management (2024) requiring recyclable packaging | Med | − |

| Legal | Food safety registration (Decree 15/2018) requires 6-month approval cycle | Foreign food products need Certificate of Free Sale + lab testing in-country | High | − |

Incorrect Application

Scenario: Same Vietnam market analysis

What went wrong:

  • "Our factory is running at 80% capacity" → Company-level fact, not macro factor. Violates Iron Law: PESTEL is macro-level only.
  • "Technology is changing fast" → No evidence, no specificity. Violates Iron Law: evidence-based, not speculative. What technology? What change? What data?

Gotchas

  • Overlap between dimensions: A factor can span multiple dimensions (e.g., "data privacy law" is both Legal and Technological). Place it where the primary impact lies, and note the connection.
  • Country-level, not city-level: PESTEL typically analyzes national macro factors. If sub-national differences matter (e.g., China's tier-1 vs tier-3 cities), note them as variations within the dimension.
  • Snapshot vs trend: A PESTEL factor should capture the direction of change, not just current state. "GDP is $X" is a fact; "GDP growing at 6.5% with acceleration trend" is a useful factor.
  • Too many factors: Listing 10+ factors per dimension creates noise. Keep to 2-4 per dimension, prioritized by impact.
  • Missing the "So what?": Each factor needs an implication for the business. "Population is aging" without "→ shifting demand toward health products" is incomplete.

References

  • For comparison with other strategy frameworks, see references/framework-comparison.md
  • For country-specific PESTEL data sources, see references/data-sources.md

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

Integration 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.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

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.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

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.

16k tokens
Benchling Integration
by christophacham
×3

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.

14k tokens
Biopython
by christophacham
×3

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.

24k tokens

How to use it

Copy the folder

Take asgard-ai-platform/biz-pestel from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.