tradermonty/scenario-analyzer
| Skill that analyzes 18-month scenarios from a news headline. Runs the primary analysis with the scenario-analyst agent and obtains a second opinion with the strategy-reviewer agent. Generates a comprehensive English report covering 1st/2nd/3rd-order impacts, recommended stocks, and a critical review. medium-to-long-term investment strategy
This is a copy. The original lives at baggat236/scenario-analyzer.
npx skills add https://github.com/tradermonty/claude-trading-skills --skill scenario-analyzer
This skill analyzes medium-to-long-term (18-month) investment scenarios
starting from a news headline. It invokes two specialized agents in sequence
(scenario-analyst and strategy-reviewer) and integrates multi-angle
analysis with a critical review into a comprehensive report.
Use this skill when:
Examples:
/scenario-analyzer "Fed raises interest rates by 50bp, signals more hikes ahead"
/scenario-analyzer "China announces new tariffs on US semiconductors"
/scenario-analyzer "OPEC+ agrees to cut oil production by 2 million barrels per day"
┌─────────────────────────────────────────────────────────────────────┐
│ Skill (orchestrator) │
│ │
│ Phase 1: Preparation │
│ ├─ Headline parsing │
│ ├─ Event type classification │
│ └─ Reference loading │
│ │
│ Phase 2: Agent invocation │
│ ├─ scenario-analyst (primary analysis) │
│ └─ strategy-reviewer (second opinion) │
│ │
│ Phase 3: Integration & report generation │
│ └─ reports/scenario_analysis_<topic>_YYYYMMDD.md │
└─────────────────────────────────────────────────────────────────────┘
Parse the headline provided by the user.
Classify the headline into one of the following categories:
| Category | Examples |
|----------|----------|
| Monetary Policy | FOMC, ECB, BOJ, rate hike, rate cut, QE/QT |
| Geopolitics | War, sanctions, tariffs, trade friction |
| Regulation & Policy | Environmental regulation, financial regulation, antitrust |
| Technology | AI, EV, renewables, semiconductors |
| Commodities | Crude oil, gold, copper, agricultural products |
| Corporate & M&A | Acquisitions, bankruptcies, earnings, industry restructuring |
Based on the event type, load the relevant references:
Read references/headline_event_patterns.md
Read references/sector_sensitivity_matrix.md
Read references/scenario_playbooks.md
Reference contents:
headline_event_patterns.md: Historical event patterns and market reactionssector_sensitivity_matrix.md: Event × sector impact-magnitude matrixscenario_playbooks.md: Scenario-construction templates and best practicesUse the Agent tool to invoke the primary analysis agent.
Agent tool:
- subagent_type: "scenario-analyst"
- prompt: |
Perform an 18-month scenario analysis for the following headline.
## Target Headline
[the input headline]
## Event Type
[classification result]
## Reference Information
[summary of the loaded references]
## Analysis Requirements
1. Use WebSearch to collect related news from the past 2 weeks
2. Construct 3 scenarios — Base/Bull/Bear (probabilities sum to 100%)
3. Analyze 1st/2nd/3rd-order impacts by sector
4. Select 3-5 positive- and 3-5 negative-impact stocks (US market only)
5. Output everything in English
Expected output:
Using the scenario-analyst's results, invoke the review agent.
Agent tool:
- subagent_type: "strategy-reviewer"
- prompt: |
Review the following scenario analysis.
## Target Headline
[the input headline]
## Analysis Result
[the full scenario-analyst output]
## Review Requirements
Review from the following angles:
1. Overlooked sectors/stocks
2. Validity of the scenario probability allocation
3. Logical consistency of the impact analysis
4. Detection of optimism/pessimism bias
5. Proposal of alternative scenarios
6. Realism of the timeline
Output constructive and specific feedback in English.
Expected output:
Integrate the output of both agents to produce the final investment judgment.
Integration points:
Generate the final report in the following format and save it to a file.
Save location: reports/scenario_analysis_<topic>_YYYYMMDD.md
# Headline Scenario Analysis Report
**Analyzed at**: YYYY-MM-DD HH:MM
**Target headline**: [the input headline]
**Event type**: [classification category]
---
## 1. Related News Articles
[news list collected by scenario-analyst]
## 2. Scenario Overview (through 18 months out)
### Base Case (XX% probability)
[scenario details]
### Bull Case (XX% probability)
[scenario details]
### Bear Case (XX% probability)
[scenario details]
## 3. Sector / Industry Impact
### 1st-Order Impact (direct)
[impact table]
### 2nd-Order Impact (value chain / related industries)
[impact table]
### 3rd-Order Impact (macro / regulation / technology)
[impact table]
## 4. Stocks Expected to Benefit (3-5 tickers)
[stock table]
## 5. Stocks Expected to Be Hurt (3-5 tickers)
[stock table]
## 6. Second Opinion / Review
[strategy-reviewer output]
## 7. Final Investment Judgment & Implications
### Recommended Actions
[concrete actions informed by the review]
### Risk Factors
[list of key risks]
### Monitoring Points
[indicators / events to follow]
---
**Generated by**: scenario-analyzer skill
**Agents**: scenario-analyst, strategy-reviewer
reports/ directory if it does not existscenario_analysis_<topic>_YYYYMMDD.md (e.g., scenario_analysis_venezuela_20260104.md)This skill generates the following file:
| File | Format | Description |
|------|--------|-------------|
| reports/scenario_analysis_<topic>_YYYYMMDD.md | Markdown | Comprehensive scenario analysis report |
Output contents:
references/headline_event_patterns.md - Event patterns and market reactionsreferences/sector_sensitivity_matrix.md - Sector sensitivity matrixreferences/scenario_playbooks.md - Scenario-construction templatesscenario-analyst - Primary scenario analysisstrategy-reviewer - Second opinion / reviewreports/ directoryreports/scenario_analysis_<topic>_YYYYMMDD.mdreports/scenario_analysis_fed_rate_hike_20260104.mdreports/ directory if it does not existConfirm the following before finalizing the report:
Take tradermonty/scenario-analyzer from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.