BC nexusweb3
Complete financial infrastructure for AI agents on Base mainnet — wallet, identity, payments, yield, insurance, reputation, marketplace, bridge, governance, and launchpad.
As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureInfrastructureAI and agentsCommercetype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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
-
low Risky intent
intent-wallet-secretsSKILL.md:15Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)Instead of providing a raw `ETH_PRIVATE_KEY`, the recommended setup is to use AgentVault's operator system. Deploy a vault, fund it with minimal USDC, and add your agent as an operator with a spending
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:31High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)- **USDC:** `0x83…913` (6 decimals)
detector -
low Secrets in code
secret-high-entropy-tokenSKILL.md:52High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)**Contract:** `0x1F…f5A`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:58High-entropy token-like string (may be an id, hash or a credential)IERC20(0x83…913), // USDC
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:84High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)**Contract:** `0x6F…C60`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:117High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)**Contract:** `0xD3…a6E`
quoted
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 11 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 15 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3146 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 171: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (28 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: suspicious
This appears to be a real Base mainnet finance skill, but it gives an agent live wallet authority without enough scoping, confirmation guidance, or loss-risk disclosure.
LLM: suspicious (high) · VirusTotal: · 29 May 2026