BB openpayment
Create x402 USDC payment links using the OpenPayment CLI.
As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:91High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Base Mainnet USDC: `0x83…913`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:92High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Base Sepolia USDC: `0x03…F7e`
quoted
Files scanned: 2. 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")
Process rating: all ten parameters 67/100
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 4 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1763 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 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)
- +3Description length 57: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 22 headings
- +3Step-by-step instructions: 20 items
- +3Output format is stated explicitly
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: clean
This skill coherently helps create OpenPayment-hosted USDC payment links, with some financial-data sharing users should understand before use.
LLM: benign (high) · VirusTotal: · 11 Jun 2026