earnings-calendar

tradermonty/claude-trading-skills · updated May 30, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/tradermonty/claude-trading-skills --skill earnings-calendar
0 commentsdiscussion
summary

This skill retrieves upcoming earnings announcements for US stocks using the Financial Modeling Prep (FMP) API. It focuses on companies with significant market capitalization (mid-cap and above, over $2B) that are likely to impact market movements. The skill generates organized markdown reports showing which companies are reporting earnings over the next week, grouped by date and timing (before market open, after market close, or time not announced).

skill.md

Earnings Calendar

Overview

This skill retrieves upcoming earnings announcements for US stocks using the Financial Modeling Prep (FMP) API. It focuses on companies with significant market capitalization (mid-cap and above, over $2B) that are likely to impact market movements. The skill generates organized markdown reports showing which companies are reporting earnings over the next week, grouped by date and timing (before market open, after market close, or time not announced).

Key Features:

  • Uses FMP API for reliable, structured earnings data
  • Filters by market cap (>$2B) to focus on market-moving companies
  • Includes EPS and revenue estimates
  • Multi-environment support (CLI, Desktop, Web)
  • Flexible API key management
  • Organized by date, timing, and market cap

Prerequisites

FMP API Key

This skill requires a Financial Modeling Prep API key.

Get Free API Key:

  1. Visit: https://site.financialmodelingprep.com/developer/docs
  2. Sign up for free account
  3. Receive API key immediately
  4. Free tier: 250 API calls/day (sufficient for weekly earnings calendar)

API Key Setup by Environment:

Claude Code (CLI):

export FMP_API_KEY="your-api-key-here"

Claude Desktop: Set environment variable in system or configure MCP server.

Claude Web: API key will be requested during skill execution (stored only for current session).

Core Workflow

Step 1: Get Current Date and Calculate Target Week

CRITICAL: Always start by obtaining the accurate current date.

Retrieve the current date and time:

  • Use system date/time to get today's date
  • Note: "Today's date" is provided in the environment ( tag)
  • Calculate the target week: Next 7 days from current date

Date Range Calculation:

Current Date: [e.g., November 2, 2025]
Target Week Start: [Current Date + 1 day, e.g., November 3, 2025]
Target Week End: [Current Date + 7 days, e.g., November 9, 2025]

Why This Matters:

  • Earnings calendars are time-sensitive
  • "Next week" must be calculated from the actual current date
  • Provides accurate date range for API request

Format dates in YYYY-MM-DD for API compatibility.

Step 2: Load FMP API Guide

Before retrieving data, load the comprehensive FMP API guide:

Read: references/fmp_api_guide.md

This guide contains:

  • FMP API endpoint structure and parameters
  • Authentication requirements
  • Market cap filtering strategy (via Company Profile API)
  • Earnings timing conventions (BMO, AMC, TAS)
  • Response format and field descriptions
  • Error handling strategies
  • Best practices and optimization tips

Step 3: API Key Detection and Configuration

Detect API key availability based on environment.

Multi-Environment API Key Detection:

3.1 Check Environment Variable (CLI/Desktop)

if [ ! -z "$FMP_API_KEY" ]; then
  echo "✓ API key found in environment"
  API_KEY=$FMP_API_KEY
fi

If environment variable is set, proceed to Step 4.

3.2 Prompt User for API Key (Desktop/Web)

If environment variable not found, use AskUserQuestion tool:

Question Configuration:

Question: "This skill requires an FMP API key to retrieve earnings data. Do you have an FMP API key?"
Header: "API Key"
Options:
  1. "Yes, I'll provide it now" → Proceed to 3.3
  2. "No, get free key" → Show instructions (3.2.1)
  3. "Skip API, use manual entry" → Jump to Step 8 (fallback mode)

3.2.1 If user chooses "No, get free key":

Provide instructions:

To get a free FMP API key:

