BC okx-dex-bridge
Use this skill to bridge tokens, cross-chain swap/transfer, move assets between chains, get cross-chain quotes, compare bridge fees, find the cheapest/fastest route, build bridge calldata, check bridge status, track a cross-chain transaction, list supported chains or bridge protocols, or when the user mentions bridging ETH/USDC/tokens from one chain (Ethereum, BSC, Polygon, Arbitrum, Base, Optimism, etc.) to another. Routes through multiple bridge protocols (Stargate, Across, Relay, Gas.zip) for optimal execution. Supports fee comparison, destination address specification, approval management, and full lifecycle status tracking until fund arrival.
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, execution cost
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
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
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 5
-
high Concealment
en-hide-from-userSKILL.md:584Instruction to hide actions from the user- **Non-atomic**: source chain broadcast does not guarantee destination arrival. Funds may be in transit for seconds to minutes. Do not tell the user "transaction complete" until status returns SUCCES
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenreferences/cli-reference.md:212High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"approveAddress": "0xe3…f2A",
quoted -
low Secrets in code
secret-high-entropy-tokenreferences/cli-reference.md:288High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"to": "0xe3…f2A",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:77High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Tron | `T9yD…Wwb` | No |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:78High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Ton | `EQAA…M9c` | No |
table
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 10052 tokens (recommended < 5000); move details to references/
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
- 40Execution cost. Instruction body is 10052 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 85Steps. 86 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 23 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (16 tags): a typed call is more reliable
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
- +2Single-language instructions
- +3Description length 655: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 86 items
- +4Has examples (14 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.