agentleFS
EodHistoricalDataEodHistoricalData/eodhd-claude-skills/skills/earnings-monitor/SKILL.md

earnings-monitor

Skill47 starsChanged 4 months agoMITView on GitHub

Monitor upcoming and recent earnings — calendar, trends, news context, and options activity around earnings dates. Use when the user asks about earnings season, upcoming reports, earnings surprises, or pre/post-earnings analysis.

The file

Files
SKILL.md

Skill: earnings-monitor

Purpose

Track and analyze earnings events using EODHD data — upcoming earnings calendar, historical earnings trends (EPS estimates vs actuals), related news, and intraday price action around earnings dates.

Trigger

Activate when the user asks for:

  • Upcoming earnings calendar or "who reports this week"
  • Earnings history, surprises, or beat/miss analysis
  • Pre-earnings or post-earnings price movement
  • Earnings trends and estimate revisions
  • Event-driven analysis around earnings dates

Workflow

  1. Determine scope — specific ticker(s) or date range for calendar view
  2. Fetch earnings calendar — calendar/earnings with date range or symbols
  3. Fetch earnings trends — calendar/trends for EPS estimates, revisions, growth
  4. Fetch related news — news endpoint filtered around earnings dates
  5. Fetch price action — intraday or eod around earnings date for reaction analysis
  6. Compile earnings report

Output Structure

Earnings Monitor — [Ticker or Date Range]

Upcoming Earnings

DateCompanyTickerEPS EstimateRevenue EstimateTime

Earnings Trends (for specific tickers)

  • EPS trend (last 4 quarters): actual vs estimate
  • Revenue trend (last 4 quarters)
  • Surprise history (% beat/miss)
  • Analyst revision direction (up/down/flat)

Price Reaction Analysis

  • Pre-earnings drift (5 days before)
  • Post-earnings move (day of + next day)
  • Historical earnings-day volatility

Related News

  • Headlines around earnings date with sentiment

Key Insights

  • Notable surprises or misses
  • Sectors with heavy reporting
  • Estimate revision trends

This is not financial advice. Data is for informational purposes only.

Endpoints Used

EndpointPurposeCost
calendar/earningsEarnings dates and estimates1 call
calendar/trendsEPS/revenue trends and revisions1 call
newsEarnings-related news5 + 5/ticker
eodPrice around earnings1 call
intradayIntraday reaction5 calls

References

  • ../eodhd-api/references/endpoints/upcoming-earnings.md
  • ../eodhd-api/references/endpoints/earnings-trends.md
  • ../eodhd-api/references/endpoints/company-news.md
  • ../eodhd-api/references/endpoints/intraday-historical-data.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.