earnings-analysis
Create professional equity research earnings update reports (8-12 pages, 3,000-5,000 words) analyzing quarterly results for companies already under coverage. Fast-turnaround format focusing on beat/miss analysis, key metrics, updated estimates, and revised thesis. Includes 1-3 summary tables and 8-12 charts. Use when user requests "earnings update", "quarterly update", "earnings analysis", "Q1/Q2/Q3/Q4 results", or post-earnings report.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- earnings-analysis
- description
- Create professional equity research earnings update reports (8-12 pages, 3,000-5,000 words) analyzing quarterly results for companies already under coverage. Fast-turnaround format focusing on beat/miss analysis, key metrics, updated estimates, and revised thesis. Includes 1-3 summary tables and 8-12 charts. Use when user requests "earnings update", "quarterly update", "earnings analysis", "Q1/Q2/Q3/Q4 results", or post-earnings report.
02 资源文件 3
- 参考文档references/best-practices.md9.1 KB
- 参考文档references/report-structure.md10.9 KB
- 参考文档references/workflow.md20.9 KB
03 SKILL.md 正文
Equity Research Earnings Update
Create professional EARNINGS UPDATE REPORTS analyzing quarterly results for companies already under coverage, following institutional standards (JPMorgan, Goldman Sachs, Morgan Stanley format).
Key Characteristics:
- Length: 8-12 pages
- Word Count: 3,000-5,000 words
- Tables: 1-3 summary tables (NOT comprehensive)
- Figures: 8-12 charts
- Turnaround: 1-2 days (within 24-48 hours of earnings)
- Audience: Clients already familiar with the company
- Focus: What's NEW - beat/miss, updated estimates, thesis impact
- Font: Times New Roman throughout (unless user specifies otherwise)
When to Use
Use when the user requests:
- "Create an earnings update for [Company] Q3 2024"
- "Analyze [Company]'s quarterly results"
- "Post-earnings report for [Company]"
- "Q1/Q2/Q3/Q4 update for [Company]"
Do NOT use if:
- User requests "initiation report" → Use different skill
- User requests "flash note" or "quick take" → Different format
- Company is not already covered → Need initiation first
Critical Requirements
1. Speed & Timeliness
- Publish within 24-48 hours of earnings release
- Focus on NEW information only
- Don't rehash company background extensively
2. Beat/Miss Analysis
- Lead with whether company beat or missed estimates
- Quantify variances (e.g., "Revenue beat by $120M or 3%")
- Explain WHY results differed from expectations
3. Summary Format
- Keep tables to 1-3 (summary only, not comprehensive)
- No full P&L/Cash Flow/Balance Sheet (just key metrics)
- Assume reader has seen initiation report
4. Citations & Source Attribution ⭐⭐⭐ MANDATORY
CRITICAL: Properly cite all data with SPECIFIC sources and CLICKABLE HYPERLINKS.
Include specific citations WITH CLICKABLE LINKS in every figure and table:
Source: Q3 2024 10-Q filed November 8, 2024; Company earnings release
[Hyperlink "10-Q" to: https://www.sec.gov/cgi-bin/viewer?accession=...]
[Hyperlink "earnings release" to: https://investor.company.com/news/q3-2024]
HOW HYPERLINKS SHOULD APPEAR IN WORD:
- Document names appear as blue, underlined clickable links
- Reader can Ctrl+Click to open source directly
- Not plain text URLs - formatted hyperlinks with display text
REQUIRED SOURCES LIST:
Cite in every earnings update:
- ✅ Earnings release (with date and URL)
- ✅ 10-Q filing (with filing date and EDGAR link)
- ✅ Earnings call transcript (with date)
- ✅ Investor presentation/supplemental materials (if available)
- ✅ Consensus estimates source (Bloomberg/FactSet/etc. with date)
- ✅ Prior guidance (from previous quarter's materials)
REFERENCE SECTION WITH CLICKABLE HYPERLINKS:
Include "Sources" section at end of report:
SOURCES & REFERENCES
Earnings Materials (Q3 2024):
• Earnings Release (November 7, 2024)
[Hyperlink entire line to: https://investor.company.com/news/q3-2024-earnings]
• Form 10-Q (Filed November 8, 2024)
[Hyperlink to: https://www.sec.gov/cgi-bin/viewer?accession=...]
• Earnings Call Transcript (November 7, 2024)
[Hyperlink to: https://seekingalpha.com/article/...]
• Investor Presentation (November 7, 2024)
[Hyperlink to: https://investor.company.com/presentations/q3-2024.pdf]
VERIFICATION CHECKLIST:
- [ ] Every figure has source with specific document and date
- [ ] Every table has source with document reference
- [ ] Beat/miss analysis cites consensus source with date
- [ ] Guidance changes cite current and prior guidance sources
- [ ] Key statistics have footnotes
- [ ] Sources section lists all materials with URLs
- [ ] ALL URLs are CLICKABLE HYPERLINKS (not plain text)
- [ ] All SEC filings hyperlinked to EDGAR viewer
5. Updated Estimates
- Update forward estimates based on results
- Show old vs. new estimates clearly
- Explain what changed and why
High-Level Workflow
The earnings update process follows 5 phases:
Phase 1: Data Collection (30-60 minutes)
🚨🚨🚨 CRITICAL: TRAINING DATA IS OUTDATED 🚨🚨🚨
BEFORE STARTING - COMPLETE THESE 4 STEPS IN ORDER:
- CHECK TODAY'S DATE - Write down the current date
- SEARCH FOR LATEST - Use web search: "[Company] latest earnings results"
- VERIFY THE DATE - Confirm earnings release is within last 3 months
- CHECK TRANSCRIPT DATE - Verify transcript date matches release date
COMMON MISTAKE: Using outdated earnings calls from training data instead of searching for the latest.
REQUIREMENTS:
- ✅ Search for latest earnings - do NOT rely on training data
- ✅ Write down today's date and the release date found
- ✅ Verify release date is within 3 months of today
- ✅ Verify transcript date matches release date
- ✅ If dates don't match or are old (>3 months), search again
See references/workflow.md for detailed search procedures and verification steps.
Phase 2: Analysis (2-3 hours)
- Beat/miss analysis for each key metric
- Segment/geographic/product breakdown
- Margin and guidance analysis
- Update financial model and estimates
See references/workflow.md for detailed analysis framework.
Phase 3: Chart Generation (1-2 hours)
Create 8-12 charts focusing on quarterly trends and what's new:
- Quarterly revenue progression
- Quarterly EPS progression
- Quarterly margin trends
- Revenue by segment/geography
- Key operating metrics
- Beat/miss summary
- Estimate revisions
- Valuation charts
See references/workflow.md for chart specifications.
Phase 4: Report Creation (2-3 hours)
Create 8-12 page DOCX report with specific structure.
See references/report-structure.md for complete page-by-page templates and formatting requirements.
High-level structure:
- Page 1: Earnings summary with rating and price target
- Pages 2-3: Detailed results analysis
- Pages 4-5: Key metrics & guidance
- Pages 6-7: Updated investment thesis
- Pages 8-10: Valuation & estimates
- Pages 11-12: Appendix (optional)
Phase 5: Quality Check & Delivery (30 minutes)
Verify content, formatting, accuracy, and timeliness before delivery.
See references/best-practices.md for quality checklist and common mistakes to avoid.
Output Specification
Primary Deliverable: DOCX report (8-12 pages)
File Name: [Company]_Q[Quarter]_[Year]_Earnings_Update.docx
Example: Nike_Q2_FY24_Earnings_Update.docx
Contents:
- Page 1: Summary with rating, price target, key takeaways
- Pages 2-3: Detailed results analysis
- Pages 4-5: Key metrics and guidance
- Pages 6-7: Updated thesis assessment
- Pages 8-10: Valuation and estimates
- Pages 11-12: Appendix (optional)
- 8-12 embedded charts
- 1-3 summary tables
- Complete sources section with clickable hyperlinks
Optional Deliverable: XLS model update (optional for earnings updates)
Key Differences from Initiation Report
| Aspect | Earnings Update | Initiation Report |
|---|---|---|
| Length | 8-12 pages | 30-50 pages |
| Words | 3,000-5,000 | 10,000-15,000 |
| Tables | 1-3 summary | 12-20 comprehensive |
| Figures | 8-12 | 25-35 |
| Turnaround | 1-2 days | 3-6 weeks |
| Scope | Quarterly results | Complete company |
| Focus | What's NEW | Everything |
| Company Background | Brief mention | 6-10 pages |
| XLS Model | Optional | Required |
Resources
references/workflow.md
Detailed Phase 1-5 instructions with step-by-step procedures for data collection, analysis, chart generation, and report creation.
references/report-structure.md
Complete page-by-page templates, table formats, and formatting requirements for the DOCX report.
references/best-practices.md
Examples of good/bad headlines, tips for success, common mistakes to avoid, and comprehensive quality checklist.
Dependencies
Required:
- Python (matplotlib, pandas, seaborn) for chart generation
- DOCX skill for report creation
Optional:
- XLS skill for model updates (not required for earnings updates)
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.