economic-calendar-trading
Skill17 starsChanged 4 months agoApache-2.0View on GitHub
Plan scheduled macro-event risk from official calendars and point-in-time expectations. Use for FOMC, employment, inflation, GDP, or other releases requiring standardized surprise, component, revision, scenario, and execution analysis.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- IngAs8/ClaudeSkilledited, first seen Sep 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- IngAs8/ClaudeSkill★ 010% same
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 repository56 other files it gives its agents.
- candlestick-patternsSkill
- channel-tradingSkill
- cup-and-handleSkill
- double-top-bottomSkill
- flag-pennantSkill
- head-and-shouldersSkill
- triangle-patternsSkill
- wedge-patternsSkill
- altcoin-rotationSkill
- arbitrage-tradingSkill
- dca-strategySkill
- funding-rate-tradingSkill
- on-chain-analysisSkill
- breakout-tradingSkill
- gap-tradingSkill
- momentum-tradingSkill
- news-tradingSkill
- pullback-tradingSkill
- range-tradingSkill
- scalping-strategySkill
- earnings-tradingSkill
- insider-activity-tradingSkill
- market-correlation-tradingSkill
- sector-rotationSkill
- sentiment-analysisSkill
- breaker-blocksSkill
- fair-value-gapsSkill
- kill-zonesSkill
- liquidity-zonesSkill
- market-structure-shiftSkill
- optimal-trade-entrySkill
- order-blocksSkill
- premium-discountSkill
- correlation-riskSkill
- drawdown-managementSkill
- leverage-managementSkill
- partial-profit-takingSkill
- position-sizingSkill
- risk-reward-ratioSkill
- stop-loss-strategiesSkill
- trailing-stopSkill
- bollinger-bandsSkill
- divergence-tradingSkill
- fibonacci-tradingSkill
- ichimoku-cloudSkill
- macd-tradingSkill
- market-regime-detectionSkill
- mean-reversionSkill
- moving-average-crossoverSkill
- multi-timeframe-analysisSkill
- rsi-divergenceSkill
- stochastic-tradingSkill
- supply-demand-zonesSkill
- volume-profile-tradingSkill
- vwap-tradingSkill
- skill-nameSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
Use a point-in-time consensus and same-definition historical series.
- Distinctive: line 55
Use a pretested bar-based delay or price-structure trigger.
- Very specific: line 64
Use get_financial_news to analyze FOMC statements and press conferences for hawk/dove tone shifts.
- Distinctive: line 70
Treat the setup as a testable hypothesis, not a prediction.
- Distinctive: line 78
Verify actuals and revisions from the primary source before interpretation.
- Distinctive: line 79
Use the predeclared execution gate.
- Very specific: line 82
Treat clustered or conflicting components as lower confidence or no trade.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Economic Calendar Trading
Plan macro-event risk from live official calendars, time-stamped consensus, release vintages, and observable price triggers. Surprise matters, but revisions, components, positioning, uncertainty, and regime affect the response.
Event Map
| Event family | Components to record | Primary source |
| FOMC | Decision, statement changes, SEP, press conference | Federal Reserve |
| Employment | Payrolls, unemployment, participation, wages, revisions | BLS |
| Inflation | Headline/core, monthly/annual, category breadth, revisions | BLS/BEA |
| Growth/activity | Real/nominal detail, inventories, revisions, survey components | Source agency |
Standardized Surprise
Standardized surprise = (Actual - consensus) / historical standard deviation of surprisesUse a point-in-time consensus and same-definition historical series. State source, sample, standard deviation, revisions, and transformation. If history is insufficient, report raw surprise and forecast range without a synthetic score.
Workflow
1. Check Calendar
get_economics_calendar(from_date=<start>, to_date=<end>, impact="high")Refresh before each session and verify date, time, timezone, and revision policy against the official agency calendar; third-party impact labels are screening aids only.
2. Research Consensus
get_financial_news(topic="<event> forecast consensus <month> <year>", max_results=10)Extract: consensus forecast, range of estimates, leading indicators, and current market positioning.
3. Build Scenario Matrix
Map component combinations, revisions, and price triggers. Include no trade for mixed releases or failed liquidity conditions; do not assign probabilities without a calibrated model.
4. Post-Release Execution Gate
Use a pretested bar-based delay or price-structure trigger. Require verified actuals, acceptable spread/depth, stable timestamps, and a calculable stop; event labels do not determine a universal waiting period.
5. Trade the Reaction
- Continuation candidate: enter only on the specified closed-bar or retest trigger.
- Fade candidate: define overreaction in normalized returns and test separately; VWAP is a benchmark, not a guaranteed destination.
6. FOMC Analysis
Use get_financial_news to analyze FOMC statements and press conferences for hawk/dove tone shifts.
Analyze the decision, statement redlines, projections, and press conference separately. Measure the response in policy-rate futures/yields and the traded asset; do not infer fixed direction or duration from a hawkish/dovish label.
Evidence and Validation
- Treat the setup as a testable hypothesis, not a prediction. Define thresholds, entry, invalidation, and exit before evaluating outcomes.
- Calibrate on the same instrument, venue, session, and timeframe. Use closed candles and a held-out or walk-forward sample; record every variant tried.
- Include spread, fees, slippage, borrow or funding, partial fills, and latency. Reject the setup when net expectancy is not positive or depends on one narrow parameter.
- Return observed inputs, missing data, cost assumptions, entry, invalidation, exit, and a valid, watch, or no-trade status.
- Research basis: Use the official Federal Reserve calendar and BLS release calendar because dates can change; Federal Reserve research shows reaction depends on surprise, disagreement, and regime.
Key Rules
- Verify actuals and revisions from the primary source before interpretation.
- Use the predeclared execution gate; neither immediate trading nor a fixed wait is universally safe.
- Choose order type from the fill-versus-price-risk tradeoff; limits may not fill and markets may slip.
- Aggregate direct, correlated, and factor exposures in the event stress test.
- Treat clustered or conflicting components as lower confidence or
no trade. - Size from stress loss, not a vendor impact score.
Related Skills
- sentiment-analysis -- Pre-event sentiment gauges positioning
- sector-rotation -- Macro data drives sector rotation shifts
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.

