Economic Calendar Fetcher

Overview

Retrieve upcoming economic events and data releases from the Financial Modeling Prep (FMP) Economic Calendar API. This skill fetches scheduled economic indicators including central bank monetary policy decisions, employment reports, inflation data (CPI/PPI), GDP releases, retail sales, manufacturing data, and other market-moving events that impact financial markets.

The skill uses a Python script to query the FMP API and generates chronological markdown reports with impact assessment for each scheduled event.

Key Capabilities:

• - Fetch economic events for specified date ranges (max 90 days)
• Support flexible API key provision (environment variable or user input)
• Filter by impact level, country, or event type
• Generate structured markdown reports with impact analysis
• Default to next 7 days for quick market outlook

Data Source:

• - FMP Economic Calendar API: INLINECODE0
• Covers major economies: US, EU, UK, Japan, China, Canada, Australia
• Event types: Central bank decisions, employment, inflation, GDP, trade, housing, surveys

When to Use This Skill

Use this skill when the user requests:

1. 1. Economic Calendar Queries:

- "What economic events are coming up this week?" - "Show me the economic calendar for the next two weeks" - "When is the next FOMC meeting?" - "What major economic data is being released next month?"

1. 2. Market Event Planning:

- "What should I watch for in the markets this week?" - "Are there any high-impact economic releases coming?" - "When is the next jobs report / CPI release / GDP report?"

1. 3. Specific Date Range Requests:

- "Get economic events from January 1 to January 31" - "What's on the economic calendar for Q1 2025?"

1. 4. Country-Specific Queries:

- "Show me US economic data releases next week" - "What ECB events are scheduled?" - "When is Japan releasing their inflation data?"

DO NOT use this skill for:

• - Past economic events (use market-news-analyst for historical analysis)
• Corporate earnings calendars (this skill excludes earnings)
• Real-time market data or live quotes
• Technical analysis or chart interpretation

Workflow

Follow these steps to fetch and analyze the economic calendar:

Step 1: Obtain FMP API Key

Check for API key availability:

1. 1. First check if FMPAPIKEY environment variable is set
2. If not available, ask user to provide API key via chat
3. If user doesn't have API key, provide instructions:

- Visit https://financialmodelingprep.com - Sign up for free account (250 requests/day limit) - Navigate to API dashboard to obtain key

Example user interaction:
CODEBLOCK0

Step 2: Determine Date Range

Set appropriate date range based on user request:

Default (no specific dates): Today + 7 days
User specifies period: Use exact dates (validate format: YYYY-MM-DD)
Maximum range: 90 days (FMP API limitation)

Examples:

• - "Next week" → Today to +7 days
• "Next two weeks" → Today to +14 days
• "January 2025" → 2025-01-01 to 2025-01-31
• "Q1 2025" → 2025-01-01 to 2025-03-31

Validate date range:

• - Ensure start date ≤ end date
• Ensure range ≤ 90 days
• Warn if querying past dates

Step 3: Execute API Fetch Script

Run the geteconomiccalendar.py script with appropriate parameters:

Basic usage (default 7 days):
CODEBLOCK1

With specific date range:
CODEBLOCK2

Using environment variable (no --api-key needed):
CODEBLOCK3

Script parameters:

• - --from: Start date (YYYY-MM-DD) - default: today
• INLINECODE2: End date (YYYY-MM-DD) - default: today + 7 days
• INLINECODE3: FMP API key (optional if FMPAPIKEY env var set)
• INLINECODE4: Output format (json or text) - default: json
• INLINECODE5: Output file path (optional, default: stdout)

Handle errors:

• - Invalid API key → Ask user to verify key
• Rate limit exceeded (429) → Suggest waiting or upgrading FMP tier
• Network errors → Retry with exponential backoff
• Invalid date format → Provide correct format example

Step 4: Parse and Filter Events

Process the JSON response from the script:

1. 1. Parse event data: Extract all events from API response
2. Apply user filters if specified:

- Impact level: "High", "Medium", "Low" - Country: "US", "EU", "JP", "CN", etc. - Event type: FOMC, CPI, Employment, GDP, etc. - Currency: USD, EUR, JPY, etc.

