earnings-preview
Skill1 starsChanged 5 months agoApache-2.0View on GitHub
Pre-earnings setup for any listed company ahead of a quarterly, half-year, or full-year result. Builds a structured decision framework: consensus estimates, bull/base/bear scenarios, key metrics to watch, thesis pillar checklist, and historical stock reaction context. Pairs with earnings-analysis (post-print verdict) and thesis-tracker (pillar updates). Covers US (NYSE/NASDAQ) and AU (ASX) markets.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Distilla-AI/distilla-skillstheir own version, first seen Nov 1, 2026
- openai/pluginstheir own version, first seen Oct 13, 2026
- edu6565/claude-skillstheir own version, first seen Oct 11, 2026
- anthropics/financial-services-pluginstheir own version, first seen Oct 8, 2026
- anthropics/financial-servicestheir own version, first seen Jul 22, 2026
Used with
Projects with it also use cim-builder, morning-note and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillcim-builder
Structure and draft a Confidential Information Memorandum for sell-side M&A processes. Organizes company information into a professional, investor-ready document with consistent formatting and narrative flow. Use when preparing sell-side materials, drafting a CIM, or organizing company data for a sale process. Triggers on "CIM", "confidential information memorandum", "offering memorandum", "info memo", "draft CIM", or "sell-side materials".
Also in 3 projects that use this
AnthropicSkillmorning-note
Draft concise morning meeting notes summarizing overnight developments, trade ideas, and key events for coverage stocks. Designed for the 7am morning meeting format — tight, opinionated, actionable. Triggers on "morning note", "morning meeting", "what happened overnight", "trade idea", "morning call prep", or "daily note".
Also in 3 projects that use this
- +7 more from anthropics
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- anthropics/financial-services-plugins★ 41ksame name
- anthropics/financial-services★ 41ksame name
- openai/plugins★ 7.8ksame name
- Distilla-AI/distilla-skills★ 9same name
- edu6565/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- alpha-scannerSkill
- catalyst-calendarSkill
- deal-analysisSkill
- earnings-analysisSkill
- financial-statement-readerSkill
- management-quality-agentSkill
- portfolio-reviewSkill
- red-team-modeSkill
- stock-investment-analysisSkill
- stock-orchestratorSkill
- strategic-moat-agentSkill
- thesis-trackerSkill
- values-esg-agentSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 136
If no thesis file exists, flag this and suggest running thesis-tracker after the result.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Earnings Preview
Role
You prepare the investor to enter an earnings event with a structured position: what consensus expects, what the thesis requires, what scenarios are plausible, and what specific metrics will determine whether conviction rises or falls after the print.
This is a decision framework built before the result, not a prediction, and not a research report. Its job is to eliminate noise so the investor can assess the actual print quickly when it drops.
The output from this skill feeds directly into earnings-analysis. When running the post-print review, reference this preview document.
Step 0: Calibrate Depth
| Mode | Trigger | Output |
| Quick | "just the key numbers", "brief", "what's consensus" | Consensus table + 3 key metrics |
| Full (default) | No modifier, or any mention of thesis / positioning | All steps |
Step 1: Confirm Inputs
- Company and ticker (include exchange suffix for ASX: e.g. WDS.AX)
- Reporting period: Q1/Q2/Q3/Q4 or H1/H2/FY and fiscal year
- Earnings date and time: confirm via web search. For AU: note pre-market (ASX open) or post-close (after 4pm AEST)
- Existing thesis: check Theses folder for
[TICKER]-thesis.md. Load if found. - Position: held (long), watchlist, or none
Then proceed. Do not ask for anything else.
Step 2: Consensus Snapshot
Pull via web search. For US: Yahoo Finance, Seeking Alpha, company IR. For ASX: CommSec, ASX announcements, company IR. Note analyst count: thin coverage (1-3 analysts) means higher surprise potential and a wider confidence interval.
Company: [Name] ([TICKER]) Reporting period: [Q/H/FY] [Year] Earnings date: [Day DD Mon YYYY, Time] Analysts covering: [X]
| Metric | Consensus | Prior Period Actual | YoY Change | Estimate Range (High / Low) |
| Revenue | ||||
| EBITDA / Operating Profit | ||||
| NPAT / EPS | ||||
| Gross Margin | ||||
| [Key sector metric 1] | ||||
| [Key sector metric 2] | ||||
| Forward guidance | N/A (wait for result) | : | : | : |
A wide estimate range signals high uncertainty: flag this as it implies a larger potential price move.
Step 3: Key Metrics Framework
Identify the 3-5 metrics that will actually move this stock on results day: often not the headline figures. State why each matters right now.
For each metric:
- Metric: [Name and expected value or direction]
- Why it matters this print: [1 sentence]
- Threshold: [What level / direction is positive vs. concerning]
Common sector-specific metrics:
- Technology / SaaS: ARR growth, net revenue retention, RPO, operating leverage
- Resources / Mining (ASX): Realised prices vs. spot, production volumes vs. guidance, AISC, capex vs. budget
- Banks / Financials: NIM direction, credit quality, loan growth, cost-to-income
- Healthcare: Script volumes, pipeline updates, reimbursement decisions
- Industrials: Backlog, book-to-bill, price vs. volume mix
- Retail: Same-store sales, gross margin, inventory levels
Step 4: Scenario Framework
| Scenario | Probability | Revenue vs. Consensus | EPS vs. Consensus | Key Driver | Expected Stock Reaction |
| Bull | [%] | [+X%] | [+X%] | [What drives it] | [+X% to +X%] |
| Base | [%] | [~flat] | [~flat] | [In-line, guidance intact] | [Range] |
| Bear | [%] | [-X%] | [-X%] | [What drives it] | [-X% to -X%] |
Probabilities must sum to 100%. For each scenario, name the confirmation signal: the single piece of evidence in the result or commentary that immediately tells you which scenario has played out.
Step 5: Historical Reaction Context
How has this stock moved on the last 3-4 prints?
| Period | Beat / Miss / In-line | Revenue | EPS | Guidance | Stock Day-1 Move |
| [Q/H/FY Year] |
Note any pattern: does this stock reward beats, or is it guidance-dependent? Source via web search.
Step 6: Thesis Pillar Checklist (only if thesis file exists)
| Pillar | What the Print Will Show | Confirmation Signal | Concern Signal |
| [Pillar name] | [Specific metric or disclosure] | [What confirms it's intact] | [What challenges it] |
Work through this table live when the result drops: note ✅/⚠️/❌ next to each pillar. Then hand these notes to earnings-analysis for the post-print verdict.
If no thesis file exists, flag this and suggest running thesis-tracker after the result.
Step 7: Output
Quick mode: Consensus table + three key metrics. Inline only, no file.
Full mode:
- Deliver inline: lead with earnings date and key metrics (most time-sensitive), then scenarios, then pillar checklist.
- Save to the user's workspace folder:
Stock Strategy/Stock Investment Analysis/Earnings-Previews/[TICKER]-[Period]-preview.md(or equivalent) - Confirm file saved and path.
- Note: when the result drops, run earnings-analysis and reference this preview file.
Important Notes
- For ASX companies: results land on the ASX platform at market open (10am AEST) or after close (4pm AEST). The ASX announcements page is the primary source.
- For small/mid-cap ASX stocks with 1-3 analysts, a "beat" or "miss" vs. thin consensus is less meaningful than for large-caps. Note this explicitly.
- Guidance language matters for AU companies: watch for phrasing shifts: "in line", "towards the top of the range", "subject to market conditions".
- This skill pairs with: thesis-tracker (pillar source), catalyst-calendar (scheduled trigger), earnings-analysis (post-print handoff), and stock-institutional (for institutional investors: reassess the active weight recommendation after a material earnings event confirms or challenges the fundamental verdict).
Chaining note:
stock-institutionalis planned for a future release of this repository. The earnings workflow in this repo is complete without it.
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
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.

