Agent skill

pestel-delta-monitor

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.

deanpetersgithub.com/deanpetersGitHub ↗
claude-codeNOASSERTION
Install
npx skills add deanpeters/Product-Manager-Skills --skill pestel-delta-monitor --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/pestel-delta-monitor/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 6,255
Language: Shell
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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

What's inside
Steps it walks through
  1. Purpose
  2. Input
  3. Key Concepts
  4. Application
  5. Output schema (do not reorder)
  6. Final Step (offer exactly 4 options)
  7. Examples
  8. Common Pitfalls
  9. References
Ships with 3 files
  • examples/sample-industrial.md
  • examples/sample.md
  • template.md
More from Product-Manager-Skills
All skills →
About this skill
What does the pestel-delta-monitor skill do?

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.

How do I install it?

Run `npx skills add deanpeters/Product-Manager-Skills --skill pestel-delta-monitor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From deanpeters/Product-Manager-Skills, a repository with 6,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going