# Analyze Markets with Longbridge

Market research and account analysis often require several disconnected tools. This skill organizes Longbridge CLI, MCP, and SDK workflows for data, content, portfolios, and development.

## Install

```bash
npx skillstore add longbridge/longbridge
```

## Metadata

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

## Capabilities

- Retrieve quotes, candlesticks, intraday data, market sentiment, and IPO information through documented CLI commands.
- Collect company news, regulatory filings, community topics, analyst estimates, and valuation metrics.
- Inspect positions, assets, profit and loss, margin details, deposits, and withdrawal history after authorization.
- Guide OAuth setup for the Longbridge CLI, hosted MCP service, and supported SDKs.
- Provide Python, Go, and Rust examples for quote, content, portfolio, and order APIs.
- Support symbols from United States, Hong Kong, mainland China, Singapore, and cryptocurrency markets.

## Use Cases

- Research a Security: Combine price history, valuation, analyst estimates, news, and filings for a structured company review.
- Review a Portfolio: Summarize holdings, profit and loss, cash, margin, and concentration using authorized account data.
- Build a Market Integration: Choose CLI, MCP, Python, Go, or Rust workflows for a market-data or trading application.

## Prompt Templates

### Check a Quote

```
Get the latest available quote for [SYMBOL]. Show the market session, timestamp, price, and data source.
```

### Review Company Developments

```
Summarize recent news and filings for [SYMBOL]. Separate confirmed facts from interpretation and include source dates.
```

### Analyze My Portfolio

```
Review my authorized portfolio. Summarize allocation, profit and loss, concentration, cash, margin, and major risks without placing orders.
```

### Design an SDK Workflow

```
Design a [Python, Go, or Rust] workflow for [GOAL]. Use OAuth, handle rate limits, validate inputs, and require confirmation before financial actions.
```

## Limitations

- Live features require Longbridge access, OAuth authorization, and appropriate account or market-data permissions.
- Availability depends on account region, quote packages, market hours, and documented rate limits.
- CLI flags can change, so current built-in help should be checked before running complex commands.
- Financial outputs require independent verification, and every order action requires explicit confirmation.

## Best Practices

- Verify symbols, market suffixes, timestamps, and data freshness before presenting conclusions.
- Request only necessary OAuth scopes and revoke unused authorizations from account security settings.
- Require explicit user confirmation immediately before submitting, replacing, or canceling an order.

## Anti Patterns

- Do not pipe remote installers directly into a shell or PowerShell interpreter.
- Do not present delayed, incomplete, or estimated data as a live confirmed quote.
- Do not expose tokens, account identifiers, balances, or transaction history beyond the requested task.

## Security Audit

- Audited at: 2026-08-08T09:15:04.49\+00:00
- Summary: The audit confirms direct remote-script execution, local OAuth token storage, and an authenticated order-submission example. Most other findings are false positives from Markdown formatting, language imports, async tasks, relative links, or expected official URLs. Semantic review also found skill-routing manipulation and missing confirmation safeguards in SDK order examples.

## Stats

- Views: 0
- Downloads: 7
- Favorites: 1
- Popularity score: 0