fxmacrodata-calendar — Claude Code skill: macro release calendar
Pulls official FXMacroData release dates so a trade plan can pause entries ahead of CPI, NFP or a central-bank decision.
npx skills add tradermonty/claude-trading-skills --skill fxmacrodata-calendar -a claude-codeWhat fxmacrodata-calendar does
The skill runs fetch_calendar.py and returns the release-calendar events. Your agent then reads events[] and folds the timing into the trade plan: hold off on new entries around high-impact releases, trim leverage or position size, and schedule a follow-up once the actual value lands. It also states which event and timestamp caused the adjustment.
The call is python3 skills/fxmacrodata-calendar/scripts/fetch_calendar.py --currency usd --min-tier 1. Only 1, 2 or 3 are valid for --min-tier. Public USD calendar rows need no key; other FXMacroData endpoints want FXMACRODATA_API_KEY in the environment. Requests go to https://api.fxmacrodata.com/v1.
A nonzero exit means the event-risk state is unverified, not that nothing is scheduled. An empty calendar is only a successful response carrying events: []. Results are accepted when the response currency matches the request and data_quality marks the source as official, current, non-proxy, non-fallback and timestamp-complete. Every event needs an announcement timestamp and a non-empty release identifier.
What it helps with
- pin down exact CPI, NFP and GDP release dates before a trade
- pause new entries around central-bank decisions
- cut leverage ahead of a PCE or PMI print
- schedule a follow-up review after the actual value is out
- tell an empty calendar apart from a failed request
Example prompts for the agent
- Show the USD release calendar with min tier 1
- Which tier-1 events this week could break my EUR/USD plan?
- Check macro event risk before I open a position
How to install fxmacrodata-calendar
1Skills CLI (Vercel)
npx skills add tradermonty/claude-trading-skills --skill fxmacrodata-calendar -a claude-code2Manually: put the files in place
~/.claude/skills/fxmacrodata-calendar/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/fxmacrodata-calendar/
1Skills CLI (Vercel)
npx skills add tradermonty/claude-trading-skills --skill fxmacrodata-calendar -a codex2Manually: put the files in place
.agents/skills/fxmacrodata-calendar/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tradermonty/claude-trading-skills --skill fxmacrodata-calendar -a cursor2Manually: put the files in place
.cursor/skills/fxmacrodata-calendar/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tradermonty/claude-trading-skills fxmacrodata-calendar2Manually: put the files in place
.github/skills/fxmacrodata-calendar/SKILL.md1Skills CLI (Vercel)
npx skills add tradermonty/claude-trading-skills --skill fxmacrodata-calendar -a gemini-cli2Platform CLI
gemini skills install https://github.com/tradermonty/claude-trading-skills --path skills/fxmacrodata-calendarManually: put the files in place
.devin/skills/fxmacrodata-calendar/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tradermonty/claude-trading-skills --skill fxmacrodata-calendar -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about fxmacrodata-calendar
How do I install fxmacrodata-calendar in Claude Code?
Run npx skills add tradermonty/claude-trading-skills --skill fxmacrodata-calendar -a claude-code. The skill lands at ~/.claude/skills/fxmacrodata-calendar/SKILL.md.
What does fxmacrodata-calendar do?
It fetches official FXMacroData release-calendar events and works their timing into the trade plan: entry pauses, smaller position size, a review after the release.
Do I need an API key?
Public USD calendar rows work without one. For the remaining FXMacroData endpoints, set the FXMACRODATA_API_KEY environment variable.
Source text
SKILL.md · MIT
--- 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 1. Run the calendar script: ```bash python3 skills/fxmacrodata-calendar/scripts/fetch_calendar.py --currency usd --min-tier 1 ``` 2. 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 and `data_quality` confirms 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. 3. 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.
© tradermonty · MIT · tradermonty/claude-trading-skills