Best for
- Learn how skilled traders operate — What metrics separate winners from losers?
- Understand trading psychology — Who chases prices? Who has discipline?
- Detect bots and anomalies — Identify suspicious patterns for research
SpartanLabsXyz/simmer-sdk/skills/polymarket-wallet-xray/SKILL.md
X-ray any Polymarket wallet — skill level, entry quality, bot detection, and edge analysis. Queries Polymarket's public APIs, no authentication needed. Inspired by @thejayden's "Autopsy of a Polymarket Whale" analysis.
Decision brief
Analyze any Polymarket wallet's trading patterns, skill level, and edge detection.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/SpartanLabsXyz/simmer-sdk --skill "skills/polymarket-wallet-xray"Inspect the Agent Skill "polymarket-wallet-xray" from https://github.com/SpartanLabsXyz/simmer-sdk/blob/b3154d43d417fe717b308bc2ccf9814181d6fc89/skills/polymarket-wallet-xray/SKILL.md at commit b3154d43d417fe717b308bc2ccf9814181d6fc89. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
When user asks to install or configure this skill:
python import subprocess import json
Review the “- Can I replicate their decision-making process?” section in the pinned source before continuing.
Past performance does not guarantee future results. A wallet's historical metrics tell you about: - ✅ How they traded in the past - ✅ Their historical win rate and entry quality - ❌ NOT whether their strategy will work going forward
Use this skill when you want to: - Learn how skilled traders operate — What metrics separate winners from losers? - Understand trading psychology — Who chases prices? Who has discipline? - Detect bots and anomalies — Identify suspicious patterns for research - Research arbitrage…
Permission review
The documentation asks the agent to run terminal commands or scripts.
python wallet_xray.py 0x1234...abcdThe documentation asks the agent to run terminal commands or scripts.
python wallet_xray.py 0x1234...abcd "Bitcoin"Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 91/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 48 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Analyze any Polymarket wallet's trading patterns, skill level, and edge detection.
No authentication needed. Queries Polymarket's public CLOB API directly.
Inspired by: The Autopsy: How to Read the Mind of a Polymarket Whale by @thejayden
🚨 Framework, not a production trading system. Read DISCLAIMER.md before connecting to a wallet with real funds.
This skill implements the forensic trading analysis framework developed by @thejayden. Read the original post to understand the philosophy behind Time Profitable, hedge checks, bot detection, and accumulation signals.
This is an analysis tool, not a trading signal. The skill returns forensic metrics for ANY Polymarket wallet — your agent uses them to UNDERSTAND traders, learn patterns, and make informed decisions. This is for education and research, not for blindly copying positions.
Past performance does not guarantee future results. A wallet's historical metrics tell you about:
Why copying is risky:
Use this skill to:
DO NOT use this skill to:
Use this skill when you want to:
NOT for:
When user asks to install or configure this skill:
Install the Simmer SDK
pip install simmer-sdk
Ask for Simmer API key
SIMMER_API_KEY# Analyze a single wallet
python wallet_xray.py 0x1234...abcd
# Analyze wallet + only look at specific market
python wallet_xray.py 0x1234...abcd "Bitcoin"
# Compare two wallets head-to-head
python wallet_xray.py 0x1111... 0x2222... --compare
# Find wallets matching criteria (top Time Profitable in market)
python wallet_xray.py "Will BTC hit $100k?" --top-wallets 5 --dry-run
# Check your account status
python scripts/status.py
APIs Used (Public, No Auth Required):
https://gamma-api.polymarket.com/markets/keyset — Market search (cursor-paginated)https://clob.polymarket.com — Trade history and orderbookThe skill returns comprehensive forensic metrics:
{
"wallet": "0x1234...abcd",
"total_trades": 156,
"total_period_hours": 42.5,
"profitability": {
"time_profitable_pct": 75.3,
"win_rate_pct": 68.2,
"avg_profit_per_win": 0.035,
"avg_loss_per_loss": -0.018,
"realized_pnl_usd": 2450.00
},
"entry_quality": {
"avg_slippage_bps": 28,
"quality_rating": "B+",
"assessment": "Good entries, occasional FOMO"
},
"behavior": {
"is_bot_detected": false,
"trading_intensity": "high",
"avg_seconds_between_trades": 45,
"price_chasing": "moderate",
"accumulation_signal": "growing"
},
"edge_detection": {
"hedge_check_combined_avg": 0.98,
"has_arbitrage_edge": false,
"assessment": "No locked-in edge; relies on direction"
},
"risk_profile": {
"max_drawdown_pct": 12.5,
"volatility": "medium",
"max_position_concentration": 0.22
},
"recommendation": "Good trader. Skilled entries, disciplined sizing. Good metrics for learning from. Not advice to copytrade."
}
Wallet was profitable (not underwater) for 75% of their trading period. This wallet endured only 25% painful drawdowns — that's discipline.
They buy near the best available price. 28 basis points is normal for active traders. No evidence of FOMO market orders.
Average 45 seconds between trades. This is human. A bot would be <1 second.
If they bought YES at $0.70 and NO at $0.30, combined = $1.00. This wallet spent exactly what they should to be neutral.
If combined < $1.00, they may have entered with a structural edge (lower combined cost than $1 payout). Actual profit depends on execution, fees, and spread.
import subprocess
import json
# Analyze a wallet known for skilled trading
result = subprocess.run(
["python", "wallet_xray.py", "0x123...abc", "--json"],
capture_output=True,
text=True
)
data = json.loads(result.stdout)
# LEARN from their profile, don't copy blindly
time_prof = data["profitability"]["time_profitable_pct"]
entry_qual = data["entry_quality"]["quality_rating"]
print(f"📊 What this trader does well:")
print(f" • Time Profitable: {time_prof}% (disciplined)")
print(f" • Entry Quality: {entry_qual} (patient buyer)")
print(f" • Behavior: {data['behavior']['accumulation_signal']} (not FOMO)")
# THEN: Ask yourself
# - Why are they profitable? (skill or luck?)
# - Can I replicate their decision-making process?
# - Do I have their capital size, timing, or information?
# Analyze multiple wallets to understand patterns
wallets = ["0x111...", "0x222...", "0x333..."]
print("Comparing trader profiles:")
for wallet in wallets:
result = subprocess.run(
["python", "wallet_xray.py", wallet, "--json"],
capture_output=True,
text=True
)
data = json.loads(result.stdout)
is_bot = "🤖 BOT" if data["behavior"]["is_bot_detected"] else "👤 HUMAN"
print(f"\n{wallet}: {is_bot}")
print(f" Win Rate: {data['profitability']['win_rate_pct']}%")
print(f" Time Profitable: {data['profitability']['time_profitable_pct']}%")
# Use this data to understand what successful trading LOOKS LIKE
# Then build your own strategy based on these insights
# Analyze before you decide what to do
result = subprocess.run(
["python", "wallet_xray.py", "0x123...abc", "--json"],
capture_output=True,
text=True
)
data = json.loads(result.stdout)
# Make an INFORMED decision based on analysis + YOUR OWN JUDGMENT
if data["profitability"]["time_profitable_pct"] > 75 and \
data["entry_quality"]["quality_rating"] in ["A", "A+"]:
print(f"✅ This wallet shows skill (high Time Profitable, good entries)")
print(f"⚠️ But I will NOT copytrade blindly.")
print(f"📋 Instead, I'll:")
print(f" 1. Backtest their patterns on fresh data")
print(f" 2. Add my own market signals")
print(f" 3. Start with small position (1-2% of capital)")
print(f" 4. Monitor for next 30 days")
print(f" 5. Adjust if it stops working")
else:
print(f"❌ This wallet doesn't show strong enough metrics.")
print(f" Safer to avoid or research further before deciding.")
Analyze a single wallet (default):
python wallet_xray.py 0x1234...abcd
Analyze wallet for a specific market:
python wallet_xray.py 0x1234...abcd "Bitcoin"
Output as JSON (for scripts):
python wallet_xray.py 0x1234...abcd --json
Compare two wallets:
python wallet_xray.py 0x1111... 0x2222... --compare
Limit analysis to recent trades (faster):
python wallet_xray.py 0x1234...abcd --limit 100
"Wallet has no trades"
"Market not found"
"Analysis took too long"
--limit 100 to analyze only recent trades for faster results"API rate limited"
--limit to speed up individual analyses"Connection error"
curl https://clob.polymarket.com/trades--limit 50 to reduce loadThis skill is based on the forensic trading analysis framework from @thejayden's "Autopsy of a Polymarket Whale".
The original post shows how to:
All metrics and analysis patterns used here are derived from that work. If you find this useful, give the original post a read and follow @thejayden.
Frequently asked questions
Analyze any Polymarket wallet's trading patterns, skill level, and edge detection.
The source record exposes this install command: npx skills add https://github.com/SpartanLabsXyz/simmer-sdk --skill "skills/polymarket-wallet-xray". Inspect the command and pinned source before running it.
Static rules flagged exec-script in the source; the page lists the matching lines and excerpts.
Alternatives
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
coreyhaines31/marketingskills
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
wanshuiyin/Auto-claude-code-research-in-sleep
Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.