BB nova-wallet
Safely operate the nova CLI wallet for authentication, balance checks, sending funds, withdrawals, and key management across mainnet and testnet. Enforces deterministic JSON/TOON parsing, exit code validation, financial confirmations, network verification, and strict secret-handling rules. Use when performing nova wallet automation, stablecoin transfers, claim links, exports, or any blockchain transaction via the nova CLI.
As a process B 69/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, 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
- 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-secretsreferences/REFERENCE.md:664Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- Seed phrase
-
medium Risky intent
intent-wallet-secretsreferences/REFERENCE.md:670Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- Display seed phrase in shared environments
-
low Secrets in code
secret-high-entropy-tokenreferences/REFERENCE.md:373High-entropy token-like string (may be an id, hash or a credential)nova withdraw 10 USDC 0x76…F28 base
-
low Secrets in code
secret-high-entropy-tokenreferences/REFERENCE.md:379High-entropy token-like string (may be an id, hash or a credential)nova -j withdraw --dry-run 10 USDC 0x76…F28 base
-
low Secrets in code
secret-high-entropy-tokenreferences/REFERENCE.md:385High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition){"result":{"amount":"10","blockchain":"base","dryRun":true,"stablecoin":"USDC","to":"0x76…F28"},"status":"ok"}detector
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (nova-wallet) differs from the folder (nova)
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 95 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Execution cost. Instruction body is 1400 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
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)
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 426: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 95 items
- +3Output format is stated explicitly
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.