BC usdc-dance-evvm-payment
Pay with USDC.d via x402 protocol on Story Aeneid EVVM using Privy server wallets. Uses BridgeUSDC (custom bridge) until LayerZero supports Story Aeneid.
As a process C 62/100 · Has gaps — weak spots: result and completion, when it triggers, consistency
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:54High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)adapterAddress: '0x00…314', // Bridge EVVM adapter
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:55High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)usdcDanceAddress: '0x5f…C40', // BridgeUSDC
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:56High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)evvmCoreAddress: '0xa6…A3b',
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:73High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)adapterAddress: '0x00…314', // Bridge EVVM adapter
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:74High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)usdcDanceAddress: '0x5f…C40', // BridgeUSDC
quoted
Files scanned: 1. 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 "requires"
Process rating: all ten parameters 62/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (usdc-dance-evvm-payment) differs from the folder (openclaw-skill-usdc-dance-evvm)
- 55Failures and branches. 1 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 45 steps
- 100Execution cost. Instruction body is 1455 tokens
- 100Running it twice. Mutating operations check current state
- 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 153: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 45 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: suspicious
This is a purpose-aligned crypto payment skill, but it gives agents autonomous wallet/payment authority without strong built-in limits or reviewed implementation files.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026