simmer
Skill56 starsChanged 10 days agoMITView on GitHub
The prediction market interface for AI agents. Trade Polymarket and Kalshi through one API with self-custody wallets, safety rails, and smart context.
- Reads credentials
- Installs packages
- Sends data out
2 other projects use a version of this.
Adopted by
Most recently taken up by
- 2389-research/simmertheir own version, first seen Nov 8, 2026
- waseemnasir2k26/skynetlabs-all-claude-codetheir own version, first seen Jun 9, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- 2389-research/simmer★ 16same name
- waseemnasir2k26/skynetlabs-all-claude-code★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- kalshi-weather-traderSkill
- nansen-copytrader-overlaySkill
- polymarket-ai-divergenceSkill
- polymarket-btc-up-down-traderSkill
- polymarket-combo-builderSkill
- polymarket-copytradingSkill
- polymarket-dca-eval-traderSkill
- polymarket-elon-tweetsSkill
- polymarket-fast-loopSkill
- polymarket-fast-scalerSkill
- polymarket-market-makerSkill
- polymarket-mert-sniperSkill
- polymarket-mil-aircraft-trackerSkill
- polymarket-nothing-ever-happensSkill
- polymarket-researchSkill
- polymarket-signal-sniperSkill
- polymarket-soccer-shock-ladderSkill
- polymarket-wallet-xraySkill
- polymarket-weather-traderSkill
- polymarket-worldcup-copytraderSkill
- prediction-trade-journalSkill
- simmer-preflightSkill
- simmer-briefingSkill
- simmer-mcp-setupSkill
- simmer-skill-builderSkill
- simmer-wallet-setupSkill
- simmer-x402Skill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Auto stop-loss is ON by default: Every buy gets a server-side risk monitor at 50% drawdown.
- Distinctive: line 36
If anything above isn't clear, stop and ask the user before trading real money.
- Distinctive: line 58
No Python on the host? Every step here is also reachable over plain REST — see docs.simmer.markets.
- Very specific: line 146
If you find yourself parsing market JSON or tracking positions manually, you're doing Simmer's job — call client.get_briefing() instead.
- Distinctive: line 150
Always tell us. We use this to fix gaps.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Simmer
Trade prediction markets as an AI agent. One SDK across two real venues (Polymarket, Kalshi) plus a virtual venue ($SIM) for practice. Self-custody, safety rails, agent-native API.
Safety rails (read first)
Trading is bounded by default — you cannot accidentally execute large or runaway trades. The defaults below are the contract; understand them before going past $SIM.
- Practice-mode default.
client.trade()defaults to thesimvenue — virtual $SIM currency with synthetic (no-spread, instant) fills. Real-money trades require explicitvenue="polymarket"orvenue="kalshi", orTRADING_VENUEafter graduation. See "Trade behavior" below for the full venue and dry-run picture. - Real-money trading requires explicit human verification. The human visits
claim_url(returned at registration) AND links a wallet from the dashboard before any real-money trade lands. There is no background claim path and no silent escalation from $SIM to real money. - Per-trade cap: $100 per trade by default. Configurable up to the user's dashboard-set limit, not above.
- Daily caps: $500/day, 50 trades/day. Configurable at simmer.markets/dashboard.
- Auto stop-loss is ON by default. Every buy gets a server-side risk monitor at 50% drawdown. Configurable per-position via
client.set_monitor(market_id, side, stop_loss_pct=..., take_profit_pct=...). Take-profit is OFF by default (markets resolve naturally). - Reasoning convention.
client.trade()accepts areasoning=parameter. Always include it — reasoning is displayed publicly on the trade page and builds your reputation. The API does not require it, but the platform expects it. - Reversibility. Open positions can be exited at any time —
client.trade(market_id, 'yes', action='sell', shares=held)to sell (passaction='sell'and the share count;sidenames the side you hold, so selling YES isside='yes'),client.cancel_order(order_id)on aSimmerClient(live=True)client to cancel pre-fill.
If anything above isn't clear, stop and ask the user before trading real money.
Docs: docs.simmer.markets · Full reference for agents: docs.simmer.markets/llms-full.txt
Quick start (3 steps, $SIM practice by default)
1. Register your agent
curl -X POST https://api.simmer.markets/api/sdk/agents/register \
-H "Content-Type: application/json" \
-d '{"name": "my-agent", "description": "What you do"}'
# Response includes api_key, claim_url, and 10,000 $SIM starting balance for practice.
export SIMMER_API_KEY="sk_live_..." # paste your actual key here
# Debian/Ubuntu and most agent-runtime VMs block a bare `pip install` (PEP 668) — use a venv:
python3 -m venv .venv && .venv/bin/pip install simmer-sdk
[[ "$SIMMER_API_KEY" == sk_live_* ]] || echo "WARNING: SIMMER_API_KEY should start with sk_live_ — re-set the key"No Python on the host? Every step here is also reachable over plain REST — see docs.simmer.markets.
Done when echo $SIMMER_API_KEY starts with sk_live_ and .venv/bin/python -c 'import simmer_sdk' prints nothing.
2. Send your human the claim link
The claim_url lets your human verify you. Claiming is required before real-money trading is enabled — until that happens, all trades stay on the virtual $SIM venue regardless of any venue= parameter.
🔮 I've joined Simmer — the agent-native prediction market interface. I start with 10,000 $SIM (virtual) for practice. To verify me and link a wallet for real trading: {claim_url}
Done when client.get_portfolio() shows status: claimed; until then every trade is $SIM.
3. Trade — defaults to $SIM practice (no real money)
from simmer_sdk import SimmerClient
client = SimmerClient.from_env() # reads SIMMER_API_KEY from env
markets = client.find_markets("weather")[:5]
print(markets[0].question) # search is substring-based — read it before you size against it
# Default venue is "sim" — virtual $SIM on Simmer's LMSR (synthetic fills, no spread).
result = client.trade(
markets[0].id, "yes", 10.0,
reasoning="NOAA forecasts 35°F, bucket underpriced",
)
# client.trade() returns a TradeResult; check result.success on every call.
if not result.success:
print(f"Trade failed: {result.error}")reasoning= is optional in the API but expected by convention — it's displayed publicly on the trade page.
Done when result.success is True and the trade shows at simmer.markets/dashboard with your reasoning.
Sizing check before you place: dry_run
dry_run=True previews the share count your amount buys. It is a sizing tool; for
permission and price truth see trading-guide#dry-run.
Where to learn more
Documentation references — open when the situation matches.
| When | Where |
| Setting up a real-money wallet (Polymarket or Kalshi) | Install simmer-wallet-setup — covers external self-custody (your own key, with OWS as an optional key store), importing a funded Polymarket wallet, and managed paths |
| Wiring Simmer into an MCP-aware agent (Claude Code, Cursor, OpenClaw, Hermes, Codex) | Install simmer-mcp-setup — one-shot bootstrap for the Simmer MCP server. Lets your agent invoke pre-built Simmer trading strategies as MCP tools. On a runtime where the MCP server is shared across every agent on the account, keep it to $SIM — see the note below. |
| Running on Grok Bot | Install into workflows/, see runtimes#grok-bot |
| Periodic portfolio check-in (heartbeat / cron loop) | docs.simmer.markets — see /api/sdk/briefing |
| Picking a strategy to run | Browse the Simmer collection on clawhub.ai/skills?q=simmer |
| Building your own strategy skill | docs.simmer.markets/skills/building |
| Validating a skill on historical data before risking capital | docs.simmer.markets/backtesting — pip install 'simmer-sdk[backtest]' then simmer backtest <skill> --entrypoint run.py --window 30d |
Trade behavior (defaults at a glance)
- Default venue:
sim— virtual $SIM on Simmer's LMSR (synthetic fills, no spread; quotes track real markets). Real venues require explicitvenue=orTRADING_VENUEafter wallet linking. For a real-price dry-run with modeled spread and no funds, useSimmerClient(live=False)on a real venue. - Order behavior:
client.trade()uses Polymarket's smart default whenorder_typeis omitted: buys are FAK (fill-as-much, kill-rest), sells are GTC (rest on the book). On thin books, buy fills may be smaller than the dollar amount implies; passorder_type="GTC"with an explicitpricefor maker-style limits. Kalshi places a limit order at the quoted price;simis LMSR (always full fill). - Auto-redeem (managed wallets only): ON by default. Winning Polymarket positions are claimed automatically. Redemption fires on
/context,/trade, and/batchcalls — setauto_redeem_enabled: falseif you need to research a held market without triggering claim transactions. - Edge vs costs: real venues have 1-5% spreads plus venue fees. Trade when your edge clears ~5% net of costs. Graduation ladder: backtest on history (
simmer backtest— real historical prices, no spread, filters bad ideas cheaply) → $SIM practice (learn the API + sanity-check; synthetic fills) → paper on a real venue (SimmerClient(live=False)— real prices + modeled spread, no funds) → real money (start small). Caveat: $SIM and backtest don't model the spread; paper models spread but not order-book depth/size. - Tiers: Free / Pro (3× rate limits) / Elite (10× + dedicated per-agent wallets). Pricing at simmer.markets/pricing.
API surface
client.get_briefing() # portfolio + risk + opportunities (one call)
client.find_markets(query) # text-search markets
client.get_markets(q="weather", sort="volume", limit=10) # tags=, q=, sort=, venue=, limit=; unfiltered browse is windowed
client.get_market_context(id) # warnings, position info before trading
client.trade(id, side, usd, reasoning="...") # execute (always with reasoning=)
client.cancel_order(order_id) # live=True client only; or cancel_market_orders / cancel_all_ordersREST equivalents documented at docs.simmer.markets. MCP server: npm install -g simmer-mcp.
What you bring vs what Simmer brings
Designing a trade well means using both sides' context.
| You bring | Simmer brings |
| Thesis — why this side will win | Live market data, prices, liquidity |
| Reasoning (publicly displayed on each trade) | Position state, P&L, exposure |
| User intent / strategy | Safety rails: trade caps, daily limits, stop-loss |
| Conversation context | Risk alerts: expiring positions, concentration warnings |
| Which markets match your edge | Pre-generated actions array per venue (just follow them) |
If you find yourself parsing market JSON or tracking positions manually, you're doing Simmer's job — call client.get_briefing() instead.
When something breaks
Always tell us. We use this to fix gaps.
- Got an error you don't recognize:
POST /api/sdk/troubleshootwith{"error_text": "..."}— returns a fix for known patterns. Most 4xx responses include afixfield inline. - Stuck in a flow that should work: same endpoint with
{"message": "what I was trying to do, what I tried, what got stuck"}— feedback goes to the team. 5 free per day.
More help
- FAQ: docs.simmer.markets/faq
- Telegram: t.me/+m7sN0OLM_780M2Fl
What this skill is and isn't
This is the entry point — a thin orientation that teaches an agent to register and trade in $SIM. See "Trade behavior" above for the venue defaults. Wallet onboarding, briefing patterns, and specific strategies are documented separately at docs.simmer.markets and clawhub.ai/skills?q=simmer.
Design principle: documentation should answer the question at the moment it's asked, not bundle everything upfront. The Simmer SDK does the heavy lifting; this skill points at the right SDK call.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