1. Visit: https://site.financialmodelingprep.com/developer/docs
2. Click "Get Free API Key" or "Sign Up"
3. Create account (email + password)
4. Receive API key immediately
5. Free tier includes 250 API calls/day (sufficient for daily use)

Once you have your API key, please select "Yes, I'll provide it now" to continue.

3.3 Request API Key Input

If user has API key, request input:

Prompt:

Please paste your FMP API key below:

(Your API key will only be stored for this conversation session and will be forgotten when the session ends. For regular use, consider setting the FMP_API_KEY environment variable.)

Store API key in session variable:

API_KEY = [user_input]

Confirm with user:

✓ API key received and stored for this session.

Security Note:
- API key is stored only in current conversation context
- Not saved to disk or persistent storage
- Will be forgotten when session ends
- Do not share this conversation if it contains your API key

Proceeding with earnings data retrieval...

Step 4: Retrieve Earnings Data via FMP API

Use the Python script to fetch earnings data from FMP API.

Script Location:

scripts/fetch_earnings_fmp.py

Execution:

Option A: With Environment Variable (CLI):

python scripts/fetch_earnings_fmp.py 2025-11-03 2025-11-09

Option B: With Session API Key (Desktop/Web):

python scripts/fetch_earnings_fmp.py 2025-11-03 2025-11-09 "${API_KEY}"

Script Workflow (automatic):

  1. Validates API key and date parameters
  2. Calls FMP Earnings Calendar API for date range
  3. Fetches company profiles (market cap, sector, industry)
  4. Filters companies with market cap >$2B
  5. Normalizes timing (BMO/AMC/TAS)
  6. Sorts by date → timing → market cap (descending)
  7. Outputs JSON to stdout

Expected Output Format (JSON):

[
  {
    "symbol": "AAPL",
    "companyName": "Apple Inc.",
    "date": "2025-11-04",
    "timing": "AMC",
    "marketCap": 3000000000000,
    "marketCapFormatted": "$3.0T",
    "sector": "Technology",
    "industry": "Consumer Electronics",
    "epsEstimated": 1.54,
    "revenueEstimated": 123400000000,
    "fiscalDateEnding": "2025-09-30",
    "exchange": "NASDAQ"
  },
  ...
]

Save to file (recommended for use with report generator):

python scripts/fetch_earnings_fmp.py 2025-11-03 2025-11-09 "${API_KEY}" > earnings_data.json

Or capture to variable:

earnings_data=$(python scripts/fetch_earnings_fmp.py 2025-11-03 2025-11-09 "${API_KEY}")

Error Handling:

If script returns errors:

  • 401 Unauthorized: Invalid API key → Verify key or re-enter
  • 429 Rate Limit: Exceeded 250 calls/day → Wait or upgrade plan
  • Empty Result: No earnings in date range → Expand date range or note in report
  • Connection Error: Network issue → Retry or use cached data if available

Step 5: Process and Organize Data

Once earnings data is retrieved (JSON format), process and organize it:

5.1 Parse JSON Data

Load JSON data from script output:

import json
earnings_data = json.loads(earnings_json_string)

Or if saved to file:

with open('earnings_data.json', 'r') as f:
    earnings_data = json.load(f)

5.2 Verify Data Structure

Confirm data includes required fields:

  • ✓ symbol
  • ✓ companyName
  • ✓ date
  • ✓ timing (BMO/AMC/TAS)
  • ✓ marketCap
  • ✓ sector

5.3 Group by Date

Group all earnings announcements by date:

  • Sunday, [Full Date] (if applicable)
  • Monday, [Full Date]
  • Tuesday, [Full Date]
  • Wednesday, [Full Date]
  • Thursday, [Full Date]
  • Friday, [Full Date]
  • Saturday, [Full Date] (if applicable)

5.4 Sub-Group by Timing

Within each date, create three sub-sections:

  1. Before Market Open (BMO)
  2. After Market Close (AMC)
  3. Time Not Announced (TAS)

Data is already sorted by timing from the script, so maintain this order.

