Digital wallet management for crypto and fiat. Unified interface for managing multiple wallet types.
33
Quality
18%
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/wallet/SKILL.mdQuality
Discovery
22%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 description is too vague to effectively guide skill selection. It identifies the domain (digital wallets) but fails to specify concrete actions and completely lacks trigger guidance. The description would benefit significantly from listing specific capabilities and adding explicit 'Use when...' conditions.
Suggestions
Add a 'Use when...' clause with trigger terms like 'check wallet balance', 'send crypto', 'transfer funds', 'view transactions', 'cryptocurrency wallet'
Replace vague 'management' with specific actions like 'check balances, send/receive funds, view transaction history, manage multiple addresses'
Include common cryptocurrency names and wallet-related terms users would naturally mention (e.g., 'Bitcoin', 'Ethereum', 'MetaMask', 'seed phrase')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'management' and 'unified interface' without listing concrete actions. It doesn't specify what operations can be performed (e.g., send, receive, check balance, swap tokens). | 1 / 3 |
Completeness | The description weakly addresses 'what' (wallet management) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'crypto', 'fiat', 'wallet', and 'digital wallet', but misses common variations users might say like 'bitcoin', 'ethereum', 'send money', 'check balance', 'cryptocurrency', or specific wallet names. | 2 / 3 |
Distinctiveness Conflict Risk | The crypto/fiat wallet domain is somewhat specific, but 'management' is vague enough that it could overlap with general finance skills, payment processing skills, or cryptocurrency trading skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a marketing brochure rather than actionable guidance. It lists features and wallet types without providing any concrete implementation details, code examples, or workflows that Claude could actually execute. Critical operations like fund transfers and wallet recovery are mentioned but completely undefined.
Suggestions
Add executable code examples for core operations (checking balance, sending funds) with specific API calls or library usage
Define step-by-step workflows with validation checkpoints for sensitive operations like transfers and backup/recovery
Include concrete configuration examples showing how to connect to different wallet types (crypto, hardware, payment)
Add references to detailed documentation files for each wallet type and complex operations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief but lacks substance - it's essentially a feature list without actionable content. The brevity comes from absence of useful information rather than efficient communication. | 2 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The 'Usage Examples' are just natural language prompts, not actual implementation details or API calls Claude could use. | 1 / 3 |
Workflow Clarity | No workflows defined for any operations. Critical processes like 'Transfer funds between wallets' or 'Wallet backup/recovery' have no steps, validation, or error handling described. | 1 / 3 |
Progressive Disclosure | Content is a shallow feature list with no references to detailed documentation. No links to implementation guides, API references, or examples for the complex features mentioned. | 1 / 3 |
Total | 5 / 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.