agent-payment-x402

Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol. Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, actionable skill body with an explicit fail-closed workflow and validation checkpoints well suited to a destructive/financial operation, plus concrete pinned-version configs and SDK references. Main room for improvement is tightening repeated deprecation messaging and optionally moving the larger code/SDK reference material into bundle files.

Suggestions

Consolidate the okx-x402-payment deprecation note to a single location to reduce repetition and save tokens.

Consider moving the full TypeScript orchestrator example or the per-language seller-SDK URL table into a references/ file, keeping SKILL.md as a tighter overview.

Tighten the inline prose in the Examples section (e.g. the fail-closed rationale) since the code already demonstrates the pattern.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient — a decision table, tight protocol and controls sections, and one focused code example — but repeats the deprecation note for okx-x402-payment in three places and re-explains fail-closed reasoning inline, which could be trimmed slightly.	4 / 5
Actionability	It provides copy-paste-ready MCP config, a complete executable TypeScript orchestrator example with real imports, a named tool table, and exact pinned versions and SDK URLs, covering the common buyer and seller cases concretely.	5 / 5
Workflow Clarity	The orchestrator example lays out an explicit sequence with validation checkpoints — validate credentials, set policy and assert success, preToolCheck with five distinct fail-closed error paths before any paid action — matching the rubric's validate->fix->retry feedback-loop standard for destructive/financial operations.	5 / 5
Progressive Disclosure	Structure is good with clear sections (When to Use, Decision Tree, How It Works, MCP Integration, Examples, Best Practices, Production Reference) and external links are one level deep, but there are no bundle files and the inlined code example plus seller-SDK URL table could arguably live in a reference file; organization is strong but not perfectly split.	4 / 5
	Total	18 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both what the skill does and when to use it, with concrete trigger phrases and named integrations. It could be even more distinctive by foregrounding the x402 protocol trigger and adding a lay synonym or two.

Suggestions

Lead the 'Use when' clause with the most common user phrasing (e.g. 'when an agent needs to spend money or pay for an API call') before the technical budget-control terms.

Add a brief synonym such as 'agent spending' or 'agent funds' so the description matches more natural user language.

Dimension	Reasoning	Score
Specificity	The description names multiple concrete actions — 'payment execution', 'per-task budgets', 'spending controls', and 'non-custodial wallets' — plus two specific chain integrations (Base via agentwallet-sdk, X Layer via OKX), giving comprehensive coverage rather than generic language.	5 / 5
Completeness	It explicitly answers both 'what' (add x402 payment execution with budgets, controls, non-custodial wallets) and 'when' ('Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet'), with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Natural phrases like 'pay for something itself', 'per-task budgets', 'spending controls', and 'non-custodial wallet' are ones a user would say, but it leans slightly technical and lacks some lay synonyms a user might use (e.g. 'agent spending', 'agent funds').	4 / 5
Distinctiveness Conflict Risk	The x402 / per-task-budget / non-custodial-wallet niche is fairly distinct, but 'agent pays for an API' has minor overlap with cost-aware-llm-pipeline and general payment skills, so it is mostly rather than perfectly distinct.	4 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/agent-payment-x402/SKILL.md
Commit: 06c5e11

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.