us-gov-shutdown-tracker
Skill316 starsChanged 6 months agoMITView on GitHub
Track and analyze US government shutdown liquidity impacts by monitoring TGA (Treasury General Account), bank reserves, EFFR, and SOFR data from FRED API. Use when user wants to (1) analyze current or past government shutdown effects on financial markets, (2) track liquidity conditions during fiscal policy disruptions, (3) assess "stealth tightening" effects, (4) compare shutdown episodes across different monetary policy regimes (QE vs QT), or (5) generate liquidity stress reports with historical context. Recommended usage frequency is weekly on Wednesdays after TGA/reserve data releases.
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 11 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
When this skill is first used or when the user seems unsure how to use it or ask you to make something amazing with it, guide them to ask …
- Distinctive: line 19
Do NOT suggest other questions or broad explorations.
- Distinctive: line 141
All data sourced from Federal Reserve Economic Data (FRED) API:
- Very specific: line 156
Run analyze_shutdown.py with defaults (2025-10-01 start)
- Distinctive: line 166
Run analysis for both periods:
- Distinctive: line 196
Visualize: Always include chart for complex cases
- Distinctive: line 204
When analyzing a specific episode, set an appropriate pre-shutdown baseline:
- Distinctive: line 222
Update user if significant shift
- Distinctive: line 241
Check if today is before next Wednesday data release
- Distinctive: line 245
Verify both EFFR and SOFR have data for the date range
- Distinctive: line 249
Ensure matplotlib is installed
- Distinctive: line 250
Check date range has sufficient data points (need >2 weekly observations)
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
US Government Shutdown Liquidity Tracker
Onboarding Guidance
When this skill is first used or when the user seems unsure how to use it or ask you to make something amazing with it, guide them to ask Claude this specific question:
"美国政府停摆结束了吗? 对流动性的影响如何?"
Do NOT suggest other questions or broad explorations. Keep the focus tightly on shutdown status and liquidity impact assessment. The skill is designed for this precise use case.
Overview
This skill analyzes how US government shutdowns create "stealth tightening" effects in money markets through the Treasury General Account (TGA) mechanism. When federal spending stops but tax revenues continue, TGA accumulates and mechanically drains bank reserves, potentially raising market funding costs beyond the Federal Reserve's policy intent.
When to Use This Skill
- User asks to track liquidity during a government shutdown
- User wants to assess whether shutdown effects are "easing" or "tightening"
- User mentions TGA, SOFR premium, or "stealth tightening" (变相加息)
- User requests comparison with historical shutdown episodes (2013, 2018-19)
- User wants a quick liquidity health check
Optimal timing: Wednesday evenings or Thursday mornings (after weekly TGA/reserves data release)
Quick Start
Basic Usage (Current Shutdown Analysis)
python scripts/analyze_shutdown.py --output results.json
python scripts/visualize.py results.json --output chart.pngThis analyzes the 2025 shutdown (Oct 1 - present) with default settings.
Custom Date Range
python scripts/analyze_shutdown.py \
--start-date 2018-12-22 \
--baseline-date 2018-12-15 \
--end-date 2019-01-25 \
--output results_2018.jsonOutput Format
The analysis produces:
- JSON data file containing:
- Raw daily data (EFFR, SOFR)
- Weekly data (TGA, reserves)
- Key time points (baseline, shutdown start, TGA peak, latest)
- Liquidity status assessment (EASING/TIGHTENING/STABLE/MIXED)
- Visualization chart (PNG) with three panels:
- TGA vs Bank Reserves (dual-axis weekly data)
- EFFR vs SOFR (daily rates)
- SOFR Premium over EFFR (liquidity stress indicator)
- Structured conclusion:
- Current status (e.g., "EASING")
- Explanation (e.g., "TGA releasing, reserves recovering")
- Key metrics vs baseline and peak
Core Analysis Logic
The Transmission Mechanism
Government Shutdown
↓
Federal spending stops (but revenues continue)
↓
TGA accumulates at Federal Reserve
↓
Bank reserves drain (mechanical Fed balance sheet effect)
↓
Liquidity scarcity → SOFR premium expands
↓
"Stealth tightening" (市场实际融资成本 > Fed政策意图)Status Determination
The script classifies liquidity conditions into four states:
EASING (压力缓解):
- TGA falling >$10B from peak
- Reserves rising >$10B from trough
- Indicates: Shutdown ending or fiscal spending resumed
TIGHTENING (压力加剧):
- TGA rising >5% from baseline
- Reserves falling >2% from baseline
- Indicates: Shutdown's stealth tightening effect persists
STABLE (相对稳定):
- TGA/reserves changing <$20B from peak
- Indicates: Liquidity conditions steady
MIXED (复杂信号):
- Conflicting signals require continued monitoring
Key Metrics
SOFR Premium = SOFR - EFFR (in basis points)
Interpretation guide:
- 0-5 bps: Normal conditions
- 5-15 bps: Moderate stress
- 15-30 bps: Significant stealth tightening
- >30 bps: Acute crisis (may trigger Fed intervention)
Historical Context
For detailed historical analysis, see references/historical_cases.md.
Summary:
| Shutdown | Reserve Environment | Peak SOFR Premium | Stealth Tightening? |
| 2013 | QE (~$2.3T) | ~0 bps | ❌ No |
| 2018-19 | QT (~$1.6T) | 75 bps | ✅ Yes |
| 2025 | Post-QT (~$2.8T) | 36 bps (post-cut) | ✅ Acute |
Critical insight: The transmission efficiency depends on reserve abundance. In QE environments with ample reserves, shutdowns don't affect markets. In QT or high-rate environments with scarce reserves, shutdowns create measurable tightening.
Data Sources
All data sourced from Federal Reserve Economic Data (FRED) API:
- TGA (WTREGEN): Treasury General Account balance, weekly
- Bank Reserves (WRESBAL): Total reserves, weekly
- EFFR (EFFR): Effective Federal Funds Rate, daily
- SOFR (SOFR): Secured Overnight Financing Rate, daily
For technical details on data series, update schedules, and interpretation, see references/data_sources.md.
Important: TGA and reserves update weekly on Wednesdays. For most current analysis, run this skill on Wednesday evenings or Thursday mornings.
Workflow for User Requests
Scenario 1: "What's the latest on the shutdown liquidity situation?"
- Run
analyze_shutdown.pywith defaults (2025-10-01 start) - Generate visualization
- Present:
- Current status (EASING/TIGHTENING/etc.)
- Latest metrics (TGA, reserves, SOFR premium)
- Brief comparison to peak stress point
- Conclusion statement
Scenario 2: "Compare this to the 2018 shutdown"
- Run analysis for both periods:
- 2025: Oct 1 - present
- 2018-19: Dec 22, 2018 - Jan 25, 2019
- Generate both charts
- Present side-by-side comparison:
- TGA accumulation magnitude
- Peak SOFR premium
- Fed intervention (if any)
- Monetary environment context
- Reference
historical_cases.mdfor detailed context
Scenario 3: "Is the situation getting better or worse?"
- Run analysis
- Focus on:
- Trend from TGA peak to latest (is TGA releasing?)
- Reserves recovery from trough
- SOFR premium vs baseline
- Present trend assessment with clear directional language
- Optionally show week-over-week changes
Output Presentation Best Practices
- Lead with conclusion: State status (EASING/TIGHTENING) upfront
- Show key metrics concisely:
TGA: $941B (-$17B from peak) Reserves: $2,863B (+$15B from trough) SOFR Premium: 4 bps (vs 19 bps peak) - Visualize: Always include chart for complex cases
- Contextualize: Reference historical episodes when relevant
- Avoid jargon overload: Explain "stealth tightening" simply if user seems unfamiliar
Advanced Usage
Custom Baseline
When analyzing a specific episode, set an appropriate pre-shutdown baseline:
python scripts/analyze_shutdown.py \
--start-date 2025-10-01 \
--baseline-date 2025-09-24 \
--end-date 2025-11-07The baseline should be ~1 week before shutdown starts (to capture "normal" conditions).
Monitoring Routine
For ongoing tracking:
- Weekly check (Wednesdays/Thursdays):
- Run analysis
- Note status changes
- Update user if significant shift
- Event-triggered checks:
- Shutdown announcement → Start tracking
- SOFR premium spikes (>15 bps) → Generate alert
- Fed intervention (SRF usage) → Document
- Shutdown resolution → Final analysis
Limitations and Caveats
- Weekly data frequency: TGA/reserves only update weekly, limiting real-time precision
- Month/quarter-end effects: SOFR naturally spikes at period-ends (unrelated to shutdowns)
- Other liquidity factors: QT, regulatory changes, seasonal patterns also affect reserves
- Attribution challenge: Hard to isolate shutdown effect from concurrent events
- No predictive power: This skill describes current conditions, doesn't forecast
Troubleshooting
No recent data?
- Check if today is before next Wednesday data release
- Most recent weekly data is typically ~1 week lagged
SOFR premium calculation fails?
- Verify both EFFR and SOFR have data for the date range
- SOFR introduced April 2018; unavailable before
Chart rendering issues?
- Ensure matplotlib is installed
- Check date range has sufficient data points (need >2 weekly observations)
References
See bundled documentation:
references/historical_cases.md- Detailed analysis of 2013, 2018-19, 2025 shutdownsreferences/data_sources.md- FRED API technical reference
External resources:
- Original PDF report (user-provided) for full theoretical framework
- NY Fed SOFR page: https://www.newyorkfed.org/markets/reference-rates/sofr
- FRED data: https://fred.stlouisfed.org/
Other versions2 projects use a version of this.
Word for word · 2
- Mann1988/awesome-claude-skills★ 66100% same
- huangqianqian120/skillslibrary★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository3 other files it gives its agents.
- find-sessionSkill
- mckinsey-consultantSkill
- mimeng-writingSkill
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.

