Earnings Preview Skill

Generates a pre-earnings briefing using Yahoo Finance data via yfinance. Pulls together upcoming earnings date, consensus estimates, historical accuracy, analyst sentiment, and key financial context — everything you need before an earnings call.

Important: Data is for research and educational purposes only. Not financial advice. yfinance is not affiliated with Yahoo, Inc.

Step 1: Ensure yfinance Is Available

Current environment status:

!`python3 -c "import yfinance; print('yfinance ' + yfinance.__version__ + ' installed')" 2>/dev/null || echo "YFINANCE_NOT_INSTALLED"`

If

YFINANCE_NOT_INSTALLED

import subprocess, sys
subprocess.check_call([sys.executable, "-m", "pip", "install", "-q", "yfinance"])

If already installed, skip to the next step.

Step 2: Identify the Ticker and Gather All Data

Extract the ticker symbol from the user's request. If they mention a company name without a ticker, look it up. Then fetch all relevant data in one script to minimize API calls.

import yfinance as yf
import pandas as pd
from datetime import datetime

ticker = yf.Ticker("AAPL")  # replace with actual ticker

# --- Core data ---
info = ticker.info
calendar = ticker.calendar

# --- Estimates ---
earnings_est = ticker.earnings_estimate
revenue_est = ticker.revenue_estimate

# --- Historical track record ---
earnings_hist = ticker.earnings_history

# --- Analyst sentiment ---
price_targets = ticker.analyst_price_targets
recommendations = ticker.recommendations

# --- Recent financials for context ---
quarterly_income = ticker.quarterly_income_stmt
quarterly_cashflow = ticker.quarterly_cashflow

What to extract from each source

calendar

earnings_estimate

revenue_estimate

earnings_history

analyst_price_targets

recommendations

quarterly_income_stmt

Step 3: Build the Earnings Preview

Assemble the data into a structured briefing. The goal is to give the user everything they need in one glance.

Section 1: Earnings Date & Key Info

Report the upcoming earnings date from

calendar

• Company name, ticker, sector, industry
• Upcoming earnings date (and whether it's before/after market)
• Current stock price and recent performance (1-week, 1-month)
• Market cap

Section 2: Consensus Estimates

Present the current quarter estimates from

earnings_estimate

revenue_estimate

If the estimate range is unusually wide (high/low spread > 20% of consensus), note that as a sign of high uncertainty.

Section 3: Historical Beat/Miss Track Record

From

earnings_history

Summarize: "AAPL has beaten EPS estimates in 4 of the last 4 quarters by an average of 2.6%."

Section 4: Analyst Sentiment

From

recommendations

analyst_price_targets

• Current recommendation distribution (Strong Buy / Buy / Hold / Sell / Strong Sell)
• Price target range: low, mean, median, high vs. current price
• Implied upside/downside from mean target

Section 5: Key Metrics to Watch

Based on the quarterly financials, highlight 3-5 things the market will focus on:

• Revenue growth trend (accelerating or decelerating?)
• Margin trajectory (expanding or compressing?)
• Any notable line items that changed significantly quarter-over-quarter
• Segment breakdowns if available in the data

This section requires judgment — think about what matters for this specific company/sector.

Step 4: Respond to the User

Present the preview as a clean, structured briefing:

1. Lead with the headline: "AAPL reports earnings on [date]. Here's what to expect."
2. Show all 5 sections with clear headers and tables
3. End with a brief summary: 2-3 sentences capturing the overall setup (bullish/bearish lean based on estimates, track record, and sentiment — frame as "the street expects" not personal recommendation)

Caveats to include

• Estimates can change up until the report date
• Historical beats don't guarantee future beats
• Yahoo Finance data may lag real-time consensus by a few hours
• This is not financial advice

Reference Files

• references/api_reference.md

  — Detailed yfinance API reference for earnings and estimate methods

Read the reference file when you need exact method signatures or edge case handling.