Run pestle analysis
Skill eugenelim/agent-ready-repo/packs/product-strategy/.apm/skills/run-pestle-analysis
Use when a strategist needs to scan the macro environment before setting strategy or evaluating market entry. Triggers on "run a PESTLE", "I need to understand the macro environment", "political economic social analysis", "macro scan", "what external forces affect us". Produces a committed macro-environment artifact. Do NOT use as a substitute for current intelligence — PESTLE organizes and prioritizes information you supply; it does not generate market research.From its SKILL.md
npx -y skills add eugenelim/agent-ready-repo --skill run-pestle-analysisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.8 KB, 700 tokens by cl100k_base, as published. Nobody here has run it
Skill: run-pestle-analysis
Produces a macro-environment analysis using the PESTLE framework — Political, Economic, Social, Technological, Legal, and Environmental dimensions. PESTLE is a structured scan; it surfaces which macro forces are most material to the strategic context and in what time horizon. See references/agentbundle-layout.md for artifact path.
When to invoke
- A scope is defined — geography, industry, and time horizon must be named before the scan begins. A global PESTLE for an indeterminate horizon is not useful.
- You are upstream of a market or strategic decision — PESTLE informs positioning, entry, and risk assessment; it is not an operational tool.
- No current PESTLE exists for this scope — amend rather than duplicate.
Procedure
- Establish scope. Name the geography (country, region, or global), the industry, and the time horizon (near-term: 0–18 months; medium-term: 18 months–3 years; long-term: 3+ years). These anchors determine what is material for each dimension.
- Assess Political. Government stability, policy direction, trade agreements, tariffs, political risk. Name at least one current policy or regulatory signal that affects this industry and geography.
- Assess Economic. GDP trajectory, inflation, interest rates, consumer confidence, exchange rates, labor market tightness. Name at least one macroeconomic indicator that is currently moving and its directional impact.
- Assess Social. Demographic shifts, consumer behavior trends, cultural values, education and workforce composition. Identify at least one social trend that creates a strategic opportunity or risk.
- Assess Technological. Technology adoption curves, emerging platforms, automation, digital infrastructure, R&D investment trends. Name the technology that poses the greatest disruption risk or opportunity in the time horizon.
- Assess Legal. Regulation, compliance requirements, IP environment, data protection laws, antitrust considerations. Flag any pending regulatory change that could alter the competitive landscape.
- Assess Environmental. Climate regulation, ESG expectations, resource scarcity, supply-chain environmental risk, physical climate exposure. Rate materiality to the business model.
- Prioritize by impact and time horizon. From the six dimensions, identify the top two or three forces by strategic materiality. For each, assign a time horizon tag (near-term / medium-term / long-term) and a directional impact (tailwind / headwind / neutral). These priorities feed into SWOT Opportunities/Threats and OKR cascade context.
- Resolve the artifact path following
references/agentbundle-layout.md. Surface the path, then commitmacro-environment.mdwith frontmattertype: macro-environment.
Anti-patterns
- PESTLE as a forecast. Each dimension describes observable forces, not predictions. Flag uncertainty rather than stating projections as fact.
- Shallow dimension entries. Each dimension needs at least one named, concrete signal — a law, a rate, a trend. "Social factors may affect us" is not an assessment.
- Missing prioritization. A PESTLE with six equally-weighted dimensions gives strategy nothing to act on. The step-8 prioritization is the deliverable, not the scan.
What ships with it: 3 files
6.2 KB alongside SKILL.md
evals/
- eval_queries.json1023 B
- evals.json1.8 KB
references/
- agentbundle-layout.md3.4 KB