Longbridge Earnings

Earnings Update Skill

Response language: match the user's input language — Simplified Chinese / Traditional Chinese / English. Both the DOCX report body and the in-chat summary follow the user's language; chart labels, axis titles, and file names always stay in English.

When to Use

Do not trigger if: user wants an initiation report.

Data Sources

Priority: CLI (primary) → Web Search (supplement)

Use the Longbridge CLI for all market data. Before using any command, run longbridge <command> --help to check available options — the CLI is updated frequently.

CLI + Python pattern: prefer reading from a file over piping into python3 -c. Multi-line JSON with embedded quotes can hit shell-quoting edge cases (especially under zsh's -c argument handling), so the safer pattern is:

longbridge institution-rating 700.HK --format json > /tmp/rating.json
python3 -c "import json; d = json.load(open('/tmp/rating.json')); print(d)"

If you do prefer pipes, use a heredoc-fed Python script (python3 <<'PY' ... PY) or save to a file and run a .py file.

CLI docs: https://open.longbridge.com/zh-CN/docs/cli/ MCP endpoint: https://openapi.longbridge.com/mcp

CLI discovery: Run longbridge --help to see all available subcommands, then longbridge <subcommand> --help before calling. Do not assume subcommand names — the CLI is updated frequently. Broad categories needed for earnings analysis:

• Earnings calendar / upcoming earnings dates
• Financial statements (income, balance sheet, cash flow)
• Earnings snapshot / AI beat-miss summary
• Analyst consensus & EPS estimates
• Quote & valuation metrics
• Price history (candlestick)
• Analyst ratings & target prices
• Regulatory filings (10-Q, 10-K, 8-K)
• News

Web Search supplements for content not in CLI: consensus estimates vintage, earnings call transcripts, M&A precedent data.

Execution Workflow

Step 1 — Identify reporting period Use longbridge filing --help to find the latest quarterly or annual filing. Confirm the period with the user before proceeding.

Step 2 — Collect data & analyze See references/workflow.md

Step 3 — Update valuation See references/valuation-methodologies.md

Step 4 — Generate DOCX report See references/report-structure.md

Step 5 — Output conversation summary See references/summary-card-spec.md

Output

1. DOCX report: [SYMBOL]_Q[N]_[YEAR]_Earnings_Update.docx (8-12 pages, 8-12 charts)
2. Conversation summary: 8-module structured output directly in chat

IMPORTANT: Do NOT append a Sources section or reference links to the conversation output. All citations belong in the DOCX only.

MCP fallback

If the local longbridge CLI is unavailable (command not found: longbridge) and the user has run claude mcp add --transport http longbridge https://openapi.longbridge.com/mcp, the same data is reachable through MCP. Subcommand → MCP tool mapping:

When the CLI is unavailable, fall back to the MCP server. Discover available tools from the MCP server's tool list at runtime — do not rely on hardcoded tool names.

MCP-only extras worth pulling in for Step 3 valuation:

• the equivalent MCP tool — historical PE/PB time series for percentile context
• the equivalent MCP tool — industry-relative position
• the equivalent MCP tool / profit_analysis_detail — only if the user wants a portfolio-level P&L view alongside the single-name update

Related skills

This skill is the heaviest in the family (institutional-grade 8–12 page DOCX). For lighter or differently-framed asks, defer to a sibling:

If the user wants the full earnings DOCX plus one of the above (e.g. "earnings update on TSLA and how it compares to Ford"), do this skill first, then chain to the other.

Reference Files