assess-strategic-environment — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited assess-strategic-environment (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.
For a defined industry, diagnose the competitive environment type using BCG's Strategy Palette. Output: strategic-environment.md naming the environment in one causal sentence, evidencing the three diagnostic dimensions, flagging ambidexterity where present, and emitting a routing matrix that downstream sub-skills consume.
The discipline: Wrong environment diagnosis = wrong toolkit = useless output. A Classical analysis of an Adaptive industry produces a five-year plan that won't survive contact with reality. An Adaptive analysis of a Classical industry produces overcautious wait-and-see recommendations. This skill runs FIRST in the orchestrator chain.
Iron rules:
../_shared/provenance-tagging.md.../_shared/2026-terminology.md.Confirm: industry slug, geographic scope (if relevant — the same industry can sit in different environments in different geos), focal layer (optional but recommended for multi-layer industries — see Five Forces focal-layer discipline). Read references/strategy-palette.md for the framework refresher and references/diagnostic-questions.md for the three-question discipline with per-environment anchors.
Can the trajectory be reliably forecast over a 3-5 year horizon? Rate High / Medium / Low. Evidence anchors (see references/diagnostic-questions.md):
Write 2-3 sentences with ≥1 V/C/A/I-tagged evidence claim. Never assert High predictability for a market with active AI-native disruption.
Can a single player (or coalition) materially shape the industry's structure or rules? Rate High / Medium / Low. Evidence anchors:
Write 2-3 sentences with ≥1 V/C/A/I-tagged evidence claim. Default to Low unless there is named evidence of shaping power — Visionary and Shaping classifications require positive evidence.
Is the industry in a survival-mode constrained environment (capital scarcity, regulatory cliff, demand collapse, cost-curve collapse)? Rate High / Medium / Low. Evidence anchors:
Write 2-3 sentences with ≥1 V/C/A/I-tagged evidence claim. Harshness is rare — Renewal should be called only with named evidence of at least one of these triggers.
Apply the decision rule from references/strategy-palette.md:
| Predictable? | Malleable? | Harsh? | Environment |
|---|---|---|---|
| High | Low | Low | Classical |
| Low | Low | Low | Adaptive |
| High | High | Low | Visionary |
| Low | High | Low | Shaping |
| any | any | High | Renewal |
If the dimensions don't map cleanly, see references/diagnostic-questions.md "Edge cases" — typically the resolution is to declare ambidexterity (step 6) or restate the focal layer.
Write the classification in ONE causal sentence naming all three dimensions: "Industry X is [Environment] because [predictability evidence], [malleability evidence], and [harshness evidence]."
Does the industry genuinely span TWO environments at different layers, geos, or customer segments? If yes, declare it: "Industry X exhibits ambidexterity — the regulated incumbent layer is Classical [evidence]; the agentic-commerce-native layer is Shaping [evidence]." Default is single-environment classification; only flag ambidexterity with named layer/segment evidence. See references/diagnostic-questions.md "Ambidexterity discipline."
Orchestrator-mode signal: when invoked by analyze-industry, ambidexterity in the output triggers the orchestrator's Ambidexterity Checkpoint (a hard stop where the user chooses single-focus / dual analysis / re-scope). Do NOT presume which choice the user wants — write the ambidexterity declaration clearly enough that the orchestrator's checkpoint prompt can render it directly. See analyze-industry/references/gate-prompts.md "Ambidexterity Checkpoint" for the prompt the orchestrator will use.
Is the environment classification stable, or is the industry transitioning? Examples: Classical → Adaptive (AI disruption breaking long-run predictability); Adaptive → Renewal (capital tightening, demand collapse); Visionary → Shaping (first-mover advantage decaying as ecosystem opens). Write one sentence: "Stable" OR "Transitioning from [X] toward [Y] because [evidence]."
Read references/routing-matrix.md. Produce a table mapping the diagnosed environment to weighting designations (heavy / light / skip) for each Phase 1+2 sub-skill: size-market, map-five-forces, map-value-chain-profit-pools, map-competitive-arena, analyze-trajectory, assess-moat-sources, analyze-demand. map-five-forces is never skip — Reeves's contention is that structural analysis is required in every environment.
next_skills YAML blockBecause this skill runs FIRST, next_skills: names the Phase 1+2 sub-skills the orchestrator should dispatch next, ordered by weight (heavy-first):
---
next_skills:
- size-market # always next (calibrates dollar magnitudes)
- map-five-forces # always required (industry structure)
- map-value-chain-profit-pools # always required (profit location)
- [heavy-weight Phase 2 skill per environment]
- [heavy-weight Phase 2 skill per environment]
---At minimum: the three Phase 1 skills plus the environment-specific heavy-weight skills from step 8.
Run python scripts/validate_environment.py --output-path <path> — checks: classification = one of 5 named environments; 3 diagnostic dimensions each present with a tagged sentence; routing matrix present with all 7 sub-skills enumerated and weights assigned; tag coverage ≥3; next_skills: YAML block present with ≥3 entries; direction-of-travel statement present; ambidexterity declared OR explicitly noted as absent. Write to working/strategic-environment.md (orchestrator mode) or standalone/assess-strategic-environment-YYYY-MM-DD.md (standalone mode).
HTML on request (standalone only): markdown is the default and the only format the validator and the orchestrator consume. If the user explicitly asks for an HTML version of a standalone run, then after validation passes, also render the output via the html-output skill and review it per ../_shared/output-conventions.md § "HTML deliverables and quality review". Never produce HTML automatically.
references/diagnostic-questions.md lists 4 anchors per dimension; each rating must cite at least one with a tag.map-five-forces must never be skip.map-five-forces is never weighted "skip" in any environment.encoding='utf-8'.None yet — v1 (split out from analyze-industry/references/strategy-palette.md on 2026-05-18 as a standalone Phase 2 sub-skill).
<!-- Built with Agent Engineer Master — get your own production-ready skill: www.agentengineermaster.com/skill-engineer -->
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.