5.5 Within Each Timing Group

Companies are already sorted by market cap descending (script output):

  • Mega-cap (>$200B) first
  • Large-cap ($10B-$200B) second
  • Mid-cap ($2B-$10B) third

This prioritization ensures the most market-moving companies are listed first.

5.6 Calculate Summary Statistics

Compute:

  • Total Companies: Count of all companies in dataset
  • Mega/Large Cap Count: Count where marketCap >= $10B
  • Mid Cap Count: Count where marketCap between $2B and $10B
  • Peak Day: Day of week with most earnings announcements
  • Sector Distribution: Count by sector (Technology, Healthcare, Financial, etc.)
  • Highest Market Cap Companies: Top 5 companies by market cap

Step 6: Generate Markdown Report

Use the report generation script to create a formatted markdown report from the JSON data.

Script Location:

scripts/generate_report.py

Execution:

Option A: Output to stdout:

python scripts/generate_report.py earnings_data.json

Option B: Save to file:

python scripts/generate_report.py earnings_data.json earnings_calendar_2025-11-02.md

What the script does:

  1. Loads earnings data from JSON file
  2. Groups by date and timing (BMO/AMC/TAS)
  3. Sorts by market cap within each group
  4. Calculates summary statistics
  5. Generates formatted markdown report
  6. Outputs to stdout or saves to file

The script automatically handles all formatting including:

  • Proper markdown table structure
  • Date grouping and day names
  • Market cap sorting
  • EPS and revenue formatting
  • Summary statistics calculation

Report Structure:

# Upcoming Earnings Calendar - Week of [START_DATE] to [END_DATE]

**Report Generated**: [Current Date]
**Data Source**: FMP API (Mid-cap and above, >$2B market cap)
**Coverage Period**: Next 7 days
**Total Companies**: [COUNT]

---

## Executive Summary

- **Total Companies Reporting**: [TOTAL_COUNT]
- **Mega/Large Cap (>$10B)**: [LARGE_CAP_COUNT]
- **Mid Cap ($2B-$10B)**: [MID_CAP_COUNT]
- **Peak Day**: [DAY_WITH_MOST_EARNINGS]

---

## [Day Name], [Full Date]

### Before Market Open (BMO)

| Ticker | Company | Market Cap | Sector | EPS Est. | Revenue Est. |
|--------|---------|------------|--------|----------|--------------|
| [TICKER] | [COMPANY] | [MCAP] | [SECTOR] | [EPS] | [REV] |

### After Market Close (AMC)

| Ticker |
how to use earnings-calendar

How to use earnings-calendar on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add earnings-calendar
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/tradermonty/claude-trading-skills --skill earnings-calendar

The skills CLI fetches earnings-calendar from GitHub repository tradermonty/claude-trading-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/earnings-calendar

Reload or restart Cursor to activate earnings-calendar. Access the skill through slash commands (e.g., /earnings-calendar) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.539 reviews
  • Fatima Abebe· Dec 20, 2024

    I recommend earnings-calendar for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Tariq Iyer· Dec 4, 2024

    earnings-calendar is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Tariq Srinivasan· Nov 23, 2024

    Useful defaults in earnings-calendar — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Yusuf Park· Nov 19, 2024

    earnings-calendar has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Yash Thakker· Nov 11, 2024

    earnings-calendar has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Chinedu Lopez· Nov 11, 2024

    Keeps context tight: earnings-calendar is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Neel Kapoor· Oct 14, 2024

    I recommend earnings-calendar for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Kaira Reddy· Oct 10, 2024

    Solid pick for teams standardizing on skills: earnings-calendar is focused, and the summary matches what you get after install.

  • Dhruvi Jain· Oct 2, 2024

    Solid pick for teams standardizing on skills: earnings-calendar is focused, and the summary matches what you get after install.

  • Chinedu Haddad· Oct 2, 2024

    earnings-calendar is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 39

1 / 4