agentcash-wallet
Manage your agentcash wallet and call any x402-protected API with automatic payment. No API keys, no subscriptions — just a funded wallet (USDC on Base). USE FOR: - Checking wallet balance before API calls - Redeeming invite codes for free credits - Getting deposit address for USDC - Discovering endpoints and pricing on any x402-protected origin - Making paid API requests via the agentcash CLI - Troubleshooting payment failures TRIGGERS: - "balance", "wallet", "funds", "credits", "x402" - "redeem", "invite code", "promo code" - "deposit", "add funds", "top up" - "discover", "endpoints", "what APIs", "pricing" - "insufficient balance", "payment failed"
Install with Tessl CLI
npx tessl i github:Merit-Systems/agentcash-skills --skill agentcash-wallet100
Does it follow best practices?
Validation for skill structure
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 an excellent skill description that clearly defines a specific domain (x402 payment protocol and agentcash wallet management) with comprehensive trigger terms organized by use case. The description uses proper third-person voice, lists concrete actions, and provides explicit trigger guidance that would help Claude reliably select this skill when appropriate.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: checking wallet balance, redeeming invite codes, getting deposit address, discovering endpoints/pricing, making paid API requests, and troubleshooting payment failures. | 3 / 3 |
Completeness | Clearly answers both 'what' (manage wallet, call x402-protected APIs with automatic payment) and 'when' (explicit TRIGGERS section with natural language cues like 'balance', 'redeem', 'deposit', 'insufficient balance'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say, organized by category: 'balance', 'wallet', 'funds', 'redeem', 'invite code', 'deposit', 'top up', 'endpoints', 'pricing', 'payment failed' - these are all terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with unique domain-specific terms like 'x402', 'agentcash', 'USDC on Base' that are unlikely to conflict with other skills. The payment/wallet context is clearly scoped to this specific protocol. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill document that maximizes information density while maintaining clarity. It provides complete, executable commands for every operation, clear workflows with validation steps, and excellent organization through tables and logical section progression. The troubleshooting section anticipates common issues with specific solutions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what USDC, wallets, or APIs are. Every section delivers actionable information without padding. Tables are used effectively to compress information. | 3 / 3 |
Actionability | Fully executable commands throughout with copy-paste ready examples. The fetch command includes a complete POST example with JSON body. All CLI commands are specific and immediately usable. | 3 / 3 |
Workflow Clarity | Clear numbered workflow for calling paid APIs (discover → check → fetch). Includes validation checkpoint ('Always check before expensive operations') and explicit feedback guidance ('Read the instructions field'). Troubleshooting table provides error recovery paths. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from setup to advanced usage. References getting-started.md for installation details. Quick reference table provides at-a-glance summary. Content is appropriately scoped without being monolithic. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.