# Analyze Earnings Before and After Results

Earnings data is fragmented across statements, estimates, calls, and market feeds. This skill organizes those inputs into timely previews, summaries, and valuation reports.

## Install

```bash
npx skillstore add longbridge/longbridge-earnings
```

## Metadata

- Status: approved
- Slug: longbridge-longbridge-earnings
- Skillstore revision: r2
- Version status: missing
- Tree hash: a62d2ac981898e1c385ce8f2f33217ba7f32c9381389acb40d9fc6e7ea1b0c2c
- Author: longbridge
- GitHub username: longbridge
- License: MIT
- Repository: https://github.com/longbridge/skills/tree/main/skills/longbridge-earnings
- Ref: 656be3040aef5c047555a908cd5c695d22a4a548
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem, network
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/longbridge-longbridge-earnings
- Manifest: https://skillstore.pages.dev/api/skills/longbridge-longbridge-earnings/manifest

## Capabilities

- Determines whether a request needs a pre-earnings preview or post-earnings analysis.
- Collects Longbridge statements, consensus, ratings, segments, news, quotes, and price history in parallel.
- Creates concise post-earnings cards covering surprises, trends, segments, thesis changes, expectations, and risks.
- Compares prior management guidance with actual performance for upcoming earnings preparation.
- Builds Markdown research reports with DCF, trading-comparable, and relevant precedent-transaction valuation.
- Responds in English, Simplified Chinese, or Traditional Chinese based on the user's language.

## Use Cases

- Prepare for an Upcoming Release: Review prior guidance, recent events, consensus gaps, management credibility, and key questions before results.
- Summarize Reported Results: Turn quarterly data into a concise beat-or-miss card with segment, margin, outlook, and risk analysis.
- Update a Valuation View: Create a sourced research report with revised estimates, scenario valuation, target price, and rating rationale.

## Prompt Templates

### Quick Earnings Summary

```
Summarize the latest reported earnings for [SYMBOL]. Show major beats or misses, guidance changes, segment trends, and key risks.
```

### Upcoming Earnings Preview

```
Prepare a pre-earnings preview for [SYMBOL]. Compare prior guidance with actual performance and identify three to five questions for this release.
```

### Detailed Results Review

```
Analyze [SYMBOL] for [QUARTER]. Explain KPI surprises, margin drivers, segment performance, management guidance, estimate revisions, thesis changes, and market expectations.
```

### Full Valuation Report

```
Create a full Markdown earnings report for [SYMBOL]. Include sourced estimates, DCF, peer multiples, relevant transactions, scenarios, target price, rating, and risks.
```

## Limitations

- Requires the Longbridge CLI, a configured Longbridge MCP connection, or supplemental public web data.
- Transcript, whisper-number, and options-implied-move coverage depends on available web search results.
- Source data can be delayed, incomplete, stale, or inconsistent across reporting periods.
- Outputs are research aids, not personalized investment advice or guaranteed forecasts.

## Best Practices

- Specify the ticker, exchange, reporting quarter, and whether results are upcoming or released.
- Verify every source covers the same fiscal period before comparing results or estimates.
- Treat ratings and target prices as research inputs, then apply independent judgment.

## Anti Patterns

- Do not request precise conclusions when the ticker or reporting period is ambiguous.
- Do not treat current consensus as the historical estimate baseline without checking its date.
- Do not use generated ratings or price targets as automatic trading instructions.

## Security Audit

- Audited at: 2026-08-08T09:28:15.688\+00:00
- Summary: Most static findings are Markdown formatting, ordinary financial prose, or safe argument-array subprocess use. Confirmed risks include unquoted symbol placeholders, a predictable user-derived temporary path, stale cached responses, and an external MCP trust boundary; no prompt injection or credential-exfiltration intent was found.

## Stats

- Views: 2
- Downloads: 14
- Favorites: 1
- Popularity score: 0