
us-gov-shutdown-tracker
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.
- Installs
- 52
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/fleurytian/awesome-claude-skills --skill us-gov-shutdown-tracker- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads us-gov-shutdown-tracker automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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.png
This 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.json
Output 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-07
The 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/
FAQ
What does the us-gov-shutdown-tracker skill do?
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.
How do I install us-gov-shutdown-tracker?
Run npx skills add https://github.com/fleurytian/awesome-claude-skills --skill us-gov-shutdown-tracker in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/us-gov-shutdown-tracker/ (personal) or .claude/skills/us-gov-shutdown-tracker/ (project).
Which AI agents can use us-gov-shutdown-tracker?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is us-gov-shutdown-tracker safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains us-gov-shutdown-tracker?
It is published by fleurytian in fleurytian/awesome-claude-skills. It has 52 recorded installs.
More from fleurytian/awesome-claude-skills
mckinsey-consultant
fleurytian/awesome-claude-skills
McKinsey顾问式问题解决系统。从商业问题出发,通过假设驱动的结构化分析方法,生成McKinsey风格研究报告和PPT。融合Problem Solving方法论、MECE原则、Issue Tree拆解、Hypotheses形成、Dummy Page设计、智能数据收集和专业PPT生成能力。
mimeng-writing
fleurytian/awesome-claude-skills
Open the skill to read its SKILL.md instructions.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.