tdg-personal/agent-payment-x402
Add x402 payment execution to AI agents — per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents need to pay for APIs, services, or other agents.
84
84%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly communicates what the skill does and when to use it. It names a specific protocol (x402), lists concrete capabilities, and provides explicit trigger guidance. The main weakness is that trigger terms could be broader to capture more natural user language variations around payments and transactions.
Suggestions
Expand trigger terms to include natural variations like 'pay', 'transactions', 'crypto payments', 'micropayments', or 'billing' to improve discoverability when users use common language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: 'per-task budgets', 'spending controls', 'non-custodial wallets via MCP tools', and 'payment execution'. These are concrete, actionable features rather than vague language. | 3 / 3 |
Completeness | Clearly answers both 'what' (add x402 payment execution with per-task budgets, spending controls, non-custodial wallets) and 'when' (explicitly states 'Use when agents need to pay for APIs, services, or other agents'). | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'payment', 'budgets', 'wallets', 'APIs', 'agents', and 'x402', but misses common natural variations users might say such as 'pay', 'billing', 'crypto', 'micropayments', 'transactions', or 'spend'. The term 'x402' is quite technical and niche. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'x402 payment execution', 'AI agents', 'non-custodial wallets', and 'MCP tools' creates a very clear niche that is unlikely to conflict with other skills. The domain is specific and well-defined. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent workflow clarity and executable code examples that demonstrate real security-conscious patterns. Its main weakness is moderate verbosity — the conceptual sections explaining x402, ERC-4337, and spending controls could be trimmed since Claude understands these concepts, and the large inline code example could be referenced from a separate file to improve progressive disclosure.
Suggestions
Trim the 'How It Works' section significantly — Claude understands HTTP 402, smart accounts, and spending policies. Keep only the non-obvious details (e.g., that policy is set by orchestrator, not agent).
Move the full TypeScript example to a separate file (e.g., EXAMPLES.md) and keep only a minimal 5-10 line snippet in the main skill showing the critical pattern (set_policy + preToolCheck).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory content (e.g., explaining what x402 is, how ERC-4337 works, what non-custodial means) that Claude already knows. The code example is thorough but the extensive inline comments explaining obvious patterns (like 'fail-closed') add bulk. The 'How It Works' section is largely conceptual rather than actionable. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code with a complete MCP client setup, concrete tool names, a real JSON config block, and a detailed preToolCheck function with multiple error paths. The code is copy-paste ready and includes specific package versions and environment variable handling. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: validate credentials → connect transport → set spending policy (with error check) → run preToolCheck before any paid action. The preToolCheck function has five explicit error paths with fail-closed semantics. The orchestrator-before-agent pattern is clearly stated with a security note about preventing privilege escalation. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's somewhat monolithic — the lengthy code example and conceptual 'How It Works' section could be split into separate files. References to external resources (protocol spec, npm, NVIDIA PR) are present but the skill doesn't reference any companion files for advanced topics like wallet setup or testnet configuration. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents