AC x402card-agent
Discover, issue, top up, and manage an x402card wallet-owned virtual card through public Base-USDC x402 entrypoints, including exact-payment validation, payer ownership, idempotent recovery, asynchronous issuance or funding, owner authentication, balance, and secure credential reveal. Use when an owner wants a virtual card, wants to add funds to an active card, or needs the x402card card contract without exposing a private key.
Discover, issue, top up, and manage an x402card wallet-owned virtual card through public Base-USDC x402 entrypoints, including exact-payment validation, payer…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, 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: 3. 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 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 814 tokens
- 100Running it twice. No mutating operations
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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 431: enough signal without eating the budget
- +4Structure: 3 headings
- +3Step-by-step instructions: 13 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.