AC lobpay
LobPay Agent Skill - Purchase items via X402 protocol on Base network. Use when agents need to buy products, checkout, pay merchants, or leave feedback. Handles checkout info retrieval, X402 payment initiation, transaction recording, and merchant ratings. Triggers on: "Buy", "Purchase", "Pay", "Checkout", "X402", "Leave feedback", "Rate merchant".
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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-tokenreferences/api.md:146High-entropy token-like string (may be an id, hash or a credential)X-Payment-Token: 0x83…913
-
low Secrets in code
secret-high-entropy-tokenreferences/x402.md:35High-entropy token-like string (may be an id, hash or a credential)X-Payment-Token: 0x83…913
-
low Secrets in code
secret-high-entropy-tokenreferences/x402.md:77High-entropy token-like string (may be an id, hash or a credential)0x03…F7e
-
low Secrets in code
secret-high-entropy-tokenreferences/x402.md:82High-entropy token-like string (may be an id, hash or a credential)0x83…913
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: LobPay Agent Skill - Purchase items via X402 protocol on Base netw… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 470 tokens
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -31 of 6 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 349: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.