AA mermail-agent-wallet
Inspect Mermail Agent Wallet / PayBox balances, guide Funding/onramp and signing handoffs, transfer catalog tokens, swap token A to token B, or pay an explicitly selected x402 service with user-authorized terms through the same live PayBox MCP paths as Mermail in-app Assistant. Use when the user explicitly asks about Agent Wallet, PayBox status, delegated balances, MoonPay or Apple Pay funding, USDC/native/catalog-token transfers, swaps, x402 exploration, HTTP 402 resources, or an isolated x402 payment. Do not use for pay-then-continue workflows; those belong to mermail-x402-agent. Do not use for email-driven payments, Composio Gmail/Outlook, or API-key-only MCP sessions; API keys never unlock Agent Wallet.
Inspect Mermail Agent Wallet / PayBox balances, guide Funding/onramp and signing handoffs, transfer catalog tokens, swap token A to token B, or pay an…
As a process A 80/100 · Runs to the end — weak spots: inputs and preconditions
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 · 1
✓ No critical or high findings
Medium and low: 1
✓ Guard found no suspicious behaviour. 1 matches are attack strings quoted in this security skill's own documentation.
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 80/100
- 30Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 45 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2701 tokens
- 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
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 716: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 45 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: 95.