longbridge-ipo
IPO full-lifecycle management via Longbridge Securities — HK/US IPO calendar, subscription/pending/listed rosters, individual IPO details and timelines, account IPO orders, and P&L analysis. Calendar and stock lists require no login; account order and P&L queries require Trade permission. Triggers: "新股", "IPO", "打新", "新股申购", "新股日历", "IPO日历", "待上市", "认购", "新股盈亏", "上市首日", "打新收益", "新股申購", "新股日曆", "IPO日曆", "認購", "新股盈虧", "new IPO", "IPO calendar", "subscribe IPO", "new listing", "IPO orders", "IPO profit loss", "new stock listing", "upcoming IPO", "grey market".
npx skills add majiayu000/claude-skill-registry --skill longbridge-ipo --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-ipo IPO full-lifecycle hub: browse upcoming and recent IPOs in HK and US markets, view individual IPO details, and query your own IPO orders and profit/loss. > **Response language**: match the user's input language — Simplified Chinese / Traditional Chinese / English. ## When to use - *"近期港股新股"*, *"港股認購中"*, *"HK IPO subscriptions"* → `longbridge ipo subscriptions` - *"待上市新股"*, *"等待上市"*, *"pending listings HK"* → `longbridge ipo wait-listing` - *"最近上市的港股"*, *"近期上市"*, *"recently listed HK"* → `longbridge ipo listed` - *"美股认购"*, *"US IPO subscriptions"* → `longbridge ipo us-subscriptions` - *"美股新上市"*, *"US recent IPOs"* → `longbridge ipo us-listed` - *"IPO 日历"*, *"新股日程"*, *"IPO calendar"* → `longbridge ipo calendar` - *"XXXX.HK 打新详情"*, *"IPO detail"* → `longbridge ipo detail <SYMBOL>` - *"我的打新订单"*, *"我的新股申購記錄"*, *"my IPO orders"* → `longbridge ipo orders` (requires login + Trade) - *"我打新赚了多少"*, *"IPO 盈亏"*, *"IPO profit/loss"* → `longbridge ipo profit-loss` (requires login + Trade) For general earnings/dividend calendars, defer to `longbridge-calendar`. For account orders on secondary-market stocks, defer to `longbridge-orders`. ## Workflow **Public data (no login required
- When to use
- Workflow
- CLI
- Output
- Error handling
- MCP fallback
- Related skills
- File layout
Public — no login required longbridge ipo calendar --format json # Full IPO calendar (all markets) longbridge ipo subscriptions --format json # HK IPOs currently open for subscription longbridge ipo wait-listing --format json # HK IPOs pending listing longbridge ipo listed --format json # HK recently listed IPOs longbridge ipo us-subscriptions --format json # US IPOs currently open for subscription longbridge ipo us-listed --format json # US recently listed IPOs longbridge ipo detail <SYMBOL> --format json # Individual IPO details + timeline Account — requires login with Trade permission longbridge ipo orders --format json # My IPO subscription orders
What does the longbridge-ipo skill do?
IPO full-lifecycle management via Longbridge Securities — HK/US IPO calendar, subscription/pending/listed rosters, individual IPO details and timelines, account IPO orders, and P&L analysis. Calendar and stock lists require no login; account order and P&L queries require Trade permission. Triggers: "新股", "IPO", "打新", "新股申购", "新股日历", "IPO日历", "待上市", "认购", "新股盈亏", "上市首日", "打新收益", "新股申購", "新股日曆", "IPO日曆", "認購", "新股盈虧", "new IPO", "IPO calendar", "subscribe IPO", "new listing", "IPO orders", "IPO profit loss", "new stock listing", "upcoming IPO", "grey market".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill longbridge-ipo --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.