Filter examples:

• - "Show only high-impact events" → Filter impact == "High"
• "US events only" → Filter country == "US"
• "Central bank decisions" → Search event name for "Rate", "Policy", "FOMC", "ECB", "BOJ"

Event data structure:
CODEBLOCK4

Step 5: Assess Market Impact

Evaluate the market significance of each event:

Impact Level Classification (from FMP):

• - High Impact: Major market-moving events

- FOMC rate decisions, ECB/BOJ policy meetings
- Non-Farm Payrolls (NFP), CPI, GDP
- Market typically shows 0.5-2%+ intraday volatility

• - Medium Impact: Significant but less volatile

- Retail Sales, Industrial Production - PMI surveys, Consumer Confidence - Housing data, Durable Goods Orders

• - Low Impact: Minor indicators

- Weekly jobless claims (unless extreme) - Regional manufacturing surveys - Minor auction results

Additional Context Factors:

1. 1. Current Market Sensitivity:

- High inflation environment → CPI/PPI elevated importance - Recession fears → Employment data more critical - Rate cut speculation → Central bank meetings crucial

1. 2. Surprise Potential:

- Compare estimate vs. previous reading - Large expected changes = higher attention - Consensus uncertainty = higher impact potential

1. 3. Event Clustering:

- Multiple related events same day = amplified impact - Example: CPI + Retail Sales + Fed speech = Very High impact day

1. 4. Forward Significance:

- Does this event influence upcoming central bank decisions? - Is this a preliminary or final reading? - Will this data be revised?

Step 6: Generate Output Report

Create structured markdown report with the following sections:

Report Header:
CODEBLOCK5

Event Listing (Chronological):

For each event, provide:

CODEBLOCK6

Example Event Entry:

CODEBLOCK7

Summary Section:

Add analytical summary at the end:

CODEBLOCK8

Filtering Notes:

If user requested specific filters, note at top:
CODEBLOCK9

Output Format:

• - Primary: Markdown file saved to disk
• Filename format: INLINECODE6
• Also display summary to user in chat

Output Format Specifications

File naming convention:
CODEBLOCK10

Markdown structure requirements:

1. 1. Chronological ordering: Events sorted by date and time (earliest first)
2. Impact level indicators: Use (High Impact), (Medium Impact), (Low Impact) labels
3. Time zone clarity: Always specify UTC and provide ET/PT conversions for US events
4. Data completeness: Include all available fields (previous, estimate, actual if past)
5. Null handling: Display "N/A" or "No estimate" for null values
6. Impact assessment: Every high/medium impact event must have market implications analysis

Table format option (for dense listings):

CODEBLOCK11

Language: All reports in English

Resources

Python Script:

• - scripts/get_economic_calendar.py: Main API fetch script with CLI interface

Reference Documentation:

• - references/fmp_api_documentation.md: Complete FMP Economic Calendar API reference

- Authentication and API key management
- Request parameters and date formats
- Response field definitions
- Rate limits and error handling
- Best practices for caching and efficiency

API Details:

• - Endpoint: INLINECODE9
• Authentication: API key required (free tier: 250 requests/day)
• Max date range: 90 days per request
• Response format: JSON array of event objects
• Rate limits: 5 requests/second (free tier)

Event Coverage:

• - Major economies: US, EU, UK, Japan, China, Canada, Australia, Switzerland
• Event categories: Monetary policy, Employment, Inflation, GDP, Trade, Housing, Surveys
• Update frequency: Real-time (events added/updated as scheduled)
• Historical data: Available for past events with actual values

Usage Tips:

1. 1. Cache results to minimize API calls (events rarely change once scheduled)
2. Query 7-30 day ranges for optimal request efficiency
3. Don't query >6 months in future (sparse data, speculative dates)
4. Refresh cache daily for upcoming week to catch time changes
5. Use smaller ranges (1-7 days) for real-time event monitoring

Error Handling:

• - API key errors: Clear user guidance for obtaining free key
• Rate limits: Exponential backoff retry logic
• Network failures: Graceful degradation with cached data if available
• Invalid dates: Validation with helpful error messages