eterdis-environmental-radar — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited eterdis-environmental-radar (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Before anything, look for company-context.md. Read it if available, focusing on: industry, geography, current strategy, the External forces table, the Strategy map, and the Wardley Map section.
If context exists with a populated External forces table, you're in Review mode unless the user explicitly asks for a full scan.
If the External forces table is empty or the file doesn't exist, you're in Diagnostic mode.
If no context file exists at all, ask:
Your business doesn't exist in a vacuum. It exists in a weather system. Political pressure, economic cycles, technology shifts, regulatory changes — these are winds. Some are gusts that pass. Some are prevailing winds that reshape the landscape permanently.
Most environmental analyses get done once, produce a tidy document, and then rot in a drawer while the actual environment keeps moving. That's like checking the weather once and assuming it holds forever.
This is a radar, not a snapshot. You scan, you build a watch list, you check it regularly, you update when things move. The goal isn't a pretty matrix — it's early warning.
Time guidance: Expect to spend at least 20 minutes for the first scan. Reviews should be 10-15 minutes monthly.
First use, or when the world has shifted enough that the old watch list is stale.
Work through all six categories below. For each one, ask open questions — don't lecture. The user knows their industry. Your job is to structure the thinking and poke holes in assumptions.
After scanning all six, run the prioritisation sequence (below) and build the initial watch list.
Pull up the External forces table from company-context.md. For each force on the watch list:
Then ask: "What's new? Anything happening that wasn't on the radar last time?" New forces get assessed through the prioritisation filters and added if they make the cut.
Update company-context.md with any changes — new forces, revised speeds, fired triggers, removed forces that no longer matter.
For each top force, define a specific, observable signal: "We'll know this is moving when [concrete signal]."
Bad trigger: "When regulation changes." That's not a trigger, that's a wish. Good trigger: "When the EU committee publishes draft text on insect feed novel food classification — expected Q3 2026."
These go into the Monitoring trigger column of the External forces table in company-context.md.
Government, policy, and power
Macro forces on demand, cost, and capital
Demographics, values, behavior
New capabilities, disruption, dependency
Spend more time here than the other categories. Technology is the fastest-moving force for most industries right now, and the one most likely to blindside you.
Wardley Map connection: Technology forces are what drive components along the evolution axis. A force here often means a component in your map is about to move — from custom-built toward commodity, or from invisible to table-stakes. If you've run a Wardley Map, check: which components are under pressure from the technology forces you're seeing?
Climate, resources, physical risk
Regulation, liability, compliance
A list of 30 factors is wallpaper, not strategy. Run each one through three filters:
How hard does this hit if it lands? A force that could wipe out 40% of your revenue gets different treatment than one that might shave a margin point. Be specific — "high impact" means nothing. Say what it impacts and by how much.
When does this factor start to bite — or open up? Within 12 months, 1-3 years, or 3+ years?
Here's the trap: factors arriving in 3 years need action now. By the time they're obvious, you're late. Factors arriving in 10 years? Watch them, but don't burn resources yet.
If this hits, can you adapt — or does it permanently change the game? This is the difference between weather and climate. An economic downturn is weather — it passes. Technology substitution and regulatory restructuring are climate — they change the landscape forever. Weight your attention toward the irreversible.
External forces don't float in the abstract — they act ON your business. Specifically, they act on the causal chain in your strategy map:
For each top force, ask: "Where in the chain does this land? And does it threaten the current business, create an opening for the next business, or both?"
If a Wardley Map has been built, check each significant external force against it:
Note any Wardley Map implications in the force assessment. These feed directly into strategic plays.
After prioritisation, land on:
Top 3-5 forces that need action now — with a clear statement of what the threat or opportunity is and why it can't wait. No vague "this is important." Say what it is, what it does, what part of the chain it hits, and why the clock is ticking.
Top 2-3 forces to watch — real but not yet requiring action. For each one, name the specific monitoring trigger.
At least one "next business" opportunity — a macro force that your current organization isn't set up to exploit but that could become a real revenue stream.
Alert triggers for every force on the list — concrete, observable signals. These go into the External forces table in company-context.md.
After every session — diagnostic or review — update the External forces table in company-context.md:
| Force | Category | Speed | Impact on current model | Opportunity? | Monitoring trigger | Last reviewed |
|---|
Also update the Session log with what was covered and when the next review should happen.
No report. Reports go in drawers. Instead, close with:
This skill applies continuous environmental scanning through the lens of Eterdis consulting practice, using the PESTEL framework redesigned for ongoing use rather than one-time analysis. For a deeper engagement, visit eterdis.com or book a conversation at eterdis.com/contact.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.