AC fluxa-agent-wallet
FluxA Agent Wallet allows AI agents to securely use a user’s wallet, enabling the agent to perform payment-related actions within the approved scope. Capabilities include x402 payments, USDC transfers, agent-to-agent transfers, payment links for receiving payments, AI social gifting, discovering and calling x402 resources (one-shot APIs), and using payment-related skills (one-shot skills). Use this tool when the user the user asks to perform any of these payment-related actions.
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
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-tokenPAYMENT-LINK.md:244High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"refundId": "plr_…Z-V",
quoted -
low Secrets in code
secret-high-entropy-tokenPAYMENT-LINK.md:277High-entropy token-like string (may be an id, hash or a credential)fluxa-wallet paymentlink-refund-get --id plr_…Z-V
-
low Secrets in code
secret-high-entropy-tokenPAYMENT-LINK.md:285High-entropy token-like string (may be an id, hash or a credential)fluxa-wallet paymentlink-refund-cancel --id plr_…Z-V
-
low Exfiltration
net-credential-useX402-PAYMENT.md:260Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -H "$HEADER_NAME: $TOKEN" "$API_URL"
security skill
Files scanned: 16. 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 62/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
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 18 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3505 tokens
- 100Running it twice. Mutating operations check current state
- low 11 top-level sections: this looks like several domains in one skill
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
- +1No license
- +2Single-language instructions
- +3Description length 483: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.