CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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, X Layer through OKX Payments / OKX Agent Payments Protocol, and Solana plus multi-network EVM through the upstream x402 packages with facilitator-based settlement. Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

73%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.

The body is exceptionally actionable and workflow-safe — executable pinned code, decision-tree routing, fail-closed validation, and adversarial testing guidance throughout. Its weaknesses are structural: nearly 600 lines inlined into a single file with zero reference files, and deep edge-case material (replay protection, ATA provisioning, facilitator choice) that should be split out to respect the token budget.

Suggestions

Split Option C's deep-dive material into reference files (e.g., references/seller-replay-protection.md, references/solana-ata-setup.md, references/facilitators.md) and keep SKILL.md as a decision-tree overview with one small Quick start example per path.

Trim the two large TypeScript blocks to their load-bearing core (policy registration, payOnce reservation, and the onAfterVerify claim hook) and move the full implementations into the references, shortening the always-loaded context by roughly half.

Reduce inline code-comment verbosity to the non-obvious invariants (e.g., reserve-before-await, fail-closed-vs-open tradeoff) and drop commentary that restates what the code visibly does, tightening the conciseness of the always-loaded portion.

DimensionReasoningScore

Conciseness

The prose does not pad with concepts Claude already knows — the content is dense, non-obvious domain knowledge ("the exact-SVM scheme makes the facilitator the transaction fee payer", "verification does not consume the authorization (settlement does)"). But the body runs ~585 lines with extended digressions (a ~140-line buyer client, a ~150-line Redis replay-protection server, Solana ATA provisioning) that exceed a lean SKILL.md, fitting the 3 anchor ('mostly efficient but could be tightened') rather than 2, since the length is information-rich rather than padded.

3 / 5

Actionability

Guidance is fully executable and copy-paste ready: pinned commands ("npm install -g agentwallet-sdk@6.0.0"), complete MCP JSON config, runnable TypeScript with pinned versions ("@x402/fetch@2.22.0"), a curl + jq account-existence check, and exact package/URL references per runtime. This matches the 5 anchor; the single declared stub ("declare function confirmWithUser") is explicitly justified ("Supply this from your harness — a real prompt, never a stub").

5 / 5

Workflow Clarity

A decision tree routes each need to a concrete path, and each path carries numbered steps with explicit validation checkpoints and error recovery: "Always verify success — a silent failure means no controls are active", the five-path fail-closed preToolCheck, "Test the policy adversarially — feed it a challenge demanding 5000000 atomic units… and assert that none of them produce a signature", and "Confirm live coverage at the facilitator's /supported endpoint before production". This matches the 5 anchor (clear sequence, explicit validation, feedback loops).

5 / 5

Progressive Disclosure

No references/, scripts/, or assets/ files exist — everything lives in one monolithic 585-line SKILL.md. Content that clearly belongs in separate files is inlined (facilitator comparison, Solana ATA provisioning guide, the full seller-side replay-protection implementation), which matches the 2 anchor despite the good section headers; it does not reach 3 because that anchor requires references to be present (even unclearly signaled), and here there are none.

2 / 5

Total

15

/

20

Passed

Description

92%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 description: it explicitly states both what the skill does and when to use it, with concrete capability and network coverage and a clearly demarcated niche. The only weakness is modest keyword breadth — a few natural user phrasings (agent wallet, micropayments, agent paying for API calls) are absent.

DimensionReasoningScore

Specificity

"Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets" lists multiple concrete capabilities, and the description further names concrete integration actions ("Supports Base through agentwallet-sdk, X Layer through OKX Payments / OKX Agent Payments Protocol, and Solana plus multi-network EVM through the upstream x402 packages with facilitator-based settlement"). This matches the 5 anchor (multiple specific concrete actions, comprehensive) rather than 4, since coverage spans actions, networks, and settlement mechanics with no significant gaps.

5 / 5

Completeness

Both parts are explicit: what — "Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets"; when — "Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet." The 'Use when' clause contains concrete trigger phrases, matching the 5 anchor exactly; it does not fall to 4 because the 'when' is explicit and specific rather than vague.

5 / 5

Trigger Term Quality

Natural phrases are present ("agent must pay for something itself", "per-task budgets", "spending controls", "non-custodial wallet", named chains Base/X Layer/Solana), which is good keyword coverage. A few natural terms a user would say are missing (e.g., "agent wallet", "micropayments", "agent paying for API calls", "spending limits"), so it fits the 4 anchor rather than 5's comprehensive synonym coverage; it is well above 3's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (x402 protocol, agentwallet-sdk, OKX Payments, facilitator-based settlement) with distinct triggers ("agent must pay for something itself"), so it is unlikely to fire for unrelated skills. It matches the 5 anchor (clear niche, distinct triggers, minimal conflict risk) rather than 4, which reserves for overlap with closely related skills.

5 / 5

Total

19

/

20

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 — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (593 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

affaan-m/ECC

Path

skills/agent-payment-x402/SKILL.md

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.