BB walletchan
Drive the WalletChan browser extension as a human-in-the-loop co-pilot for web3 dapps. The agent navigates the dapp UI and surfaces each transaction or signature — decoded and human-readable — inside the extension for the user to review. A scoped, user-controlled "Agent Password" unlocks ONLY the review-and-confirm UI; it cannot export private keys, reveal the seed phrase, change security settings, or disable auto-lock. Use when the user asks to connect a wallet, swap tokens, supply/deposit to DeFi, sign typed data, or check on-chain balances through a dapp. Requires Chrome with remote debugging and the WalletChan extension installed.
As a process B 74/100 · Nearly there — weak spots: result and completion, 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 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
- 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
✓ No critical or high findings
Medium and low: 5
-
medium Risky intent
intent-wallet-secretsskill-card.md:23Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer targetMitigation: Share only the Agent Password, never the master password or seed phrase, and use it only in WalletChan's unlock field; rotate or revoke it in WalletChan settings when needed. <br>
-
medium Risky intent
intent-wallet-secretsSKILL.md:3Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer targetdescription: Drive the WalletChan browser extension as a human-in-the-loop co-pilot for web3 dapps. The agent navigates the dapp UI and surfaces each transaction or signature — decoded and human-reada
-
medium Risky intent
intent-wallet-secretsSKILL.md:41Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target| **Master Password** | Vault key. Decrypts private keys and seed phrases. | **User only.** Never shared with any agent, ever. | Private key export, seed phrase reveal, security settings. |
-
medium Risky intent
intent-wallet-secretsSKILL.md:47Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- Revealing a seed phrase
-
medium Risky intent
intent-wallet-secretsSKILL.md:94Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- Attempt to export, reveal, copy, or transmit a private key or seed phrase.
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "extension_listing"
Process rating: all ten parameters 74/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 1 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 60 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 9 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3303 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 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
- +1No license
- +2Single-language instructions
- +3Description length 642: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 60 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.