BC aidex
Swap tokens on Ethereum via the AIDEX aggregator. Search tokens, check exchange rates, view balances, and execute swaps. Client-side transaction signing keeps your private key on your machine.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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 skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.
Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".
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 · 12
✓ No critical or high findings
Medium and low: 12
-
medium Concealment
en-hide-from-userSKILL.md:305Instruction to hide actions from the user (quoted — discussed, not commanded)13. **Do not assume the private key is missing — check by running the script.** When the user asks for their balance, wallet address, or any operation that may require a private key, do not refuse pre
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/scripts.md:11High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **By address**: `0xA0…B48`
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/scripts.md:48High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded){"success": true, "address": "0x74…D18"}quoted -
low Secrets in code
secret-high-entropy-tokenreferences/scripts.md:77High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": "0xA0…B48",
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/scripts.md:149High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded){"address": "0xA0…B48", "symbol": "USDC", "balance": "3250.00", "allowance": "1000.0"}quoted -
low Secrets in code
secret-high-entropy-tokenscripts/data/tokens.json:10High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": "0xC0…Cc2",
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/data/tokens.json:17High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": "0xA0…B48",
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/data/tokens.json:24High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": "0x6B…d0F",
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/data/tokens.json:31High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": "0xdA…ec7",
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/data/tokens.json:38High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": "0x22…599",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:158High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)- By address: `--token-in 0xA0…B48`
detector -
low Secrets in code
secret-high-entropy-tokenSKILL.md:312High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- WETH address: `0xC0…Cc2`
quoted
Files scanned: 16. 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 "homepage" - note
frontmatter-keyunknown frontmatter key "emoji"
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
- 30Running it twice. 4 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70Execution cost. Instruction body is 4850 tokens
- 85Steps. 48 steps, 1 vague phrases
- 100Failures and branches. 20 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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
- -42 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 192: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 48 items
- +4Has examples (16 code blocks)
- +3All 6 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.