CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wallet-payments

Use when web_fetch returns HTTP 402, an API offers a paid tier or micro-toll, another agent charges USDC, or the user asks you to pay, tip or buy. Not for a plain balance or address check (call the wallet tool directly).

Quality

82%

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

86%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 dense, highly actionable instruction skill whose guidance is almost entirely non-obvious, environment-specific operational detail rather than background Claude already knows. The only meaningful gap is the absence of failure-path handling (what to do when a payment fails or is declined) in an otherwise well-checkpointed payment workflow.

DimensionReasoningScore

Conciseness

Nearly all content is environment-specific knowledge Claude cannot already have (x402 atomic units, paymaster sponsorship, the APPROVAL-REQUIRED protocol), with only minor trimmable padding such as the run-on caveats in paywall step 1 — 'efficient; minor instances of over-explanation that could be trimmed' rather than perfectly lean.

4 / 5

Actionability

Fully concrete instruction-only guidance: exact tool calls with parameters ('get_balance (token="USDC")', 'pay_for_resource ... resource_url and amount'), ready-to-use user-facing phrasings, and explicit do/don't rules ('Do NOT call web_fetch again after paying') covering the common cases — the top anchor.

5 / 5

Workflow Clarity

The 402 workflow is a clear 6-step sequence with real checkpoints (price verification with a no-guess rule, balance check, user notification before spend) plus approval-state handling, but it lacks a feedback loop for failed or rejected payment outcomes, fitting 'clear sequence with most checkpoints present; minor validation gaps' rather than the full error-recovery anchor.

4 / 5

Progressive Disclosure

This is a single-file skill (~50-line body) with no bundle files and no content that warrants external references; it is organized into clean, well-labeled sections (wallet actions, approval, paywalls, beyond paywalls, spending rules), which per the simple-skill guideline earns the top score on structure alone.

5 / 5

Total

18

/

20

Passed

Description

73%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 distinctive, well-triggered description with explicit use-when clauses and a rare explicit exclusion boundary. Its main weakness is that the 'what' is implied rather than stated — the concrete wallet operations (send USDC, pay paywalled resources) are absent from the description.

Suggestions

State the 'what' explicitly up front, e.g. 'Pay USDC from a Coinbase smart wallet: settle HTTP 402 paywalls, paid API tiers, and agent-to-agent charges' before the trigger list.

Add a few natural trigger synonyms such as 'purchase' or 'spend crypto' to broaden keyword coverage toward the comprehensive anchor.

DimensionReasoningScore

Specificity

Concrete trigger situations ('HTTP 402', 'paid tier or micro-toll', 'charges USDC') and the actions 'pay, tip or buy' are named, but the description never states what the skill actually performs (send USDC, pay paywalled resources, fund the wallet), matching the anchor 'names domain and 1-2 concrete actions, but not comprehensive'.

3 / 5

Completeness

The 'when' is explicit and specific ('Use when web_fetch returns HTTP 402... or the user asks you to pay, tip or buy') but the 'what' is only implied through those verbs — the wallet/USDC payment mechanism is never stated — fitting 'both present; when could be more explicit' inverted here as what being the weaker half, below the fully-explicit anchor 5.

4 / 5

Trigger Term Quality

Good natural-term coverage ('pay', 'tip', 'buy', 'paid tier') plus observable signals (402, web_fetch, USDC), but misses common variations like 'purchase', 'spend', or 'send money', so it sits at 'good keyword coverage; a few natural terms missing' rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche (payment triggers: 402 responses, paid tiers, USDC charges) with explicit negative boundary guidance ('Not for a plain balance or address check'), giving minimal conflict risk with any other skill — matches the 'clear niche with distinct triggers' anchor.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

Bitterbot-AI/bitterbot-desktop

Path

skills/wallet-payments/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.