longbridge-etf-analysis
ETF analysis framework via Longbridge — product screening (AUM/expense ratio/index), tracking error, liquidity (bid-ask spread/volume), premium/discount (NAV vs market price), and A-share ETF allocation insights. Triggers: "ETF分析", "ETF选择", "ETF跟踪误差", "ETF溢价", "ETF流动性", "ETF费率", "ETF规模", "宽基ETF", "行业ETF", "指数基金", "ETF分析", "ETF選擇", "ETF追蹤誤差", "ETF溢價", "ETF流動性", "ETF費率", "ETF規模", "指數基金", "ETF analysis", "ETF selection", "tracking error", "ETF premium discount", "ETF liquidity", "expense ratio", "broad market ETF", "sector ETF", "index fund".
npx skills add majiayu000/claude-skill-registry --skill longbridge-etf-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# longbridge-etf-analysis Prompt-only analysis skill. Analyses ETFs across five dimensions: product profile, tracking error, liquidity, premium/discount, and allocation fit — supporting both US-listed ETFs and A-share ETFs. > **Response language**: match the user's input language — Simplified Chinese / Traditional Chinese / English. ## When to use - *"QQQ 和 QQQM 哪个更适合长期持有?"* / *"QQQ vs QQQM for long-term holding?"* - *"这只 ETF 的跟踪误差大不大?"* / *"Is the tracking error on this ETF high?"* - *"510300 现在溢价还是折价?"* / *"Is 510300 trading at a premium or discount?"* - *"帮我分析沪深300 ETF 的流动性"* / *"Analyse the liquidity of CSI 300 ETFs"* - *"行业 ETF 怎么选?"* / *"How to pick a sector ETF?"* For index constituent stocks route to `longbridge-constituent`. For individual stock valuation route to `longbridge-valuation`. ## CLI Run `longbridge <subcommand> --help` to verify exact flags. ```bash # ETF quote — price, volume, market cap, turnover longbridge quote <ETF_SYMBOL> --format json # Constituent holdings — underlying stocks and weights longbridge constituent <ETF_SYMBOL> --format json # Historical price — compute tracking error vs index longbridge kline <ETF_SYMBOL> --period day --count 60 --format js
- When to use
- CLI
- Five-dimension analysis
- 1. Product profile
- 2. Tracking error
- 3. Liquidity
- 4. Premium / discount (NAV vs market price)
- 5. Allocation fit
- Workflow
- Output template
- Error handling
- MCP fallback
- Related skills
- File layout
ETF quote — price, volume, market cap, turnover longbridge quote <ETF_SYMBOL> --format json Constituent holdings — underlying stocks and weights longbridge constituent <ETF_SYMBOL> --format json Historical price — compute tracking error vs index longbridge kline <ETF_SYMBOL> --period day --count 60 --format json Index / benchmark price for comparison longbridge kline <BENCHMARK_SYMBOL> --period day --count 60 --format json Valuation indices (PE/PB of ETF if available) longbridge calc-index <ETF_SYMBOL> --format json
What does the longbridge-etf-analysis skill do?
ETF analysis framework via Longbridge — product screening (AUM/expense ratio/index), tracking error, liquidity (bid-ask spread/volume), premium/discount (NAV vs market price), and A-share ETF allocation insights. Triggers: "ETF分析", "ETF选择", "ETF跟踪误差", "ETF溢价", "ETF流动性", "ETF费率", "ETF规模", "宽基ETF", "行业ETF", "指数基金", "ETF分析", "ETF選擇", "ETF追蹤誤差", "ETF溢價", "ETF流動性", "ETF費率", "ETF規模", "指數基金", "ETF analysis", "ETF selection", "tracking error", "ETF premium discount", "ETF liquidity", "expense ratio", "broad market ETF", "sector ETF", "index fund".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill longbridge-etf-analysis --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.
