BB laso-finance
Order prepaid cards, gift cards, and send money to USD/EUR/GBP debit cards or US bank accounts using USDC on Base or Solana via the x402 protocol. Use when a user or agent needs to spend cryptocurrency, pay for an online checkout, buy a prepaid card, order a gift card, send money to a debit card or bank account, check a card or account balance, pay a paywalled x402 endpoint, or resolve a 402 Payment Required response.
Order prepaid cards, gift cards, and send money to USD/EUR/GBP debit cards or US bank accounts using USDC on Base or Solana via the x402 protocol.
As a process B 67/100 · Nearly there — weak spots: result and completion, when it triggers, execution cost
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:291High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"wallet_address": "3MZV…fYX",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:315High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"wallet_address": "3MZV…fYX",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:661High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"payer": "9sZE…WXR",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:1736High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Solana payment recipient: `3MZV…fYX`
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 22202 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 67/100
- 10Execution cost. Instruction body is 22202 tokens: crowds the task out of the window
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (bash, read, web) that frontmatter does not declare
- 85Steps. 138 steps, 2 vague phrases
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 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 19 top-level sections: this looks like several domains in one skill
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (4 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 421: enough signal without eating the budget
- +4Structure: 58 headings
- +3Step-by-step instructions: 138 items
- +4Has examples (79 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.