Installs into .claude/skills of the current project.
Are you the author of Supply Chain Shock?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/tatashbar-supply-chain-shock-economic-modeling-studio)
---
name: supply-chain-shock
description: "Analyzes sectoral and supply-chain shocks with input-output and production-network models: propagation, bottlenecks, and price and quantity effects."
argument-hint: "[shock description]"
user-invocable: true
allowed-tools: Read, Glob, Grep, Write, Edit, Bash, AskUserQuestion, Task
---
# /supply-chain-shock — Supply Chain Shock
**Category:** Analysis · **Primary agent:** `production-networks-specialist`
Analyzes sectoral and supply-chain shocks with input-output and production-network models: propagation, bottlenecks, and price and quantity effects.
Arguments: `$ARGUMENTS`
## Purpose
Analyze a sectoral or supply-chain shock (a disaster, export ban, sanctions, port closure or input shortage) by propagating it through input-output and production-network models, identifying bottlenecks, and estimating output, price, employment and trade effects under low and high substitutability. The output compares nonlinear network results with a first-order approximation and evaluates mitigation options with their costs.
**Use it when** a disruption hits specific sectors or suppliers and its economy-wide effects, bottlenecks and resilience options must be assessed.
**Do not use it when** the shock is purely a demand change suitable for multipliers (`/build-io-sam`) or a tariff scenario (`/trade-policy-analysis`).
## Before you start
1. **Check required inputs.** For each input below record `FOUND` or `ABSENT` (never 'assumed'):
- IO or network data
- Shock description
If a required input is `ABSENT`, that part is **`NOT ASSESSED — NO DATA`**: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
2. **Check confidentiality.** Identify the data classification level of the inputs (`.claude/docs/confidentiality-and-ai-use.md`). Do not proceed with restricted or confidential data in a way the policy does not allow.
3. **Collaboration.** Follow `.claude/docs/collaboration-protocol.md`: ask questions first, present options, get approval before writing files, and update `production/session-state/active.md` after each approved section.
## Agents
- `production-networks-specialist` — primary agent; coordinates the work and integrates results
- `input-output-sam-specialist` — Builds input-output, supply-use and social accounting matrix frameworks
- `trade-gvc-specialist` — Models trade and global value chains
- `physical-climate-risk-specialist` — Quantifies physical climate risk
- `commodity-markets-specialist` — Models commodity markets
Run these agents as subagents (the `Task` tool), in parallel where the steps are independent. Subagents only write to the paths named in your instructions.
## Key design decisions (present options, let the user choose)
| Decision | Typical options | What it changes |
|---|---|---|
| Network | national IO, multi-regional IO, firm-level | Detail and coverage |
| Substitution | Leontief, low CES, high CES | Severity of bottlenecks |
| Shock form | output loss, price spike, quantity rationing | Propagation pattern |
| Duration | weeks, months, permanent | Role of inventories |
| Mitigation | diversification, stockpiles, reshoring | Policy options |
## Workflow
1. Define the shock: sector, region, size, duration and substitution assumptions
2. Propagate through the network with low and high substitutability
3. Estimate output, price, employment and trade effects; identify bottlenecks
4. Compare with a first-order (Hulten-style) approximation and explain differences
5. Evaluate mitigation options: diversification, stockpiles, reshoring
- Include costs in normal times, not only benefits in crises
## Checkpoints with the user
- After defining the shock: confirm size, duration and substitution range
- After results: confirm mitigation options to evaluate
## Common pitfalls
- Fixed coefficients for large, persistent shocks
- Aggregation hiding single points of failure
- Missing foreign suppliers
- Mitigation without cost
## Output
`forecasts/sectoral/<name>-supply-chain.md`
The report defines the shock, presents results under low and high substitution, compares them with the first-order result, identifies bottlenecks and evaluates mitigation with costs.
## Gate / verdict
- Results shown for low and high substitution
- Data coverage limits disclosed
- Mitigation options include their costs
## Suggested next steps
- `/policy-brief`
- `/scenario-analysis`