AB merktop-wallet
Pay for any x402-gated API or resource (and get paid) from a non-custodial Merktop wallet on Base. Every payment is pulled just-in-time from the user's own wallet under a hard on-chain spend cap, so this skill can never spend beyond the budget the user set.
Pay for any x402-gated API or resource (and get paid) from a non-custodial Merktop wallet on Base.
As a process B 67/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Exfiltration
net-credential-useREADME.md:24Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -s "https://facilitator.merktop.com/buyer/$MERKTOP_BUYER_KEY/pay?url=…"
vendor-host -
low Exfiltration
net-credential-useSKILL.md:38Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -s "https://facilitator.merktop.com/buyer/$MERKTOP_BUYER_KEY/pay?url=…"
vendor-host -
low Exfiltration
net-credential-useSKILL.md:41Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -s -X POST "https://facilitator.merktop.com/buyer/$MERKTOP_BUYER_KEY/pay?url=…" \
vendor-host
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 67/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 5 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 13 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 873 tokens
- 100Progress reporting. Reports progress
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 257: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.