pestel-delta-monitor
Quarterly re-scan of a prior PESTEL analysis
Install / Use
npx skills add deanpeters/Product-Manager-Skills --skill pestel-delta-monitorInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OperationsSupported Platforms
Tags
Our assessment of pestel-delta-monitor
pestel-delta-monitor scores 81/100 on our quality scale, 635th of 746 Operations skills we index.
Its SKILL.md is 9.6 KB long, well organised into 17 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 7,063 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 3 months ago, so pestel-delta-monitor is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
pestel-delta-monitor compared with similar skills
All 4 of these similar skills score higher than pestel-delta-monitor; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| pestel-delta-monitor (this skill)by deanpeters | 81 | 7.1k | 3mo ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install pestel-delta-monitor?
- Run
npx skills add deanpeters/Product-Manager-Skills --skill pestel-delta-monitor. The install tabs above show the steps for each supported agent. - Which AI agents does pestel-delta-monitor work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is pestel-delta-monitor safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is pestel-delta-monitor still maintained?
- The repository was last updated about 3 months ago, so pestel-delta-monitor is actively maintained.
Skill content
View source on GitHubname: pestel-delta-monitor argument-hint: "[prior PESTEL analysis, and any suspected events since]" description: "Quarterly re-scan of a prior PESTEL analysis. Use when checking which macro factors moved, which assumptions broke, and what's new — turning PESTEL from a workshop artifact into a radar." intent: >- Refresh a PESTEL analysis by diffing each factor against the prior run and reporting material movement only — regulation passed, thresholds crossed, technology matured, assumptions broken. Macro factors move slowly; the value is catching the two that moved, not re-debating the twenty that did not. type: workflow theme: market-intelligence best_for:
- "Keeping a PESTEL analysis alive on a quarterly cadence instead of letting it rot in a deck"
- "Catching which macro assumptions your strategy quietly depends on — and which just broke"
- "Feeding regulatory and macro shifts into roadmap and OKR conversations with citations" scenarios:
- "Here's the PESTEL we did in Q1 — what's moved since?"
- "A new regulation just passed in our space; re-run the macro scan against our baseline" estimated_time: "15-30 min per run"
PESTEL Delta Monitor
Purpose
Refresh a PESTEL analysis by diffing each factor — Political, Economic, Social, Technological, Environmental, Legal — against the prior run and reporting material movement only: search plan → factor-by-factor diff → broken assumptions → new entrants to the frame → next-step options. Macro factors move slowly, which is exactly why teams stop looking; the value of a cadence is catching the two factors that moved, not re-debating the twenty that didn't. Diffing also reveals which baseline entries were live assumptions versus furniture — broken assumptions are the real output.
Input
Works best with: the prior PESTEL analysis (pasted or attached) and the product/market scope it covered — this skill requires a baseline to diff against. Also useful: any events since the last run you already suspect matter — they get checked first.
Input supplied inline with the invocation — text after the skill name, a pasted context dump, or an
appended ARGUMENTS: line — counts as answers already given. Use it against the question budget;
don't re-ask.
Arriving empty-handed? This is the one investigation skill with a hard prerequisite: with no
baseline, it recommends running pestel-analysis first and stops —
there is nothing to diff. (That referral is the empty-handed path: you leave knowing exactly what
to do first.)
Example invocation: PESTEL delta against the attached Q1 analysis — scope is our EU payments product; I suspect the new AI liability directive matters.
Key Concepts
- Governing protocol: honors the
autonomous-investigationcontract — question budget of 2, search-plan gate, Fact/Inference/Assumption labels, Just Enough Mode, stable schema, 4-option Final Step. Disciplines: GEOINT/DEMOINT statistics plus FININT regulatory sources (seeintelligence-collection-disciplines); this is the annual/quarterly layer of the fusion cadence. - Materiality for macro factors: regulation passed or credibly proposed, macro indicators crossing thresholds your baseline named, technology maturation with adoption evidence, social signals with data behind them. "No material movement" per factor is a valid and common result — a quiet quarter reported honestly keeps the radar trusted.
- Broken assumptions are the headline. A baseline entry now contradicted by evidence outranks ten new observations, because strategy was built on it. The diff exists to find these.
- Assumptions vs. furniture. Entries that never move and touch no decision were furniture — flag them for retirement at the next baseline refresh rather than re-scanning them forever.
- Scope changes break diffs. New market, pivot, fundamentally different business context → redo the full PESTEL; never diff across a scope change.
- Do-not-invent list: regulations, statistics, dates, events. Real URLs and dates on everything — invented regulation is this domain's signature fabrication risk.
Application
- Check the prerequisite. No prior PESTEL → recommend
pestel-analysisand stop. Scope changed since the baseline → recommend a fresh full analysis and stop. - Credit inline context, then ask only the unanswered questions (max 2):
- Prior PESTEL to paste?
- Any events since then you already suspect matter?
- Read the prior analysis fully; diff factor by factor — the baseline document is the diff target, not your general knowledge of the macro environment.
- Show the 3-bullet search plan — which factor categories get active searching this cycle (suspected events first), source types (government and regulatory sources, central-bank and statistical data, credible news, industry bodies, standards organizations), fact/inference separation. Continue unless revised.
- Emit the schema below exactly.
Output schema (do not reorder)
# PESTEL Delta Report
## 1. Run Header
**Scope (from prior analysis):** | **Prior analysis date:** | **This run date:**
## 2. Factor-by-Factor Delta
For each of P / E / S / T / E / L:
### [Factor]: [moved / no material movement]
- **What moved:** [1-2 bullets, labeled, cited — only if moved]
- **Prior assumption affected:** [which entry from the baseline]
- **Reading:** [Inference — implication for the product scope]
Keep "no material movement" factors to a single line each.
## 3. Broken Assumptions
- [Baseline entries now contradicted by evidence — the run's most important section; cited]
## 4. New to the Frame
- [Factors absent from the baseline that now warrant a slot]
## 5. So What?
- **3** implications for strategy or roadmap
- **2** factors to watch closely next cycle
- **3** assumptions to validate
Each bullet: label, confidence, URL where relevant.
A copy/paste fill-in version of this schema, with quality checks, lives in template.md.
Final Step (offer exactly 4 options)
- Update the baseline PESTEL with these deltas (new baseline)
- Deep-dive the most consequential moved factor
- Trace the broken assumptions into roadmap or OKR impact
- Set next cycle's watch priorities
Accept 1, 2, 3, 4, 1 and 2, Verbose Mode, or a custom path.
Examples
A factor that moved, traced to its assumption (fictional):
Legal: moved
- What moved: the data-residency provision cleared committee with an 18-month compliance window — Fact ([legislature record, URL, date])
- Prior assumption affected: baseline entry L2 assumed "no residency mandate before 2028," which justified deferring the regional storage architecture
- Reading: the deferral logic is dead — Inference: the architecture decision moves from someday to next two roadmap quarters, and compliance becomes a sales asset in regulated verticals before it's a legal obligation.
A quiet quarter reported honestly: five factors show "no material movement" at one line each; one Economic entry moved (a rate-path shift crossing the baseline's stated budget-gate threshold). The report is half a page. That brevity is the radar working — the reader spends two minutes and knows the strategy's macro floor held except where it didn't.
See examples/sample.md for a complete worked delta run (fictional
trades-software scope) with two broken assumptions traced to their baseline entries and furniture
flagged for retirement. examples/sample-industrial.md runs the
industrial scope, where the hot factors swap — tariffs, energy, disclosure rules — and threshold
crossings are distinguished from broken assumptions.
Common Pitfalls
- Re-debating the unmoved. Rewriting all six factors every quarter turns the radar back into the workshop it was meant to replace. One line per quiet factor — the discipline is the product.
- Materiality inflation. Promoting think-pieces and proposals-going-nowhere into "movement." The bar is passed/credibly-proposed regulation, crossed thresholds, adoption evidence — not discourse.
- Burying broken assumptions. Listing deltas without connecting them to the baseline entries they contradict. The "prior assumption affected" line is what makes a delta actionable.
- Diffing across a pivot. The business entered a new market and the monitor keeps diffing the old scope's factors. Scope change = new baseline, always.
- Invented specificity. A regulation name, effective date, or statistic that doesn't check out. In this domain a fabricated citation isn't just wrong, it's a compliance risk for the reader — the do-not-invent list is load-bearing.
References
pestel-analysis(Component) — builds the baseline this monitor diffs against; the pair turns PESTEL into an operating radarautonomous-investigation(Workflow) — the governing protocolintelligence-collection-disciplines(Component) — GEOINT/DEMOINT statistical sources; regulatory registriesderisk-measurement-advisor(Interactive) — consumes broken assumptions as risk inputscompetitive-intel-watch(Workflow) — the competitor-level sibling of this macro-level watch- Adapted from
market-intelligence/pestel-delta-monitor-prompt.mdin thehttps://github.com/deanpeters/product-manager-promptsrepo.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
