tradecore-venues

Guide TradeCore venue integrations across Polymarket, Kalshi, Limitless, and Hyperliquid.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/recallnet/polymarket-cross-sectional-momentum --skill tradecore-venues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tradecore-venues
Source: https://github.com/recallnet/polymarket-cross-sectional-momentum/tree/main/.agents/skills/tradecore-venues
Command: npx skills add https://github.com/recallnet/polymarket-cross-sectional-momentum --skill tradecore-venues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Canonical failure-oriented guidance for building, debugging, and extending TradeCore venue integrations across Polymarket, Kalshi, Limitless, and Hyperliquid to reduce recurring mistakes and onboarding time.

Core Features & Use Cases

  • Failure-oriented venue integration notes distilled from recurring agent mistakes, with per-venue references and canonical signing, auth, and websocket patterns.
  • Direct pointers to internal packages that own the relevant TradeCore integration surfaces (ws-venues, venue-auth, funding-clients, venue-wiring, arb-execution, cost-model, etc.).
  • A structured workflow and governance notes that help maintain stable integrations, validate compatibility, and triage venue failures quickly.

Quick Start

Read the workflow and references to align your TradeCore venue integration, signing, and testing with canonical patterns and governance checks.

Frequently Asked Questions about tradecore-venues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the common websocket subscription errors when integrating trading venues?

Common websocket subscription errors stem from incorrect authentication signing and malformed subscription shapes. Canonical failure-oriented patterns triage these venue integration mistakes across Polymarket, Kalshi, Limitless, and Hyperliquid by codifying correct wiring and governance checks.

How do I handle authentication and signing for Polymarket and Kalshi venue integrations?

Authentication and signing for venue integrations require canonical patterns defined in internal packages like venue-auth and ws-venues. Applying these governance notes and package hooks ensures correct TradeCore wiring and reduces recurring signing mistakes across supported platforms.

Can I use this venue integration guidance for platforms beyond Polymarket, Kalshi, Limitless, and Hyperliquid?

This venue integration guidance explicitly applies to Polymarket, Kalshi, Limitless, and Hyperliquid. Compatibility validation is maintained through structured workflow and governance notes, but extending to unlisted venues requires validating against canonical patterns independently.

How do I set up TradeCore venue wiring and testing without repeating common mistakes?

Setting up TradeCore venue wiring requires reading the workflow and references to align with canonical patterns and governance checks. Using included package hooks for ws-venues, venue-wiring, and cost-model ensures correct implementation and testing without recurring mistakes.

Why does my venue integration keep failing despite correct websocket connections?

Venue integration failures persist despite correct websocket connections due to overlooked error triage and governance gaps. Failure-oriented notes distilled from recurring agent mistakes codify common pitfalls in order handling, subscription shapes, and authentication to resolve these issues.