BC polymarket-fast-loop
Trade Polymarket BTC 5-minute and 15-minute fast markets using CEX price momentum signals via Simmer API. Default signal is Binance BTC/USDT klines. Use when user wants to trade sprint/fast markets, automate short-term crypto trading, or use CEX momentum as a Polymarket signal.
Trade Polymarket BTC 5-minute and 15-minute fast markets using CEX price momentum signals via Simmer API.
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
The same skill appears in 4 more places: ClawHub, ClawHub, ClawHub, ClawHub
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.
How to improve
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Risky intent
intent-wallet-secretsSKILL.md:56Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target3. **Ask for wallet private key** (required for live trading)
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 62/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 53 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2768 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
- +1No license
- +2Single-language instructions
- +3Description length 278: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 53 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.
In the sandbox Скрипты не запустились
The skill's scripts were run in a throwaway machine: no network, fake keys in the home directory, a tracer watching. We wrote down what they did. Reaching for the network or for secrets caps the technical grade at C; a quiet run adds no points.
Запущено 1 скрипт; каждому дали двадцать секунд, поддельный домашний каталог с ключами и сеть, в которой ничего нет.
Ни один не дошёл до работы — им не хватило зависимостей, аргументов или файлов. Это не отзыв о поведении: наблюдать было не за чем.
fastloop_trader.py | не запустился: ModuleNotFoundError: No module named 'simmer_sdk' |
21 Sept 2026