skills/kalshi-prediction-market/SKILL.md
Context and working knowledge for Calci’s prediction-market domain, which is powered by Kalshi. Use this skill whenever the user asks about Calci prediction markets, Kalshi markets, tickers, order books, pricing, settlement, or the Kalshi API/WebSocket.
npx skillsauth add ratacat/claude-skills calci-prediction-marketInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Calci’s prediction-market layer is built on Kalshi. This skill provides the domain model, trading mechanics, and API conventions you need to reason about Calci/Kalshi data and to explain it clearly to users.
Binary event contracts
Implied probability
Fully collateralized
Kalshi uses a strict hierarchy:
Calci mirrors these objects. When you see “market” in Calci UI, clarify whether it’s an event page (container) or a specific market outcome (binary leg).
When interpreting Calci/Kalshi market JSON:
Fees on Kalshi are variable/quadratic, roughly a percent of potential profit; maker orders may be discounted.
can_close_early is true.When asked “how does this resolve?”, reference the series rules and settlement source, then restate in plain language.
Public data (no auth needed):
GET /seriesGET /events (events include their markets)GET /marketsGET /market/{ticker}GET /market/orderbookGET /market/candlesticksGET /market/tradesGET /exchange/statusTrading/account (auth required):
POST /orders, DELETE /orders/{id}, GET /orders/{id}POST /order-groups and related order‑group endpointsGET /portfolio/balance, GET /portfolio/positions, GET /portfolio/fillsAuth uses an API key id plus RSA signature headers:
KALSHI-ACCESS-KEYKALSHI-ACCESS-TIMESTAMPKALSHI-ACCESS-SIGNATUREReal‑time updates arrive via WebSocket subscriptions to tickers.
For more detail, see reference.md.
tools
Build and test iOS apps on simulator using XcodeBuildMCP
development
Produces concise, clear documentation by applying Elements of Style principles. Use when writing or improving any technical documentation (READMEs, guides, API docs, architecture docs). Not for code comments.
testing
Use when user asks to create, write, edit, or test a skill. Also use when documenting reusable techniques, patterns, or workflows for future Claude instances.
testing
Execute work plans efficiently while maintaining quality and finishing features