BF polymarket-autotrader
Polymarket AutoTrader (Premium) — BTC 5-minute prediction auto-trading bot with 92%+ win rate, 5-8% profit per trade. Enters in the last 30 seconds of each 5-min slot when BTC moves ≥$50, buys the winning side at $0.92-0.95. FOK orders: full match or auto-cancel, zero loss on unmatched. Strong signals (≥$100) trigger 2x position. Built-in billing (0.001 USDT/trade, pre-configured). Only 2 required env vars: POLY_PRIVATE_KEY, POLY_WALLET_ADDRESS (wallet address doubles as billing user ID). Billing vars pre-filled in .env.example. Optional: POLY_RPC, CLOB_HOST, CHAIN_ID, SIGNATURE_TYPE, TRADE_SIZE_USD, MAX_ASK_PRICE, MIN_BTC_MOVE, STRONG_BTC_MOVE. Connects to: Polymarket CLOB, Binance, Gamma API, skillpay.me. Writes .poly-creds.json (sensitive) and trades.json locally.
Polymarket AutoTrader (Premium) — BTC 5-minute prediction auto-trading bot with 92%+ win rate, 5-8% profit per trade.
As a process F 41/100 · Will not run — References files that are not bundled: scripts/.env.example
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 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.
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.
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Exfiltration
net-redirectable-api-keyscripts/bot.js:49Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
medium Risky intent
intent-wallet-secretsSKILL.md:91Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target| POLY_PRIVATE_KEY | Dedicated Polymarket wallet private key (Polygon) |
-
low Exfiltration
read-dotenvscripts/bot.js:66Reads a .env file (quoted — discussed, not commanded)console.error(' 👉 Copy .env.example to .env — billing credentials are pre-filled.');quoted -
low Exfiltration
read-dotenvscripts/bot.js:67Reads a .env file (quoted — discussed, not commanded)console.error(' 👉 Run: cp .env.example .env');quoted
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/.env.example
Process rating: all ten parameters 41/100
- 0Tools and files. 1 referenced file(s) missing: scripts/.env.example
- 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
- 50When it triggers. No condition that starts the skill
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1268 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- +1No license
- +2Single-language instructions
- +3Description length 777: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.