← Search

Earnings Recap
Finance
⚙ Needs: Use "Earnings Recap" with your Muse.

Earnings Recap

A post-earnings debrief: actual EPS versus the estimate, the size of the surprise, revenue and margin trends, and how the stock actually reacted to the print.

⚠️ **Trading warning / Avertissement trading** : informational only, not investment advice. A recap explains what already happened; it is not a signal to buy or sell after the move. Curated by Skill Harbor: a post-earnings analysis that starts from the result itself. It pulls the actual versus estimated EPS and the surprise in dollars and percent, revenue with year-over-year growth, and gross and operating margin trends computed from about five quarters of statements, then measures the stock's real price reaction: the move from the last close before the report to the first close after it, handling after-close and before-open releases correctly, and compares it with the stock's average absolute earnings-day move over its previous four reports so you can tell a genuine shock from a routine swing. It finishes with what changed: margin direction, the revenue growth trajectory, and whether this surprise fits or breaks the company's usual pattern. Data comes from Yahoo Finance through the free yfinance library. From the himself65/finance-skills repository (MIT). Honest caveats: you need Python 3 with pip (the skill installs yfinance itself if missing); the recap works from statements and prices only, so guidance, segment color, and management commentary from the earnings call are not captured; the measured reaction can partly reflect a broad market move that day rather than the report itself; if the report landed after the most recent close, the regular-session reaction is still pending and the skill says so. Skill Harbor never reviews the code, review it yourself before use.
At a glance
What
A post-earnings debrief: actual EPS versus the estimate, the size of the surprise, revenue and margin trends, and how the stock actually reacted to the print.
Cost
Free
Needs
Use "Earnings Recap" with your Muse.
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

⌁

Install

Copy the install package below, then paste it into Muse
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a build before installing →

Use "Earnings Recap" with your Muse. Prerequisites: Python 3 with pip and an agent that can run Python code. The skill installs yfinance itself if it is missing. No API key and no paid data subscription are required; the data comes from Yahoo Finance via the free yfinance library. 1. Open the skill: https://github.com/himself65/finance-skills/blob/main/plugins/market-analysis/skills/earnings-recap/SKILL.md and copy the full SKILL.md text (the skill also reads its included references/api_reference.md, keep the repo folder handy). 2. Paste it into a chat with Muse and add: "How did [TICKER]'s latest earnings go? Beat or miss, how big was the surprise, how did margins trend, and how did the stock react compared with its usual earnings-day move?" 3. Read the reaction number with its context: a big move on a market-wide wild day says less about the report than the same move on a quiet day. Tip: ask for a specific past quarter (for example "the Q2 report") when you want to study an older print rather than the latest one. Safety: a skill is plain-text instructions; it runs nothing by itself. This is informational only, not investment advice.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.