polymarket-trading
Skill13 starsChanged 9 months agoMITView on GitHub
Trade prediction markets on Polymarket via Quantish MCP
3 other projects use a version of this.
Adopted by
Most recently taken up by
- machina-sports/sports-skillstheir own version, first seen Nov 5, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Oct 27, 2026
- BlockRunAI/blockrun-mcptheir own version, first seen Oct 20, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- BlockRunAI/ClawRouter★ 6.7ksame name
- BlockRunAI/blockrun-mcp★ 389same name
- machina-sports/sports-skills★ 266same 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 repository3 other files it gives its agents.
- copyclawSkill
- kalshi-tradingSkill
- quantish-mcp-setupSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
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 15
Run /quantish-mcp-setup first to connect to the MCP servers.
- Distinctive: line 202
If you hold both YES and NO tokens, merge them back to USDC:
- Very specific: line 230
Verify fills: - Use get_positions not just order status
- Distinctive: line 231
Check balances: - Ensure sufficient USDC before trading
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Polymarket Trading Skill
Complete guide to trading on Polymarket through the Quantish MCP server.
Prerequisites
Run /quantish-mcp-setup first to connect to the MCP servers.
Trading Workflow
1. Check Wallet Status
mcp__quantish__get_wallet_statusResponse fields:
safeAddress: Your trading wallet (Polygon)safeDeployed: Must betrueapprovals: All should betrue(usdc, ctf, negRisk)isReady: Must betrueto trade
2. Check Balances
mcp__quantish__get_balancesResponse:
{
"safe": {
"address": "0x...",
"usdc": "10.0", // Available to trade
"nativeUsdc": "0.0" // Circle USDC (different token)
}
}3. Find Markets via Discovery
Use the Discovery MCP to search for markets across all platforms.
mcp__quantish-discovery__search_markets
query: "government shutdown"
platform: "polymarket"
limit: 5Response includes:
{
"markets": [{
"platform": "polymarket",
"conditionId": "0xd5a91c9ee50ba80385283714f2a66b1e16d544a682af2af06a8f57fcf1d0233d",
"title": "Will the government shutdown last 5 days or more?",
"prices": [
{"outcome": "Yes", "price": 0.45, "tokenId": "8008742846..."},
{"outcome": "No", "price": 0.55, "tokenId": "1122334455..."}
]
}]
}Key fields:
conditionId: Market identifier (0x...) - needed for place_ordertokenId: Outcome token ID (long number) - needed for place_orderprices[].outcome: "Yes" or "No"prices[].price: Current price (0.01-0.99)
4. Check Orderbook (IMPORTANT - DO THIS FIRST)
mcp__quantish__get_orderbook
tokenId: "8008742846391096366381429238657491392199916771102623264605530168655505543184"Response shows:
bids: Buy orders (sorted low to high)asks: Sell orders (sorted high to low)- Best bid = highest bid price
- Best ask = lowest ask price
ALWAYS check orderbook before placing orders to get best price.
5. Get Current Price
mcp__quantish__get_price
tokenId: "8008742846391096366381429238657491392199916771102623264605530168655505543184"Returns midpointPrice between best bid/ask.
6. Place Order
mcp__quantish__place_order
conditionId: "0xd5a91c9ee50ba80385283714f2a66b1e16d544a682af2af06a8f57fcf1d0233d"
tokenId: "8008742846391096366381429238657491392199916771102623264605530168655505543184"
side: "BUY"
price: 0.45
size: 4Parameters:
| Param | Type | Description |
| conditionId | string | Market ID (from search) |
| tokenId | string | YES or NO token ID |
| side | "BUY" or "SELL" | Direction |
| price | number | Limit price 0.01-0.99 |
| size | number | Number of shares |
| orderType | string | "GTC" (default), "FOK", "FAK", "GTD" |
Order Types:
GTC: Good Till Cancelled - rests on book, crosses spread if price allowsFOK: Fill Or Kill - must fill entirely or failsFAK: Fill And Kill - fills what it can, cancels restGTD: Good Till Date - requiresexpirationtimestamp
Cost calculation: price × size = USDC cost
Response:
{
"success": true,
"orderId": "f3a665c9-...",
"status": "LIVE", // or "FILLED"
"message": "Order is live: BUY 4 shares at $0.45"
}7. Check Positions
mcp__quantish__get_positionsResponse:
{
"positions": [{
"outcome": "Yes",
"size": 4,
"avgPrice": 0.45,
"currentPrice": 0.43,
"currentValue": 1.72,
"pnl": -0.08,
"marketTitle": "Will the government shutdown last 5 days or more?"
}]
}8. Check Orders
mcp__quantish__get_orders
status: "LIVE" // optional: PENDING, LIVE, FILLED, CANCELLED, FAILED9. Cancel Order
mcp__quantish__cancel_order
orderId: "f3a665c9-..."10. Sync Order Status
mcp__quantish__sync_order_status
orderId: "f3a665c9-..."Note: May show sizeMatched: 0 due to API lag even if filled. Use get_positions to confirm.
11. Claim Winnings (After Market Resolves)
mcp__quantish__get_claimable_winningsmcp__quantish__claim_winnings
positionId: "..." // optional, claims all if omittedAdvanced Operations
Merge Tokens (Exit Position at $1)
If you hold both YES and NO tokens, merge them back to USDC:
mcp__quantish__merge_tokens
conditionId: "0x..."Transfer USDC
mcp__quantish__transfer_usdc
toAddress: "0x..."
amount: 5.0Get Deposit Addresses
mcp__quantish__get_deposit_addressesSupports deposits from Ethereum, Polygon, Arbitrum, Optimism, Base, Solana, and Bitcoin.
Best Practices
- Always check orderbook first - Know the spread before placing orders
- Use limit orders - GTC orders get price improvement
- Start small - $1-2 trades until comfortable
- Verify fills - Use
get_positionsnot just order status - Check balances - Ensure sufficient USDC before trading
Error Handling
| Error | Cause | Fix |
| "not enough balance" | Insufficient USDC | Deposit more or reduce size |
| "order failed" | Price moved | Check orderbook, adjust price |
| "invalid token" | Wrong tokenId | Get fresh market data |
Example: Complete Trade Flow
1. get_wallet_status → Confirm ready
2. get_balances → Check USDC
3. search_markets → Find market
4. get_orderbook → See bid/ask spread
5. place_order → Execute trade
6. get_positions → Verify fillDoes 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.

