CtrlK
BlogDocsLog inGet started
Tessl Logo

wallet

Use the wallet tools for all balance, send, and sign operations. Supports both ETH and ERC-20 tokens. The away wallet operates autonomously after setup — the home device does not need to be online.

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./packages/evm-wallet-experiment/openclaw-plugin/skills/wallet/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%Weight 40%Scale 1-5

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

The body is a well-organized, highly actionable tool catalog with concrete parameters and clear routing rules, assuming Claude's competence without padding. Its main gap is the lack of explicit pre-send validation for irreversible financial operations, which caps workflow clarity.

Suggestions

Add an explicit pre-send validation checkpoint (e.g. confirm recipient address and human-readable amount with the user before calling wallet_send/wallet_token_send) to support the destructive-operation feedback loop.

Remove the redundant re-description of wallet_token_send and wallet_token_balance in the ERC-20 section since they are already covered in the Tools list.

Add a brief quote→confirm→swap sequence note in the Token Swaps section so the validate-before-execute loop is explicit for swaps too.

DimensionReasoningScore

Conciseness

The body is lean with tight one-line tool descriptions and no padding about concepts Claude already knows, but the ERC-20 Token Operations section re-explains wallet_token_send/balance already covered in the Tools list, a minor redundancy that could be trimmed.

4 / 5

Actionability

Guidance is concrete and specific — exact tool names, parameter examples ('100.5' for 100.5 USDC, slippage 0.1–50%, 'ETH' or zero address), and clear routing rules; as an instruction-only skill the absence of code is not penalized because the guidance is fully actionable.

5 / 5

Workflow Clarity

Sequences are present (wallet_accounts → wallet_balance; quote → swap; automatic approval batching), but sending ETH/tokens is an irreversible destructive operation with no pre-send validation checkpoint confirming amount/recipient, so workflow clarity is capped at 3 per the destructive-operations rule.

3 / 5

Progressive Disclosure

At ~48 lines with no external references needed and no bundle files, the content is well-organized into clear sections (Tools, Autonomy, ERC-20, Swaps, Rules), meeting the under-50-lines simple-skill exception for a 5.

5 / 5

Total

17

/

20

Passed

Description

66%Weight 40%Scale 1-5

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 specific and well-targeted to a distinct Ethereum wallet niche, naming concrete balance/send/sign actions across ETH and ERC-20 tokens. Its main weakness is the lack of an explicit 'Use when...' trigger clause, which caps completeness, and a few missing natural synonyms like 'transfer'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to check an Ethereum balance, send ETH or ERC-20 tokens, swap tokens, or sign a message.'

Mention swaps and token resolution in the description to close the capability-coverage gap.

Include natural synonyms such as 'transfer' and 'crypto' alongside 'send' and 'ETH'.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'balance, send, and sign operations' plus 'ETH and ERC-20 tokens' — but omits notable capabilities like swaps and token resolution, leaving minor gaps that keep it below a 5.

4 / 5

Completeness

The 'what' is clear (balance/send/sign for ETH and ERC-20), but there is no explicit 'Use when...' trigger clause — 'Use the wallet tools for all balance, send, and sign operations' is an imperative instruction rather than explicit trigger guidance, so completeness is capped at 3 per the rubric.

3 / 5

Trigger Term Quality

Natural terms users would say are present ('balance', 'send', 'sign', 'ETH', 'ERC-20 tokens', 'wallet'), but common synonyms like 'transfer' and generic 'crypto' are missing.

4 / 5

Distinctiveness Conflict Risk

The Ethereum wallet niche (ETH/ERC-20 balance, send, sign) is clearly distinct with minimal overlap risk, though the absence of an explicit 'Use when' trigger phrase keeps it just below a 5.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Consensys-Incorporated/ocap-kernel
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.