ledger-dmk-implementation

Execute Ledger Device Management Kit (DMK) signing operations safely: initialize the SDK, establish a device session, verify device state, open the correct chain app, perform signing or device management operations, and return the result. Use when a developer needs to implement a signing operation (transaction, message, typed data), derive or retrieve an address from a Ledger device, send any command to a Ledger device, or perform device management operations such as genuine check, app install, or app uninstall.

1.38x

Quality

100%

Does it follow best practices?

Impact

98%

1.38x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Quality

Content

100%Weight 40%Scale 1-3

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 tightly written, gate-based workflow with concrete API calls, explicit validation checkpoints, and clear one-level-deep reference signaling. It is an exemplar of token-efficient, actionable hardware-operation guidance.

Dimension	Reasoning	Score
Conciseness	Lean and dense: every line is an actionable gate, decision table, or security rule, with no padding explaining what a Ledger or DMK is. Assumes Claude's competence throughout.	3 / 3
Actionability	Provides concrete executable API calls (startDiscovering, connect, OpenAppDeviceAction, new [Chain]SignerBuilder(...).build()), exact status enums, status words (5501, 6985, 0x9000), and copy-ready error messages.	3 / 3
Workflow Clarity	Five sequenced gates each with explicit validation checkpoints, feedback loops (WAIT/recheck, cancel-on-timeout), and error classification — exactly the validate→fix→retry structure the rubric rewards for destructive/batch operations.	3 / 3
Progressive Disclosure	Overview body signals one-level-deep references (dmk-sdk-reference.md, dmk-code-patterns.md, dmk-platform-patterns.md) with explicit load triggers per step; no deeply nested references. Note: referenced files are not present on disk, but structure and signaling are exemplary.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, uses natural trigger terms, and explicitly covers both what the skill does and when to use it. Third person voice is maintained throughout, with no vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "initialize the SDK, establish a device session, verify device state, open the correct chain app, perform signing or device management operations" — rather than vague language.	3 / 3
Completeness	Explicitly answers both what (the enumerated DMK operations) and when via an explicit "Use when a developer needs to..." clause with concrete triggers.	3 / 3
Trigger Term Quality	Covers natural developer phrasing including "signing operation (transaction, message, typed data)", "derive or retrieve an address", "send any command", and "genuine check, app install, or app uninstall".	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to Ledger DMK hardware operations with distinct triggers (signing, address derivation, device management) unlikely to conflict with generic skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: LedgerHQ/agent-skills
Path: skills/dmk/ledger-dmk-implementation/SKILL.md
Commit: 2edb393

Reviewed: 12 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.