Fxmacrodata Calendar Skill for Claude
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/tradermonty/claude-trading-skills --skill fxmacrodata-calendarThe instruction itself
3 sections, as written by the authorFXMacroData 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 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.
- 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.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take tradermonty/fxmacrodata-calendar from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.