Agent skill · Business & Finance

longbridge-consensus

Analyst consensus snapshot for listed companies via Longbridge — current revenue / EPS / target-price consensus estimates and analyst rating distribution. For revision direction, beat/miss tracking, and PEAD signals use longbridge-earnings-revision. Triggers: "一致预期", "分析师预期", "EPS预测", "目标价", "分析师评级分布", "买入评级", "卖出评级", "一致預期", "分析師預期", "EPS預測", "目標價", "分析師評級分佈", "買入評級", "賣出評級", "analyst consensus", "EPS forecast", "target price", "analyst rating distribution", "buy sell hold", "price target consensus", "TSLA.US consensus", "700.HK analyst estimates".

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill longbridge-consensus --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Version: 1.0.0
Declared author: longbridge
Path: skills/analysis/longbridge-consensus/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# longbridge-consensus Prompt-only analysis skill. Orchestrates Longbridge CLI commands to surface analyst consensus estimates, estimate revision trends, beat/miss history, and post-earnings announcement drift (PEAD) signals. > **Response language**: match the user's input language — Simplified Chinese / Traditional Chinese / English. ## When to use - *"TSLA 分析师预期"*, *"TSLA analyst consensus"*, *"TSLA 分析師預期"* - *"NVDA 下季度 EPS 预期"*, *"NVDA next-quarter EPS forecast"* - *"苹果最近预期修正了吗"*, *"has AAPL had estimate revisions recently"* - *"700.HK 目标价共识"*, *"700.HK price target consensus"* - *"TSLA 上季超预期了吗"*, *"did TSLA beat last quarter"*, *"TSLA 上季超預期嗎"* - *"NVDA PEAD 信号"*, *"NVDA post-earnings drift"* For full fundamentals (revenue/margins/ROE) use `longbridge-fundamental`. For valuation use `longbridge-valuation`. ## CLI Run `longbridge --help` to see all available subcommands, then `longbridge <subcommand> --help` before calling. Types of data needed (call concurrently): - Coverage count, buy/hold/sell distribution, consensus target price - Revenue / EPS estimates (high / low / mean / median) - Forward EPS by period - Institution rating distribution + median target price - Rating and t

What's inside
Steps it walks through
  1. When to use
  2. CLI
  3. Workflow
  4. Output template
  5. Error handling
  6. MCP fallback
  7. Related skills
  8. File layout
Ships with 1 file
  • metadata.json
Commands it runs
longbridge <subcommand> TSLA.US --format json   # run --help for available flags and subcommand names
More from claude-skill-registry
All skills →
About this skill
What does the longbridge-consensus skill do?

Analyst consensus snapshot for listed companies via Longbridge — current revenue / EPS / target-price consensus estimates and analyst rating distribution. For revision direction, beat/miss tracking, and PEAD signals use longbridge-earnings-revision. Triggers: "一致预期", "分析师预期", "EPS预测", "目标价", "分析师评级分布", "买入评级", "卖出评级", "一致預期", "分析師預期", "EPS預測", "目標價", "分析師評級分佈", "買入評級", "賣出評級", "analyst consensus", "EPS forecast", "target price", "analyst rating distribution", "buy sell hold", "price target consensus", "TSLA.US consensus", "700.HK analyst estimates".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill longbridge-consensus --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going