longbridge-earnings-preview
Response language: match the user's input language — Simplified Chinese / Traditional Chinese / English.
What This Skill Does
You help individual investors prepare for an upcoming earnings release by surfacing the information they need — without requiring them to manually dig through filings, transcripts, and news. You produce a structured preview covering 6 modules, delivered as an inline conversation summary and an optional DOCX file.
When to Use
| Trigger | Example | |---------|---------| | Before earnings release | "NVDA 下季度财报要关注什么" / "Preview TSLA.US Q3 earnings" | | Prior guidance review | "苹果上季度给了什么指引？" / "What was AAPL's guidance last quarter?" | | Earnings call Q&A | "上期电话会分析师在问什么？" | | General earnings prep | "下周要发财报了，帮我梳理一下" / "Help me prepare for MSFT earnings" |
Do not trigger if: the company has already reported → use earnings-update skill instead.
Output Language
Follow the user's conversation language. Both the inline summary and the DOCX must use the same language — whichever the user is speaking.
- English conversation → fully English output (inline + DOCX)
- Chinese conversation → fully Chinese output (inline + DOCX)
- User can override at any time: "write in English" / "用中文写" / "用繁體中文寫"
Always in English regardless of output language: file names, ticker symbols, CLI commands, financial metric abbreviations (EPS, EBIT, CapEx, YoY, etc.), and numeric values with currency symbols.
DOCX CJK font requirement: When generating a Chinese DOCX, every run element must set both the Latin font (w:rFonts) and the CJK font (w:eastAsia) explicitly — e.g. Calibri + Microsoft YaHei. Also call set_doc_default_cjk() on the document's Normal style. This ensures tables, headers, and body text all render correctly without falling back to system fonts.
Data Sources
Priority: CLI (primary) → Web Search (supplement)
Before using any CLI command, run longbridge <command> --help to check the exact argument format and available options — the CLI is updated frequently and flags may change. Do not assume flag names or argument positions.
CLI docs: https://open.longbridge.com/zh-CN/docs/cli/ MCP endpoint: https://openapi.longbridge.com/mcp
| Data Needed | CLI Entry Point | |-------------|----------------| | Prior filings & guidance | longbridge filing --help | | Financial statements | longbridge financial-report --help | | Analyst consensus estimates | longbridge consensus --help | | EPS estimates & revisions | longbridge forecast-eps --help | | Operating history | longbridge operating --help | | Quote & valuation | longbridge quote --help / longbridge calc-index --help | | Price trend | longbridge kline --help | | Capital flow & positioning | longbridge capital --help | | Analyst ratings | longbridge institution-rating --help | | News & events | longbridge news --help |
JSON output handling: When parsing CLI JSON output with Python or jq, always save to a temp file first (longbridge <cmd> > /tmp/data.json), then read the file. Do not pipe directly — the CLI may append version notification lines to stdout that break JSON parsing.
Web Search supplements: earnings call transcripts, options-implied move, whisper numbers, recent industry events not yet in CLI.
Functional Modules
Module A — Prior Quarter Earnings Extraction
Extract from the most recent earnings filing and call:
- Guidance fulfillment: the key metric is always management's own prior guidance vs. actual result — not YoY comparison, not consensus vs. actual. Specifically: what did management guide for Q[N-1] at the end of Q[N-2]? How did Q[N-1] actual compare to that guidance?
- Management outlook: macro/sector views, strategic priorities, capital allocation
- Performance summary: for each guided metric, compute the beat/miss amount and direction
Critical rule for 【一】table columns:
指标 | 管理层此前指引（上上季电话会） | 上季实际值 | 与指引偏差 | 评估- Column 2 = management's own guidance range/midpoint, NOT market consensus
- Column 3 = actual reported value
- Column 4 = (actual − guidance midpoint) / guidance midpoint, with sign
- Column 5 = 超预期 / 基本符合 / 不及预期
If management did not give quantitative guidance for a metric (e.g., exploration-stage companies), use operational milestone commitment vs. actual progress instead.
Use longbridge filing --help to locate prior filings. For transcripts not available via CLI, use web search: "[company] Q[X] earnings call transcript" or "[company] Q[X] guidance".
Module B — Recent Events Tracking
Surface events since the prior earnings release that are relevant to this quarter's results. Categorize by:
- Macro / policy: rate changes, trade policy, regulatory actions
- Industry: competitor moves, sector data, supply chain changes
- Company: product launches, management changes, M&A rumors, major contracts, stock moves
- Market sentiment: analyst rating changes, institutional activity, options implied volatility
Use longbridge news --help for news and longbridge institution-rating --help for rating changes. Use web search for events not yet indexed in CLI.
Each event: timestamp, source, relevance to upcoming earnings.
Module C — Prior Earnings Call Q&A Summary
Extract from the prior earnings call transcript:
- High-frequency analyst questions: topics multiple analysts pressed on (margins, segment growth, capex, etc.)
- Management response: concise conclusion for each key question — not verbatim, just the key judgment
- Verification significance: which of these Q&A topics will be answered or updated by this quarter's results
Source: web search for "[company] Q[X] earnings call transcript".
Module D — Key Focus Framework for This Quarter
Synthesize Modules A–C into an actionable preview:
- Guidance fulfillment checklist: each prior quantitative guidance item → the specific data point to check
- Beat / miss risk factors: what could cause results to surprise in either direction
- 3–5 key questions to watch: written in plain language, combining institutional focus with the user's holding thesis
- Risk flags: tail risks from prior management warnings + recent external events
See [references/scenarios.md](references/scenarios.md) for scenario analysis framework.
Module E — Historical Guidance Fulfillment Tracking
Pull 4–8 quarters of history to establish management's guidance track record:
- Guidance vs. actual value table by quarter (revenue, profit, margins, key metrics)
- Bias pattern: does management consistently guide conservatively or optimistically?
- Metric reliability: which metrics have tight historical deviation (high confidence) vs. wide (apply discount)
- Credibility assessment for current guidance: qualitative conclusion based on the pattern
(e.g. "Revenue guidance has beaten actual by avg 3–5% over 6 quarters — current guidance likely conservative")
Use longbridge financial-report --help, longbridge operating --help, longbridge consensus --help.
Module F — Market Consensus vs. Management Guidance
Identify expectation gaps between the Street and management:
- Current consensus estimates for key metrics (revenue, EPS, margins)
- Comparison with management guidance: is consensus above / below / within the guidance range?
- Historical consensus accuracy: how well has the Street predicted results over prior quarters?
- Expectation gap alerts: flag significant divergences as upside or downside risk
Use longbridge consensus --help and longbridge forecast-eps --help for consensus data.
Output
Output 1 — Inline Conversation Summary
Use exactly the following structure. Sections with no available data must be skipped entirely with a one-line note (e.g. "暂无电话会记录，跳过"). Do not rename, reorder, or add extra sections.
📊 [公司名称（股票代码）] 财报前瞻摘要
财报发布日期：{日期} | 分析日期：{今天}
════════════════════════════════════════
【一】上期业绩指