Multi-chain cryptocurrency wallet management. Check balances, send tokens, view transaction history across Ethereum, Solana, Bitcoin and more.
63
Quality
60%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xterrybit/crypto-wallet/SKILL.mdQuality
Discovery
82%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 description with strong specificity and excellent trigger terms covering multiple blockchain ecosystems. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The description effectively communicates capabilities but relies on implicit rather than explicit selection guidance.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Use when the user asks about crypto wallets, token transfers, blockchain balances, or mentions specific chains like ETH, SOL, BTC'
Consider adding file extensions or common abbreviations users might mention (e.g., '.sol', 'ERC-20', 'NFT transfers') to improve trigger coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Check balances, send tokens, view transaction history' - these are clear, actionable capabilities that describe exactly what the skill does. | 3 / 3 |
Completeness | Clearly answers 'what' (check balances, send tokens, view history across chains) but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the capabilities listed. | 2 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'cryptocurrency', 'wallet', 'balances', 'send tokens', 'transaction history', 'Ethereum', 'Solana', 'Bitcoin'. These cover common user terminology for crypto operations. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers - 'cryptocurrency', 'wallet', specific blockchain names (Ethereum, Solana, Bitcoin) make this highly distinguishable from other skills and unlikely to conflict. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is concise but severely lacks actionability - it reads like a feature list or marketing overview rather than executable guidance. For a skill involving financial transactions across multiple blockchains, the absence of concrete code examples, API usage, and explicit validation workflows for sending tokens is a critical gap.
Suggestions
Add executable code examples for core operations (checking balance, sending tokens) with actual API calls or library usage for at least one chain
Create explicit multi-step workflows for sending transactions with validation checkpoints (verify address format, confirm amount, check gas/fees, require user confirmation, verify transaction hash)
Add chain-specific reference files (e.g., ETHEREUM.md, SOLANA.md) with detailed API endpoints, authentication setup, and chain-specific considerations
Include concrete output formats showing what balance responses, transaction confirmations, and error states look like
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient - lists supported chains, features, and safety rules without unnecessary explanation. No verbose descriptions of what cryptocurrencies are or how blockchains work. | 3 / 3 |
Actionability | Provides only vague feature descriptions and natural language usage examples. No concrete code, API calls, commands, or executable guidance for actually checking balances, sending tokens, or interacting with any blockchain. | 1 / 3 |
Workflow Clarity | No workflow steps provided for any operation. 'Send tokens (with confirmation)' mentions confirmation but doesn't show the actual process, validation steps, or error handling for risky financial transactions. | 1 / 3 |
Progressive Disclosure | Content is brief and organized into clear sections, but for a multi-chain wallet skill this should reference detailed docs for each chain's specifics, transaction signing, or API configuration. No references to additional resources. | 2 / 3 |
Total | 7 / 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 | |
45f9fac
Table of Contents
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.