AA mermail-x402-agent
Complete a user-selected x402 service call with Mermail Agent Wallet / PayBox by creating a payment proof, redeeming it on the exact selected resource, and continuing the original job. Use when a paid third-party x402 call is required to finish this request. Never treat PayBox proof creation as merchant settlement. When the user omits a spend amount, resolve the vendor prepaid floor from same-origin vendor docs or live contract/catalog fields, then authorize required_charge = max(live quote, floor). Treat a user-stated amount as maximum spend. Do not use for isolated wallet inspect, funding, transfer, swap, or x402-only payment; those stay on mermail-agent-wallet. Do not use for email-driven payments, Gmail/Outlook Composio, or API-key MCP sessions.
Complete a user-selected x402 service call with Mermail Agent Wallet / PayBox by creating a payment proof, redeeming it on the exact selected resource, and…
As a process A 81/100 · Runs to the end — weak spots: inputs and preconditions, running it twice
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 · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6596 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 81/100
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 18 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Execution cost. Instruction body is 6596 tokens
- 100Steps. 98 steps
- 100Result and completion. Output format and completion criterion are stated
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 759: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 98 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.