fxmacrodata-calendar
GitHub获取FXMacroData官方宏观数据日历事件，用于交易计划制定、宏观状态检查及事件风险过滤。支持按货币和层级筛选，确保数据源权威性与时效性，辅助在高影响发布前后调整仓位与策略。
Trigger Scenarios
Install
npx skills add tradermonty/claude-trading-skills --skill fxmacrodata-calendar -g -y
SKILL.md
Frontmatter
{
"name": "fxmacrodata-calendar",
"description": "Fetch official FXMacroData macro release-calendar events for trade planning, macro regime checks, and event-risk filters. Use before CPI, NFP, GDP, PCE, retail sales, PMI, and central-bank decision windows."
}
FXMacroData Calendar
Retrieve official-source macro release-calendar events from FXMacroData. Use this skill when a trade plan needs event timing, confirmed release dates, or a top-tier macro risk check.
Workflow
-
Run the calendar script:
python3 skills/fxmacrodata-calendar/scripts/fetch_calendar.py --currency usd --min-tier 1 -
Review
events[]for top-tier releases.Treat a nonzero exit as an unverified event-risk state, never as an empty calendar. Only a successful response containing
events: []establishes that no matching events were returned. The client accepts results only when the response currency matches the request anddata_qualityconfirms an official, current, non-proxy, non-fallback, timestamp-complete, point-in-time-safe source. Each event must include an announcement timestamp and a non-empty release identifier. -
Fold the event timing into the trade plan:
- pause new entries around high-impact releases;
- reduce leverage or position size;
- schedule follow-up review after the actual value is available;
- explain which event and timestamp drove the adjustment.
Authentication
Set FXMACRODATA_API_KEY for authenticated FXMacroData endpoints. Public USD
calendar rows can be fetched without a key. The client uses the canonical
https://api.fxmacrodata.com/v1 endpoint and accepts --min-tier values 1,
2, or 3 only. Live calendar responses currently include market_tier; the
skill treats it as an extension field and requires integer values 1 through 3
for filtering, although the current CalendarReleaseRow OpenAPI schema does
not declare that field.
Version History
- 769a6c8 Current 2026-08-20 07:01
