BC USD1 WLF Transfer Skill
Allows an agent to securely transfer USD1 (USDC on Wormhole) from one wallet to another using Wormhole Liquidity Facility (WLF).
Allows an agent to securely transfer USD1 (USDC on Wormhole) from one wallet to another using Wormhole Liquidity Facility (WLF).
As a process C 62/100 · Has gaps — weak spots: when it triggers, failures and branches, consistency
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
- 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 · 6
✓ No critical or high findings
Medium and low: 6
-
medium Risky intent
intent-wallet-secretsSKILL.md:22Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- privateKey: string (secure, required) - sender wallet private key
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:53High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…nFR+MDik6udKfj2+9ZsmTLV0/t73v…I7L+1+yjEbQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:196High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…ovq+VyC9…p8L/81Rk…DIw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:212High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…3SV+TCHq…BR5+ti7Hw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:286High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-Gih++NYHEiP+oyD4…FSg+33Hp…p5Z+W3A==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:319High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…ov7+qofC…XjQ==",
detector
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 62/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (USD1 WLF Transfer Skill) differs from the folder (usd1)
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 14 steps
- 100Execution cost. Instruction body is 248 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 128: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 14 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.