crypto-wallet

Multi-chain cryptocurrency wallet management. Check balances, send tokens, view transaction history across Ethereum, Solana, Bitcoin and more.

Quality

45%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/crypto-wallet/SKILL.md

Quality

Discovery

67%

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 strong in specificity and distinctiveness, clearly naming concrete actions and supported blockchains. Its main weaknesses are the absence of an explicit 'Use when...' clause and missing some common trigger term variations (e.g., 'crypto', 'ETH', 'BTC', 'transfer').

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about crypto wallets, token transfers, blockchain balances, or transaction history.'

Include common trigger term variations such as 'crypto', 'ETH', 'SOL', 'BTC', 'transfer', 'web3', and 'blockchain' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Check balances, send tokens, view transaction history' and specifies the domain clearly with named blockchains (Ethereum, Solana, Bitcoin).	3 / 3
Completeness	Clearly answers 'what does this do' with specific actions and supported chains, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes good keywords like 'wallet', 'balances', 'send tokens', 'transaction history', 'Ethereum', 'Solana', 'Bitcoin', and 'cryptocurrency', but misses common user variations like 'crypto', 'ETH', 'SOL', 'BTC', 'transfer', 'blockchain', or 'web3'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'multi-chain cryptocurrency wallet management' with specific blockchains and wallet operations creates a clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Implementation

22%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a feature overview or README rather than an actionable skill file. It lists supported chains and features but provides zero concrete guidance on how to actually check balances, send tokens, or interact with any blockchain. The absence of any executable code, tool usage patterns, API endpoints, or step-by-step workflows makes it nearly unusable as a skill.

Suggestions

Add concrete, executable examples for each core operation (e.g., specific tool calls or API commands for checking balances, sending tokens) rather than just listing natural language prompts.

Define a clear step-by-step workflow for the 'send tokens' operation with explicit validation checkpoints: verify address format, confirm amount, simulate transaction, get user confirmation, execute, verify on-chain.

Include specific tool/function signatures or SDK calls that Claude should use, such as the actual MCP tool names or API endpoints for each supported chain.

Add chain-specific configuration details or reference files (e.g., ETHEREUM.md, SOLANA.md) for chain-specific nuances like gas estimation, token approval flows, or SPL token accounts.

Dimension	Reasoning	Score
Conciseness	Reasonably brief but includes feature lists and chain lists that are somewhat generic. The 'Features' section is a bullet list of vague capabilities rather than actionable content, adding tokens without much value.	2 / 3
Actionability	No concrete code, commands, API calls, or executable guidance whatsoever. The 'Usage Examples' are just natural language prompts, not instructions on how to actually perform wallet operations. There are no SDK references, endpoints, or tool invocations.	1 / 3
Workflow Clarity	No workflow is defined for any operation. Sending tokens is a destructive/financial operation that critically needs a step-by-step process with validation checkpoints, yet only a vague safety rule ('confirm before sending') is mentioned without any concrete sequence.	1 / 3
Progressive Disclosure	The content is organized into clear sections with headers, which is good. However, there are no references to supporting files for detailed chain-specific instructions, API references, or configuration guides, and no bundle files exist to support deeper content.	2 / 3
	Total	6 / 12 Passed

Validation

81%

Warnings & errors only

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: 21 days ago

Table of Contents

Discovery Implementation Validation

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.