BC tradr
Onchain trade execution engine. Feed a CA + score, get full trade lifecycle — sized entry, mode-based exits, on-chain verification, and trade logging. Requires Bankr skill.
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 7
✓ No critical or high findings
Medium and low: 7
-
low Secrets in code
secret-high-entropy-tokenconfig-template.json:77High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"token": "0x0A…ec9",
quoted -
low Exfiltration
exfil-webhook-urlscripts/notify-telegram.sh:26Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl -sf -X POST "https://api.telegram.org/bot${BOT1_TOKEN}/sendMessage" \placeholder -
low Exfiltration
exfil-webhook-urlscripts/notify-telegram.sh:34Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)curl -sf -X POST "https://api.telegram.org/bot${BOT2_TOKEN}/sendMessage" \placeholder -
low Dangerous commands
cmd-background-processscripts/setup.sh:99Starts a background / autostarted processsystemctl enable "$SERVICE_NAME"
-
low Secrets in code
secret-high-entropy-tokenscripts/test-tradr.py:90High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; test fixture / example file)def _(): assert detect_chain("0x5B…44A") == "base"detectorfixture -
low Secrets in code
secret-high-entropy-tokenscripts/test-tradr.py:96High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; test fixture / example file)def _(): assert detect_chain("DezX…263") == "solana"detectorfixture -
low Secrets in code
secret-high-entropy-tokenscripts/test-tradr.py:99High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; test fixture / example file)def _(): assert detect_chain("DezX…xjn") == "solana"detectorfixture
Files scanned: 11. 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") - note
frontmatter-keyunknown frontmatter key "dependencies"
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 50 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2996 tokens
- 100Progress reporting. Reports progress
- low 14 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
- -31 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 172: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 50 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
External checks
ClawHub: suspicious
tradr is a disclosed crypto trading automation skill, but it needs Review because it can run persistent live buy/sell automation with limited consent boundaries and sensitive notification behavior.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026