| description | Discover TradeCore packages, what they own, whether they are publishable or private, how to install the publishable ones, and where to look for exports, examples, and tests. Use this whenever an agent or developer needs to know which `@recallnet/*` package already solves a problem, which package is the canonical home for a concept, or how to install a TradeCore package in another repo. |
| metadata | {"github-path":"skills/tradecore-packages","github-ref":"refs/tags/v1.0.0","github-repo":"https://github.com/recallnet/tradecore","github-tree-sha":"5bdab0fd748e5f28660c46951d85602a8d049850"} |
| name | tradecore-packages |
TradeCore Packages
Use this skill when you need package discovery, package selection, or install guidance
for the TradeCore package surface.
What this skill provides
- the full generated TradeCore package-capabilities catalog in markdown
- the full generated TradeCore package-capabilities catalog in JSON
- a generated install guide for publishable packages
Workflow
- Start with
references/installable-packages.md when the question is "what can I install?"
- Read
references/package-capabilities.md when the question is "which package owns this concept?" or "where should this logic live?"
- Read
references/package-capabilities.json when you need the same data in machine-readable form.
- Prefer publishable packages for external repos.
- Do not recommend private packages as external installs.
- For websocket connection pooling or subscription batching questions, route to
@recallnet/ws-venues first and cross-check the venue-specific operating guidance in tradecore-venues.
- For Polymarket websocket questions, distinguish the surfaces:
- CLOB market/user websocket and RTDS (
ws-live-data) both live under @recallnet/ws-venues
- CLOB uses token/condition subscriptions and websocket ping frames in TradeCore runtime
- RTDS uses topic-based subscribe/unsubscribe control messages and requires literal text
PING every 5 seconds
- If the question is specifically about sharing Kalshi's single local websocket connection across multiple local projects on one machine, surface
@recallnet/kalshi-ws-relay as an opt-in local-development package. Do not suggest it as a default dependency for TradeCore executors.
- Call out the local resiliency behavior when relevant: the relay client auto-reconnects to a restarted daemon and replays active subscriptions.
- Call out the daemon-side protections when relevant: silent upstream stalls trigger a heartbeat reconnect, untargeted Kalshi control frames are not fanned out to local clients, and late shared ticker subscribers reuse cached ticker state without disrupting the shared upstream subscription.
- For Polymarket relayer REST questions, route to
@recallnet/funding-clients and its PolymarketRelayerClient. For Polymarket merge/redeem, claim, or recent inventory recovery flows, route to @recallnet/polymarket-redeemer before suggesting ad hoc SDK wiring. Call out that relayer API key auth is a separate surface from ordinary CLOB auth.
Install this skill
gh skill install recallnet/tradecore tradecore-packages --agent codex
Notes
- The bundled references are generated from TradeCore's canonical package-capability catalog.
- If you are inside the TradeCore repo,
pnpm repo:capabilities <term> is the live search entrypoint.
- The install guide is additive. The full catalog remains the source of truth for ownership, exports, examples, and internal dependencies.
