stress-test
Skill4 starsChanged 6 days agoMITView on GitHub
Runs macro-financial stress tests: scenario design, satellite models, bank and sector results, policy implications.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- arndvs/ctrlshfttheir own version, first seen Oct 15, 2026
- adam-paterson/skillstheir own version, first seen Oct 11, 2026
- shakacode/react_on_railstheir own version, first seen Oct 8, 2026
- sgl-project/rbgtheir own version, first seen Oct 8, 2026
- ai-analyst-lab/ai-analysttheir own version, first seen Sep 10, 2026
- arusli1/askillstheir own version, first seen Sep 2, 2026
Used with
Projects with it also use ai-act-readiness, c-level-agents and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Hussain-ElfalahSkillai-act-readiness
Also in 3 projects that use this
Hussain-ElfalahSkillc-level-agents
Also in 3 projects that use this
MicrosoftSkillinbox-setup
Set up the Inbox agent with recommended VS Code settings and gh CLI configuration
Also in 3 projects that use this
- +9 more from Hussain-Elfalah
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- shakacode/react_on_rails★ 5.2ksame name
- sgl-project/rbg★ 314same name
- ai-analyst-lab/ai-analyst★ 304same name
- machina-exm/film-studio-skills★ 137same name
- okikusan-public/stock_skills★ 134same name
- gbasin/stress-test-skill★ 44same name
- Hassaan146/claude-skills★ 18same name
- ilya-a11y/growthband-outbound-skills★ 13same name
- erhwenkuo/stock_skills★ 3same name
- Hussain-Elfalah/Agentic-Skills★ 2same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository210 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/ai-ml-code.mdcCursor rule
- .cursor/rules/code-translation.mdcCursor rule
- .cursor/rules/data-pipelines.mdcCursor rule
- .cursor/rules/documentation.mdcCursor rule
- .cursor/rules/dsge-code.mdcCursor rule
- .cursor/rules/econometrics-code.mdcCursor rule
- .cursor/rules/eviews-code.mdcCursor rule
- .cursor/rules/forecasts.mdcCursor rule
- .cursor/rules/gempack-code.mdcCursor rule
- .cursor/rules/lego-manifests.mdcCursor rule
- .cursor/rules/llm-code.mdcCursor rule
- .cursor/rules/model-code.mdcCursor rule
- .cursor/rules/notebooks-and-scripts.mdcCursor rule
- .cursor/rules/r-code.mdcCursor rule
- .cursor/rules/restricted-data.mdcCursor rule
- .cursor/rules/rl-code.mdcCursor rule
- .cursor/rules/sectoral-trade-climate-code.mdcCursor rule
- .cursor/rules/semi-structural-code.mdcCursor rule
- .cursor/rules/stata-code.mdcCursor rule
- .cursor/rules/tests.mdcCursor rule
- .cursor/rules/validation.mdcCursor rule
- adoptSkill
- ai-auditSkill
- backtestSkill
- build-abmSkill
- build-causal-mlSkill
- build-cgeSkill
- build-climate-macroSkill
- build-deep-forecasterSkill
- build-drl-policySkill
- build-dsgeSkill
- build-financial-programmingSkill
- build-fpasSkill
- build-game-modelSkill
- build-hankSkill
- build-io-samSkill
- build-llm-agentsSkill
- build-llm-pipelineSkill
- build-multicountrySkill
- build-neural-solverSkill
- build-rag-kbSkill
- build-semi-structuralSkill
- build-sfcSkill
- build-trade-modelSkill
- calibrate-modelSkill
- calibration-planSkill
- carbon-pricing-analysisSkill
- chart-packSkill
- climate-scenarioSkill
- code-inventorySkill
- code-reviewSkill
- country-typologySkill
- create-exerciseSkill
- data-requirementsSkill
- debt-decompositionSkill
- debt-sustainabilitySkill
- design-trainingSkill
- distributional-analysisSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Do not use it when: only macro scenarios are needed without financial-sector mapping (/scenario-analysis).
- Very specific: line 26
If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.
- Very specific: line 28
Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …
- Distinctive: line 56
After scenario design: confirm severity
- Distinctive: line 57
After results: confirm policy implications
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated from .claude/skills/stress-test/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->/stress-test — Stress Test
Category: Analysis · Primary agent: financial-stability-stress-testing-specialist
Runs macro-financial stress tests: scenario design, satellite models, bank and sector results, policy implications.
Arguments: whatever the user wrote after the command name.
Purpose
Run a macro-financial stress test: design severe but plausible scenarios calibrated to history and current vulnerabilities, map them to credit losses, income and funding pressures through validated satellite models, compute capital and liquidity outcomes including second-round effects, and draw policy implications. The output identifies vulnerabilities and capital or liquidity shortfalls with their sensitivity to assumptions.
Use it when assessing resilience of banks, non-banks or the financial system, or the fiscal implications of financial stress.
Do not use it when only macro scenarios are needed without financial-sector mapping (/scenario-analysis).
Before you start
- Check required inputs. For each input below record
FOUNDorABSENT(never 'assumed'):- Balance-sheet data
- Macro scenarios
If a required input is
ABSENT, that part isNOT 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.
- 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. - Collaboration. Follow
.claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and updateproduction/session-state/active.mdafter each approved section.
Agents
financial-stability-stress-testing-specialist— primary agent; coordinates the work and integrates resultsmacroprudential-housing-specialist— Analyzes macroprudential policy and housing/credit cyclesscenario-risk-analysis-specialist— Designs scenarios and risk assessmentsbanking-credit-specialist— Models banks and credit markets
Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. 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 |
| Scenario severity | historical analogues, statistical percentiles, reverse stress | Credibility |
| Coverage | largest banks, all banks, non-banks | System view |
| Balance sheet | static, dynamic | Interpretation |
| Channels | credit, market, funding, contagion, fire sales | Completeness |
| Horizon | 1–3 years | Loss accumulation |
Workflow
- Design severity-calibrated scenarios and document the calibration
- Map to risk drivers with validated satellite models
- Validate satellites out of sample on historical losses
- Compute losses, capital and liquidity outcomes with second-round effects
- Interbank and common-exposure contagion; fire sales where relevant
- Report vulnerabilities and policy responses
Checkpoints with the user
- After scenario design: confirm severity
- After results: confirm policy implications
Common pitfalls
- Scenarios milder than past crises
- Static balance sheets read as forecasts
- Ignoring liquidity–solvency interactions
- Second-round effects omitted without flag
Output
forecasts/stress-tests/<name>.md
The report covers scenario calibration, satellite models and validation, losses and capital and liquidity outcomes by institution or sector, second-round effects, and policy implications.
Gate / verdict
- Severity calibrated; satellite models validated
- Balance-sheet assumptions are stated
- Second-round effects are estimated or their omission is flagged
Suggested next steps
/policy-brief/team-stress-test
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

