x402
Use x402 protocol for HTTP-native crypto payments. Use when Clawdbot needs to pay for APIs, access paid resources, or handle 402 Payment Required responses. Supports USDC payments on Base, Ethereum, and other EVM chains via the x402 standard.
67
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 skill description that clearly defines a specific niche (x402 crypto payment protocol), lists concrete actions and use cases, and provides explicit trigger conditions. The description is concise yet comprehensive, with excellent trigger term coverage spanning protocol names, HTTP status codes, cryptocurrency terms, and blockchain networks.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: paying for APIs, accessing paid resources, handling 402 Payment Required responses, and specifies USDC payments on Base, Ethereum, and EVM chains via x402 standard. | 3 / 3 |
Completeness | Clearly answers both what ('HTTP-native crypto payments via x402 protocol, USDC payments on EVM chains') and when ('when Clawdbot needs to pay for APIs, access paid resources, or handle 402 Payment Required responses'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'x402', '402 Payment Required', 'crypto payments', 'USDC', 'Base', 'Ethereum', 'EVM chains', 'paid resources', 'pay for APIs'. These cover the terms a user or system would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: x402 protocol, 402 Payment Required responses, USDC crypto payments on specific chains. Very unlikely to conflict with other skills given the specificity of the payment protocol and blockchain context. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with good executable code examples and clear structure. Its main weaknesses are moderate verbosity (protocol explanation, network tables, V2 features that pad the content) and missing validation/verification steps in the payment workflow — there's no guidance on confirming payment settlement or handling retry failures. The content would benefit from trimming informational sections and adding explicit verification checkpoints.
Suggestions
Add a validation/verification step after payment (e.g., check transaction hash, confirm settlement) to create a proper feedback loop in the workflow.
Remove or condense the 'How x402 Works' conceptual overview, supported networks table, and V2 features section — these consume tokens without adding actionable guidance.
Add explicit error recovery guidance: what to do if the payment signature is rejected, if the transaction is pending, or if the 402 response is unexpected.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary sections like the supported networks table, payment schemes list, and V2 features that add bulk without being directly actionable. The 'How x402 Works' section explains a protocol flow Claude could infer from the code examples. | 2 / 3 |
Actionability | Provides fully executable TypeScript code examples for the SDK client, fetch wrapper, balance checking, and error handling. The manual curl flow gives concrete step-by-step commands. Code is copy-paste ready with realistic patterns. | 3 / 3 |
Workflow Clarity | The manual flow has a clear 4-step sequence, and the SDK usage is straightforward. However, there are no validation checkpoints — no step to verify the payment actually settled, no feedback loop if the retry with payment signature fails, and no guidance on confirming transaction success before proceeding. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and sections, but it's somewhat monolithic at ~150 lines. The V2 features, supported networks table, and payment schemes could be in separate reference files. External links are provided at the bottom but there are no bundle files to offload detailed content to. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
f45fcb5
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.