Original Summary

We build small tools on our own market data API and open them up. This is the latest one, and it turned out to be the one people reacted to most, probably because the thing it measures is easy to compute and almost nobody computes it. What it checks Most people can describe their positions. Far fewer can describe their concentration. The check computes four things straight off the account: HHI, the sum of squared weights. Above 2500 is the conventional over-concentration threshold. Largest single weight. Top three combined. Splits by market, currency and sector. On the demo account below: HHI 3922, largest holding 58.5%, top three 85.7%, and 96.7% of it in one currency. We build small tools on our own market data API and open them up. This one computes portfolio concentration off a live brokerage account. It got the most reaction internally, probably because the thing it measures is easy to compute and almost nobody computes it. Output on a demo account: CONCENTRATION HHI index 3922 over-concentrated (>2500) Largest holding 58.5% 700.HK Top 3 combined 85.7% 700.HK · 9988.HK · 9888.HK EXPOSURE Market HK 96.7% US 3.3% Currency HKD 96.7% USD 3.3% Sector Internet content 74.0% · Retail 14.8% · Autos 11.2% HHI is the sum of squared position weights. Above 2500 is the conventional over-concentration line. Most people can list their positions and have never worked this out. It runs threshold alerts over the same numbers: RISK ALERTS HIGH Single position > 30% 700.HK 58.5% HIGH Loss over 20% 1211.HK -25.1% MID HHI above 2500 3922 MID Top 3 combined > 70% 85.7% LOW FX outside peg band 7.5-8.0 HKD/USD 7.0001 Where the data comes from One CLI command reads the whole account: positions, quantities, cost basis, market values, across every market the account holds. The skill calls that, then does the arithmetic locally. Nothing about the portfolio leaves the machine except the API calls needed to price it. Installing it Download the zip, import it into an assistant that supports skill packages, ask it to run. Roughly 20 seconds per six tickers, most of it waiting on data. One prerequisite we could not design around: the CLI has to be installed and logged in first, or the skill has nothing to read. What it does not do No recommendations, no price targets, no order placement, nothing personalised. It reports the composition of the account and has no view on whether that composition suits you. It is a snapshot rather than a monitor. You run it, you get a reading. No scheduling or alerting yet. Repo and install guide: github.com/longbridge/longbridge-mcp What we would like input on The prerequisite problem. A tool that cannot do anything until you go and install a second tool is a bad first thirty seconds, and we have not found a good pattern for it. If you have shipped a skill or plugin with a hard dependency, how did you handle first run?   submitted by   /u/Longbridge_AI [link]   [comments]

  • 情报分类：商业与市场研究
  • 分类依据：内容涉及商业、投资或市场动态
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/17 11:15:27