BF gasless-crosschain-executor
local-key swap planning and execution skill. Cross-chain (1inch Fusion+, gasless), same-chain gasless (1inch Fusion), and same-chain paid (1inch Aggregation Router v6) paths are bundled. Use when a user asks an agent to quote, validate, sign locally, broadcast, monitor, or recover EVM swaps while keeping private keys on the user's machine.
As a process F 70/100 · Will not run — References files that are not bundled: examples/node_modules/, examples/generate_wallet.py, examples/preflight.py
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
- The text references files that are not there: add them or drop the references.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Risky intent
intent-wallet-secretsSKILL.md:24Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- Never ask the user to paste a private key, seed phrase, mnemonic, raw keystore password, wallet backup, or one-time code into chat.
-
low Secrets in code
secret-high-entropy-tokenreferences/provider-adapters.md:76High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)Same-chain, NOT gasless, immediate-execution. Returns a regular EVM transaction targeting Aggregation Router v6 (`0x11…A65` on most chains); the user signs and submit
detector
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: examples/node_modules/ - warning
missing-refreference to a missing file: examples/generate_wallet.py - warning
missing-refreference to a missing file: examples/preflight.py - warning
missing-refreference to a missing file: examples/build_order_fusion_plus.mjs - warning
missing-refreference to a missing file: examples/build_order_fusion.mjs - warning
missing-refreference to a missing file: examples/swap_aggregator.mjs - warning
missing-refreference to a missing file: examples/local_signer.py
Process rating: all ten parameters 70/100
- 0Tools and files. 7 referenced file(s) missing: examples/node_modules/, examples/generate_wallet.py, examples/preflight.py
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 107 steps
- 100Failures and branches. 13 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3974 tokens
- 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 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (7 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)
- +1No license
- +2Single-language instructions
- +3Description length 341: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 107 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.