calci-prediction-market

Explain Kalshi prediction-market data, pricing, order books, and settlement workflows.

49|9|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/ratacat/claude-skills --skill calci-prediction-market
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: calci-prediction-market
Source: https://github.com/ratacat/claude-skills/tree/main/skills/kalshi-prediction-market
Command: npx skills add https://github.com/ratacat/claude-skills --skill calci-prediction-market

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Context and working knowledge for Calci’s Kalshi-based prediction markets, enabling clear reasoning about Kalshi data and the Kalshi API/WebSocket.

Core Features & Use Cases

  • Data hierarchy: Series → Event → Market
  • Price, bid/ask, last price, volume, and settlement concepts
  • Public vs private endpoints, authentication, and streaming updates

Quick Start

Example: "Explain market TICKER with Yes/No bids" or "Describe market XYZ's settlement rules."

Frequently Asked Questions about calci-prediction-market

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

FAQPage Schema
How do I understand Kalshi prediction market data structures and pricing?

Kalshi prediction markets organize data as Series → Event → Market hierarchies. Prices represent binary Yes/No outcomes; convert bid/ask spreads to implied probabilities by dividing price by 100. The API exposes these structures with real-time pricing, volume, and settlement metadata across public endpoints.

What's the difference between Kalshi's Yes and No prices, and how do I interpret them as probabilities?

Kalshi prices range 0–100 for binary markets. A Yes price of 65 implies 65% probability; No price of 35 implies 35% probability. Prices sum to 100. Use these conversions to reason about market expectations and translate between Kalshi UI terms and Calci domain concepts.

How do I access Kalshi market data via API and WebSocket?

Kalshi provides public endpoints for market, order book, and trade data, plus WebSocket streaming for real-time updates. Authentication uses API credentials for private endpoints. Map Kalshi API responses to Calci structures; cite specific endpoints and authentication methods when building integrations.

What order types and settlement rules apply to Kalshi prediction markets?

Kalshi supports limit and market orders with standard trading rules. Settlement occurs at event resolution; markets resolve to Yes (100) or No (0) based on event outcome. Understanding order types, trading halts, and settlement workflows is essential for modeling Kalshi-based trading logic.

Can I use Kalshi prediction markets for portfolio analysis and risk modeling?

Yes. Map Kalshi markets to Calci portfolio structures by treating each market as a binary asset. Use implied probabilities from prices for scenario analysis, and leverage order book depth and volume data to assess liquidity and execution risk.

What are the limitations of Kalshi's public API for real-time trading workflows?

Public endpoints have rate limits and latency; WebSocket streaming mitigates this for live updates. Not all data is available on public endpoints—private data requires authentication. Plan integrations around these constraints and fallback to polling if streaming is unavailable.