tradecore-venues

description	Canonical failure-oriented venue integration guidance for TradeCore-supported venues. Use this whenever an agent is building, debugging, or extending a venue integration; sizing orders; parsing websocket messages; handling fills; or triaging venue error responses for Polymarket, Kalshi, Limitless, or Hyperliquid.
metadata	{"github-path":"skills/tradecore-venues","github-ref":"refs/tags/v1.0.0","github-repo":"https://github.com/recallnet/tradecore","github-tree-sha":"a36032132ceed32fc19052ea62b39c95526820a9"}
name	tradecore-venues

TradeCore Venues

Use this skill when you need venue-specific integration guidance for the TradeCore venue surface.

What this skill provides

• failure-oriented venue integration notes distilled from recurring agent mistakes
• canonical per-venue references for websocket handshakes, auth, sizing, fills, and errors
• direct pointers to the internal @recallnet/* packages that own the relevant TradeCore integration surfaces
• a compact starting point for Polymarket, Kalshi, Limitless, and Hyperliquid without pretending to replace the vendor docs

Workflow

1. Start with the venue-specific file in references/ for the venue you are integrating or debugging.
2. Read the sections in order:
   • Stable Reference for denomination/auth/protocol facts
   • First Contact for handshake/subscription flow and the most common initial parsing mistake
   • Order Constraints and Fill Handling before writing execution code
   • Error Codes before triaging venue failures
   • Volatile — Verify Before Use before trusting rate limits, fee tiers, or fast-moving policy details
3. Check denomination before writing any parser, signer, or sizing code:
   • ask whether the venue price is a probability in dollars (0.01 to 0.99), a fixed-point dollar string, a cent integer, or a direct quote-asset price
   • ask whether size is whole contracts, decimal shares, or raw token units
   • use the venue file's TradeCore Package Hooks and denomination bullets before inventing conversions
4. Use these files as an internal index:
   • keep the TradeCore-specific gotchas
   • click through to the linked official docs for stable API details instead of re-deriving them from memory
5. When you need to know which package to import or extend:
   • use the TradeCore Package Hooks subsection in the venue file first
   • then cross-check with the tradecore-packages skill or pnpm repo:capabilities <venue-or-concept>
6. If venue behavior contradicts the guide, file a skunkworks issue labeled venue-knowledge before closing the PR that discovered it.

References

• references/Polymarket.md — Polymarket CLOB order sizing, token IDs, websocket market/user flow, RTDS (ws-live-data) heartbeat/subscription rules, and common marketable-order mistakes
• references/Kalshi.md — Kalshi contract-denominated order handling, RSA websocket auth, private fill flow, and lifecycle gotchas
• references/Limitless.md — Limitless Socket.IO market and position streams, CTF order signing, and current documentation gaps that require validation
• references/Hyperliquid.md — Hyperliquid public + account websocket channels, correlated websocket post flow, and user/fill data handling
• tradecore-packages skill — canonical ownership and installability for the @recallnet/* package surface when the venue ref tells you which package family to use

Governance

• These references use @recallnet/docs-governance-policy style frontmatter.
• If a file's review_by date is expired, treat it as potentially stale and flag it rather than trusting it blindly.
• Use [TODO: validate] text as a hard signal that the point needs live confirmation before use in production-sensitive code.

Install this skill

gh skill install recallnet/tradecore tradecore-venues --agent codex

Notes

• This skill is intentionally failure-oriented. It documents the mistakes agents actually make, not a feature tour of the venue APIs.
• Denomination is one of the highest-value failure surfaces in this skill. Before trusting any venue integration, confirm:
  • what unit price uses on the wire
  • what unit size uses on the wire
  • what unit TradeCore normalizes into after parsing
• The intended future complement is a lightweight canary per venue that asserts stable invariants such as denomination, tick size, and minimum order sizing against a live or fixture response. Those canaries are not part of this change, but they are the expected mechanical backstop for the expiring-doc governance model.