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.
95
Quality
96%
Does it follow best practices?
Impact
Pending
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 well-crafted skill description that clearly defines its purpose (HTTP-native crypto payments via x402), provides explicit trigger conditions, and includes specific technical details about supported chains and payment types. The description uses proper third-person voice and balances technical accuracy with natural language triggers.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'pay for APIs', 'access paid resources', 'handle 402 Payment Required responses', and specifies 'USDC payments on Base, Ethereum, and other EVM chains via the x402 standard'. | 3 / 3 |
Completeness | Clearly answers both what ('Use x402 protocol for HTTP-native crypto payments', 'Supports USDC payments...') and when ('Use when Clawdbot needs to pay for APIs, access paid resources, or handle 402 Payment Required responses'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'pay for APIs', 'paid resources', '402 Payment Required', 'USDC', 'Base', 'Ethereum', 'EVM chains', 'x402', and 'crypto payments' - good coverage of both technical and natural terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with distinct triggers around x402 protocol, 402 responses, and crypto payments - unlikely to conflict with other skills due to the specific payment protocol and blockchain focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently teaches x402 payment protocol usage with concrete, executable examples. The workflow is clearly explained with both automatic SDK usage and manual curl steps. Minor improvement opportunity in splitting reference content (network tables, V2 features) into separate files for better progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, jumping straight to installation and usage without explaining what stablecoins, HTTP status codes, or blockchain concepts are. Every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples, complete curl commands, and specific CLI usage. Code is copy-paste ready with real imports, method calls, and error handling patterns. | 3 / 3 |
Workflow Clarity | The 4-step flow (Request → 402 Response → Pay & Retry → Access) is clearly sequenced. Manual flow section provides explicit numbered steps with validation at each stage. Error handling section covers failure modes. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is somewhat long (~150 lines) with inline content that could be split. Network tables, V2 features, and detailed manual flow could be separate reference files. | 2 / 3 |
Total | 11 / 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
45f9fac
- 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.