# Research Markets with Longbridge Data

Investment research often requires many disconnected data checks. This skill combines Longbridge data with structured workflows for faster, consistent market analysis.

## Install

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

## Metadata

- Status: approved
- Slug: longbridge-longbridge-research
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r3
- Version status: not\_bumped
- Tree hash: fce3a2ee7b4c9088924e106e7331dccbbc4adb351b5a14b84eb7af7b893f3e9c
- Author: longbridge
- GitHub username: longbridge
- License: MIT
- Repository: https://github.com/longbridge/skills/tree/main/skills/longbridge-research
- Ref: 656be3040aef5c047555a908cd5c695d22a4a548
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 69
- Public page: https://skillstore.pages.dev/skills/longbridge-longbridge-research
- Manifest: https://skillstore.pages.dev/api/skills/longbridge-longbridge-research/manifest

## Capabilities

- Retrieves analyst rating distributions and consensus price targets for supported securities.
- Summarizes forward earnings and revenue forecasts by reporting period.
- Builds finance calendars covering earnings, dividends, listings, market closures, and macroeconomic events.
- Examines shareholders, fund holders, insider filings, institutional portfolios, and short-selling data.
- Ranks industries and maps peer groups for supported markets.
- Structures investment proposals, stock briefs, competitive analyses, financial plans, and digital-asset research.

## Use Cases

- Evaluate a Stock: Combine analyst expectations, valuation, ownership, short interest, and recent events into a balanced research brief.
- Prepare an Investment Memo: Organize a thesis, financial evidence, peer comparisons, catalysts, risks, and monitoring criteria for review.
- Track Market Events: Create a prioritized calendar across selected markets and explain potential effects without direct trading instructions.

## Prompt Templates

### Check Analyst Expectations

```
Summarize analyst ratings, the consensus price target, and forward earnings estimates for {symbol}. Separate sourced facts from interpretation.
```

### Build a Finance Calendar

```
Build a finance calendar for {date_range}. Prioritize {markets} and {symbols}, explain likely impacts, and include source dates.
```

### Compare Industry Peers

```
Compare {company} with {peer_1}, {peer_2}, and {peer_3}. Benchmark growth, margins, valuation, analyst sentiment, moat, catalysts, and risks.
```

### Prepare an Investment Proposal

```
Prepare an investment proposal for {symbol} over {horizon}. Include thesis, bear case, valuation, ownership changes, short interest, catalysts, and monitoring triggers.
```

## Limitations

- Most market data requires the Longbridge CLI, plugin, or MCP tools to be available.
- DeFi and on-chain workflows depend on current WebSearch results from external sources.
- Coverage and reporting frequency vary by market, security, and data source.
- Portfolio-aware calendar analysis requires account authorization and access to private holdings and watchlists.

## Best Practices

- Provide full market-qualified symbols, such as NVDA.US or 700.HK, and specify the research period.
- Request source dates and distinguish reported facts, consensus estimates, and analytical conclusions.
- Use several evidence types and include both bullish and bearish interpretations.

## Anti Patterns

- Do not treat consensus estimates, price targets, or historical relationships as guaranteed outcomes.
- Do not request direct buy or sell instructions without defining risk, horizon, and decision criteria.
- Do not access holdings or watchlists without confirming authorization and intended portfolio scope.

## Security Audit

- Audited at: 2026-08-08T09:56:11.623\+00:00
- Summary: All 46 static alerts are false positives caused by Markdown formatting, CLI documentation, or ordinary prose. No shell backtick execution, reconnaissance, prompt injection, or exfiltration intent was found. However, the finance-calendar workflow accesses private portfolio data despite metadata stating that login is unnecessary.

## Stats

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