CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wallet-cli-usage

Official Ledger wallet-cli - USB-based CLI for Ledger hardware wallet flows (account discover, receive, balances, operations, send, swap quote/execute/status, genuine-check, assets token / token-by-id), the Ledger Key Ring (ring init/encrypt/decrypt/keys/destroy — LKRP-backed encryption of files and text), and Agent Intent (agent-intent enroll/recover/list/show/sync/send/swap/intents/status/cancel — enroll or recover a remote agent's software identity, import the Ledger Sync accounts it was granted, propose Ethereum and Solana payments and Ethereum swaps for human review, list the intents it proposed, check their status and cancel them, no device required, never broadcasts, a separate trust model from `ring`). Use for any wallet-cli command execution and for mapping informal requests to the right command.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

An exceptionally actionable, safety-conscious reference: every command has executable examples, exact flags, validation checkpoints, and an error-recovery table. Its costs are length and structure — material that belongs in reference files (Agent Intent internals, ring key-management detail) is inlined, and key rules are repeated across the callout, table, and error sections.

Suggestions

Move the Agent Intent deep-dive (enrollment trust model, recovery semantics, keychain/environment requirements) and the ring password-injection/rotation detail into references/ files, keeping in SKILL.md only the commands, required flags, and safety-critical rules.

State each sandbox/TTY/password rule once — the Commands table plus a single callout — and have the Common errors row reference it instead of restating it.

Trim duplicated device-readiness guidance between the top 'Device readiness' callout and the genuine-check row of the error table.

DimensionReasoningScore

Conciseness

The body is dominated by product-specific rules Claude cannot know (sandbox matrix, provider lists, exit codes), which justifies much of its ~670 lines — but there is real tightening left: sandbox requirements are stated four times (top callout, Commands table column, footnote *, and the USB-timeout error row), device-readiness rules are duplicated between the top callout and the genuine-check error row, and the Agent Intent section carries long prose passages (trust model, relay channel, keychain behavior) that could be condensed or moved to the reference. This matches anchor 3 ('mostly efficient but includes some unnecessary explanation or could be tightened') better than 4, where over-explanation would be only minor.

3 / 5

Actionability

Every flow ships copy-paste-ready commands with exact flags and realistic values — e.g. the WETH wrap/unwrap `--data` examples with padded calldata, the agent-intent status jq polling loops, `echo "destroy" | wallet-cli ring destroy` for non-interactive shells, and a Common errors table mapping each error string to a cause and a fix. Fully executable and covering the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

Multi-step flows are explicitly sequenced with validation checkpoints and feedback loops: "immediately run `session view`" before asking anything, "Always run with `--dry-run` first to validate calldata before signing", the two-phase Solana withdraw (undelegate → wait ~2–3 days → `--finalize`), the address-mismatch abort-and-genuine-check procedure, fingerprint comparison before approving enrollment, and "confirm with the user before the live run" for irreversible signatures. Destructive operations (send, ring destroy, agent-intent cancel) all carry confirmation/validation guidance, so no cap applies.

5 / 5

Progressive Disclosure

The one bundle reference (references/business-logic.md) exists, is clearly signaled at the top with a purpose statement ("for _why_ a command behaves the way it does… read references/business-logic.md"), and is one level deep — but the bulk of the skill is inlined in SKILL.md rather than split: the full Agent Intent deep-dive (~250 lines: enrollment trust model, recovery semantics, keychain requirements, environment isolation), the ring password-injection and rotation internals, and per-provider swap execution details are all candidates for reference files. This fits anchor 3 ('content that should be separate is inline') better than 4, whose example assumes the bulk lives in the separate file.

3 / 5

Total

16

/

20

Passed

Description

83%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.

A highly specific, third-person description that names the tool's niche precisely and covers its command surface at unusual granularity. Its weaknesses are moderate: the 'when' clause triggers on the tool name instead of natural user situations, and the earn/staking flow — a whole section of the skill — is absent from the description.

Suggestions

Rewrite the 'Use for' clause around user situations rather than the tool name, e.g. "Use when the user mentions their Ledger or hardware wallet, wants to check balances, send or swap funds, stake SOL/ETH, or encrypt secrets with their device".

Add the earn flow (earn yields/positions/deposit/withdraw) to the capability list so the description matches the skill's actual command surface.

DimensionReasoningScore

Specificity

The description lists many concrete actions across all three feature families — "account discover, receive, balances, operations, send, swap quote/execute/status, genuine-check", "ring init/encrypt/decrypt/keys/destroy — LKRP-backed encryption of files and text", "enroll or recover a remote agent's software identity, import the Ledger Sync accounts it was granted, propose Ethereum and Solana payments" — with comprehensive, command-level coverage. It clearly matches the 5 anchor (multiple specific concrete actions) rather than 4, since the action list goes well beyond 'several' with per-command granularity.

5 / 5

Completeness

Both halves are present: a clear, detailed 'what' (the three parenthesized command families) and an explicit 'when' ("Use for any wallet-cli command execution and for mapping informal requests to the right command"). It falls short of anchor 5 because the 'when' is self-referential to the tool name rather than concrete user trigger phrases, and the 'what' omits the earn/staking flow documented in the body — but it is well above anchor 3's 'when is missing or only weakly implied'.

4 / 5

Trigger Term Quality

Good natural-term coverage ("Ledger", "hardware wallet", "send", "swap", "balances", "payments", "encryption of files and text") but a few natural phrases users would say are missing — notably the entire staking/earning vocabulary ("stake", "yield", "earn") and common synonyms like "transfer" — and the trigger clause keys on the tool name ("any wallet-cli command execution") rather than user situations. It sits above anchor 3 (coverage is well beyond 'some relevant keywords') but below anchor 5 (not comprehensive including synonyms).

4 / 5

Distinctiveness Conflict Risk

"Official Ledger wallet-cli", unique command namespaces (ring, agent-intent), and the explicit "a separate trust model from `ring`" framing give it a clear niche with distinct triggers and minimal conflict risk with any other skill. Third-person voice throughout, so no voice penalty applies.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (679 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

LedgerHQ/agent-skills

Path

skills/wallet-cli/wallet-cli-usage/SKILL.md

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.