BC evm-bnb-band-trader
Execute BNB Chain EVM swing trades after importing a private key: buy when trigger price exceeds market condition, then place 5% take-profit and 3% stop-loss management. Use when user asks to automate BNB band/swing trading with strict TP/SL and wallet-key based execution.
As a process C 55/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.
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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Risky intent
intent-wallet-secretsskill-card.md:19Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer targetRisk: The skill asks users to provide a raw wallet private key, which can expose funds if used with a main wallet or unsafe environment. <br>
-
medium Risky intent
intent-wallet-secretsskill-card.md:20Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer targetMitigation: Run dry-run mode first and use only a dedicated low-balance wallet for experimentation; never use a main wallet private key. <br>
-
medium Risky intent
intent-wallet-secretsSKILL.md:14Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- `EVM_PRIVATE_KEY` (wallet private key, never hardcode)
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Execute BNB Chain EVM swing trades after importing a private key: … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 55/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
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 19 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 312 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 273: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (2 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.