AB breeze-x402-payment-api
Operates Breeze x402 payment-gated endpoints for balance checks, deposits, and withdrawals on Solana. Use when the user asks to manage Breeze positions or execute paid x402 API calls.
Operates Breeze x402 payment-gated endpoints for balance checks, deposits, and withdrawals on Solana.
As a process B 77/100 · Nearly there — weak spots: progress reporting
How to improve
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 Secrets in code
secret-high-entropy-tokenSKILL.md:64High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)-d '{"jsonrpc":"2.0","id":1,"method":"getTokenAccountsByOwner","params":["YOUR_WALLET_ADDRESS",{"mint":"EPjF…t1v"},{"encoding":"jsonParsed"}]}'quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:100High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const USDC_MINT = 'EPjF…t1v';
quoted -
low Exfiltration
read-dotenvSKILL.md:155Reads a .env fileexport $(cat .env | xargs) && node deposit.js
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:226High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const BASE_ASSET = process.env.BASE_ASSET ?? "EPjF…t1v";
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:276High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)base_asset: "EPjF…t1v",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:300High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)base_asset: "EPjF…t1v",
quoted
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 23, 66, 69, 127, 192, 193): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 77/100
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (web, node) 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
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4504 tokens
- 100Steps. 58 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 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 17 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)
- +1No license
- +2Single-language instructions
- +3Description length 183: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 58 items
- +3Output format is stated explicitly
- +4Has examples (18 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.