wallet
Digital wallet management for crypto and fiat. Unified interface for managing multiple wallet types.
26
18%
Does it follow best practices?
Impact
—
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.
The description is too vague and lacks concrete actions, explicit trigger guidance, and natural keyword coverage. It tells Claude this skill manages wallets but doesn't explain what specific operations it supports or when it should be selected over other potentially related skills. The absence of a 'Use when...' clause and specific capabilities makes it poorly suited for skill selection among many options.
Suggestions
Add specific concrete actions such as 'Check balances, send/receive crypto, manage fiat deposits/withdrawals, view transaction history, swap tokens across wallets.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about wallet balances, sending or receiving cryptocurrency, managing fiat currency accounts, or interacting with blockchain wallets.'
Include more natural trigger terms users would say, such as 'Bitcoin', 'Ethereum', 'token balance', 'transfer funds', 'wallet address', 'blockchain', '.eth', 'MetaMask', etc.
| 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 balances, swap tokens). | 1 / 3 |
Completeness | The 'what' is vaguely stated as 'wallet management' without specifics, and there is no 'when' clause or explicit trigger guidance at all. The missing 'Use when...' clause caps this at 2 per the rubric, but the weak 'what' brings it to 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'crypto', 'fiat', 'wallet', and 'digital wallet' that users might naturally say. However, it misses common variations like 'Bitcoin', 'Ethereum', 'token', 'balance', 'transfer', 'send', 'receive', or specific wallet names. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'crypto and fiat' wallet management is somewhat specific, but 'digital wallet management' could overlap with payment processing skills, cryptocurrency trading skills, or general finance tools. | 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 reads like a product brochure rather than actionable instructions for Claude. It lists features and wallet types without providing any concrete implementation details, code, commands, APIs, or workflows. For a domain involving financial operations, the absence of safety constraints, validation steps, and executable guidance makes this skill essentially non-functional.
Suggestions
Add concrete, executable code examples showing how to interact with specific wallet APIs or tools (e.g., web3.py for crypto wallets, specific SDK calls for payment wallets).
Define a clear workflow with validation checkpoints for sensitive operations like fund transfers and wallet backup/recovery, including error handling and confirmation steps.
Replace the feature bullet list with actionable instructions—specify which tools/libraries to use, what commands to run, and what outputs to expect.
Add safety constraints and boundaries: transaction limits, confirmation requirements before sending funds, backup verification steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but consists mostly of feature bullet lists that don't add actionable value—Claude already knows what wallets are and what features they might have. The feature list is filler rather than instruction. | 2 / 3 |
Actionability | There is no concrete code, no commands, no API references, no specific tools or libraries mentioned. The 'Usage Examples' are just natural language prompts, not executable guidance. Claude has no idea how to actually implement any wallet management from this content. | 1 / 3 |
Workflow Clarity | There are no steps, no sequences, no validation checkpoints. For a skill involving financial transactions (sending funds, backup/recovery), the complete absence of any workflow or safety checks is a critical gap. | 1 / 3 |
Progressive Disclosure | The content is a flat, shallow document with no references to supporting files, no structured navigation, and no bundle files to support it. There's no layered information architecture—just a marketing-style feature list. | 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 | |
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
f45fcb5
- 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.