Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ledgerhq/wire-devtool
Wire an existing devtool package into host apps (LLD, LLM, web-tools) and optionally create bindings
Passed 16 of 19 test cases with the skill, and 4 of 19 without it.
and 12 more in the full report
13 fixed5 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
If a devtool has props but the user chooses not to create a bindings hook during the selection prompt, what config value should be wired into the host configuration array?
| Checked | Without skill | With skill |
|---|---|---|
| Assigns config: undefined in the host configuration array. | Missed | Passed |
The instructions your model reads when the skill loads.
Reference: devtools/README.md.
Warning: bindings, protocols, registry, shell, transport, transport-panel, and wire are internal platform packages, not tools — do not wire them. feature-flags is an example of a real tool.
devtools/<tool-name>/ does not exist, stop and tell the user to generate it first:
pnpm --filter @devtools/registry add-tool
devtools/<tool-name>/src/types.ts to determine whether the tool has props (file present = has props). Do not read anything else.AskUserQuestion({
questions: [
{
question: "Which host apps should I wire this tool into?",
header: "Host wiring",
multiSelect: true,
options: [
{ label: "LLD", description: "apps/ledger-live-desktop" },
{ label: "LLM", description: "apps/ledger-live-mobile" },
{ label: "web-tools", description: "apps/web-tools" },
]
}
]
})
Stop here if the user selects none.
If the tool has props, check whether devtools/bindings/src/use<ToolName>ToolProps.ts already exists.
test cases passed, vs 4 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.