DC polymarket-oracle
Multi-strategy arbitrage and trading bot for Polymarket prediction markets. Scans ALL markets (crypto, politics, sports, economics, entertainment) for parity arbitrage, logical arbitrage, tail-end trading, market making, and latency opportunities.
Multi-strategy arbitrage and trading bot for Polymarket prediction markets.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.
Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 18
✓ No critical or high findings
Medium and low: 18
-
medium Risky intent
intent-wallet-secretsCONFIGURATION.md:90Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target**IMPORTANT:** Your wallet private key is needed **ONLY ONCE** to create Polymarket API credentials.
-
medium Dangerous commands
cmd-privilegeCONFIGURATION.md:141Privilege escalation / world-writable permissionssudo chmod 600 /etc/polymarket-oracle/credentials.env
-
medium Dangerous commands
cmd-privilegeCONFIGURATION.md:142Privilege escalation / world-writable permissionssudo chown root:root /etc/polymarket-oracle/credentials.env
-
medium Exfiltration
exfil-webhook-urlCONFIGURATION.md:237Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)url = f"https://api.telegram.org/bot{token}/sendMessage"quoted -
medium Dangerous commands
cmd-shell-rcCONFIGURATION.md:276Writes to a shell startup filecat >> ~/.bashrc << 'EOF'
-
medium Exfiltration
exfil-webhook-urlpolymarket_oracle.py:485Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)self.api_url = f"https://api.telegram.org/bot{bot_token}/sendMessage" if bot_token else Nonequoted -
medium Exfiltration
exfil-webhook-urlSKILL.md:25Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)- "https://api.telegram.org/bot*"
quoted -
medium Risky intent
intent-wallet-secretsSKILL.md:377Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- ✅ Polygon wallet private key
-
medium Risky intent
intent-wallet-secretsSYSTEMD_SETUP.md:98Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- `WALLET_PRIVATE_KEY=...` → Your Polygon wallet private key
-
medium Dangerous commands
cmd-privilegeSYSTEMD_SETUP.md:358Privilege escalation / world-writable permissionssudo chmod 600 /etc/polymarket-oracle/credentials.env
-
medium Dangerous commands
cmd-privilegeSYSTEMD_SETUP.md:359Privilege escalation / world-writable permissionssudo chown root:root /etc/polymarket-oracle/credentials.env
-
low Risky intent
intent-wallet-secretsCONFIGURATION.md:88Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (detector / deny-list definition)## ⚠️ CRITICAL SECURITY - WALLET PRIVATE KEY
detector -
low Exfiltration
exfil-webhook-urlCONFIGURATION.md:217Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)https://api.telegram.org/botYOUR_TOKEN/getUpdates
placeholder -
low Dangerous commands
cmd-background-processCONFIGURATION.md:495Starts a background / autostarted processnohup python3 polymarket_oracle.py > oracle.log 2>&1 &
-
low Dangerous commands
cmd-background-processCONFIGURATION.md:622Starts a background / autostarted processsudo systemctl enable polymarket-oracle
-
low Dangerous commands
cmd-background-processSYSTEMD_SETUP.md:120Starts a background / autostarted processsudo systemctl enable polymarket-oracle
-
low Dangerous commands
cmd-background-processSYSTEMD_SETUP.md:223Starts a background / autostarted processsudo systemctl enable polymarket-oracle
-
low Dangerous commands
cmd-background-processSYSTEMD_SETUP.md:517Starts a background / autostarted processsudo systemctl enable polymarket-oracle
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 53/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 54 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2014 tokens
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -238 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 247: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 54 items
- +4Has examples (17 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.