How do I install the Bitcoin Descriptors skill?

Run npx skillmds@latest add claude-dev-suite/bitcoin-descriptors in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bitcoin Descriptors safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bitcoin Descriptors?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bitcoin Descriptors free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bitcoin Descriptors?

claude-dev-suite (@claude-dev-suite) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bitcoin Descriptors by claude-dev-suite

Name: Bitcoin Descriptors
Rating: 4.666666666666667 (3 reviews)
Author: claude-dev-suite

Bitcoin Descriptors

Output descriptors: BIP380-385 family. Descriptor language for declaring scriptPubKey templates with key origin info, ranges, checksums. Functions: pkh, wpkh, sh, wsh, tr, multi, sortedmulti, multi_a, addr, raw, combo, rawtr. USE WHEN: importing watch-only wallets, defining multisig, declaring scan ranges, exchanging key info between wallets.

claude-dev-suite Updated Sep 8, 2026 28 repo stars

File contents

Output Descriptors

Descriptor language: a way to describe a set of scriptPubKey templates (addresses) with all metadata needed to derive, scan, and sign them.

Why descriptors

Pre-descriptors, "import this xpub at BIP44 paths" required convention. Different wallets used different paths, making coordination fragile. Descriptors make the script type, derivation, and key origin explicit.

Core syntax

function(args)#checksum

Functions:

Func	Output type
`pk(KEY)`	P2PK
`pkh(KEY)`	P2PKH
`wpkh(KEY)`	P2WPKH (native segwit single-sig)
`sh(SCRIPT)`	P2SH wrapper
`wsh(SCRIPT)`	P2WSH wrapper (segwit script)
`tr(KEY)` or `tr(KEY, TREE)`	P2TR (Taproot)
`rawtr(KEY)`	P2TR with raw output key (no tweak) — rare, only when key already includes a commitment
`multi(k, KEY1, KEY2, ...)`	unsorted k-of-n multisig (legacy ordering)
`sortedmulti(k, KEY1, KEY2, ...)`	k-of-n with keys lexicographically sorted at runtime
`multi_a(k, KEY1, KEY2, ...)`	k-of-n multisig in Tapscript (uses CHECKSIGADD)
`addr(ADDRESS)`	hard-coded address
`raw(HEX)`	hard-coded scriptPubKey (advanced/debug)
`combo(KEY)`	shorthand for pk + pkh + wpkh + sh-wpkh (legacy compat)

Keys

A KEY is one of:

Hex pubkey (66 char compressed or 130 uncompressed).
WIF privkey (signing-capable descriptor).
xpub / xprv (extended key).
xpub with derivation: xpub.../84h/0h/0h/0/* or xpub.../<0;1>/* (multipath BIP389).

Key origin

Prefix [fingerprint/path] declares where this key came from in a master tree:

[d34db33f/84h/0h/0h]xpub.../<0;1>/*

d34db33f = fingerprint of master key (4-byte hex).
84h/0h/0h = path used to reach this xpub from master.
<0;1>/* = multipath: receive (0) and change (1) derivation chains.

Key origin is mandatory for any cross-wallet coordination (multisig, hardware signing). Without it, signers can't tell which device should sign.

Checksums

Every descriptor ends with #XXXXXXXX (8 chars, BCH code over the character set). Wallet APIs typically auto-compute via getdescriptorinfo.

Ranges

A descriptor with * in derivation is a ranged descriptor. Import specifies a range:

{
  "desc": "wpkh([d34db33f/84h/0h/0h]xpub.../<0;1>/*)#abcd1234",
  "active": true,
  "range": [0, 999],
  "next_index": 0,
  "timestamp": "now"
}

Range = inclusive integer range of indices to scan.

Examples

Single-sig watch-only

wpkh([d34db33f/84h/0h/0h]xpub.../<0;1>/*)#chk

2-of-3 multisig (P2WSH)

wsh(sortedmulti(2,
  [d34db33f/48h/0h/0h/2h]xpub.../<0;1>/*,
  [b15ec0de/48h/0h/0h/2h]xpub.../<0;1>/*,
  [c0ffee00/48h/0h/0h/2h]xpub.../<0;1>/*
))#chk

Taproot single-sig with key-only

tr([d34db33f/86h/0h/0h]xpub.../<0;1>/*)#chk

Taproot key-path + 2-of-3 script-path (Tapscript multisig)

tr([fp/86h/0h/0h]xpub.../<0;1>/*,
   multi_a(2,
     [a/86h/0h/0h]xpub1.../<0;1>/*,
     [b/86h/0h/0h]xpub2.../<0;1>/*,
     [c/86h/0h/0h]xpub3.../<0;1>/*))#chk

RPC integration

RPC	Purpose
`getdescriptorinfo "desc"`	Compute checksum, validate syntax
`deriveaddresses "desc" range`	Generate addresses for a range
`importdescriptors`	Add to descriptors wallet (watch-only or signing)
`listdescriptors`	List descriptors in current wallet

Common bugs

Missing key-origin → can't be used in multisig coordination.
Hardened path component without an xprv → derivation fails (you can't derive hardened from xpub).
Forgetting checksum on import in some implementations → rejection.
Mixing multi (unsorted, key order matters for multisig signing) vs sortedmulti — multi requires same exact order on every signer.

---name: bitcoin-descriptorsdescription: Output descriptors: BIP380-385 family. Descriptor language for declaring scriptPubKey templates with key origin info, ranges, checksums. Functions: pkh, wpkh, sh, wsh, tr, multi, sortedmulti, multi_a, addr, raw, combo, rawtr. USE WHEN: importing watch-only wallets, defining multisig, declaring scan ranges, exchanging key info between wallets.---# Output DescriptorsDescriptor language: a way to describe a **set of scriptPubKey templates**(addresses) with all metadata needed to derive, scan, and sign them.## Why descriptorsPre-descriptors, "import this xpub at BIP44 paths" required convention.Different wallets used different paths, making coordination fragile.Descriptors make the script type, derivation, and key origin **explicit**.## Core syntax```function(args)#checksum```Functions:| Func | Output type ||------|------------|| `pk(KEY)` | P2PK || `pkh(KEY)` | P2PKH || `wpkh(KEY)` | P2WPKH (native segwit single-sig) || `sh(SCRIPT)` | P2SH wrapper || `wsh(SCRIPT)` | P2WSH wrapper (segwit script) || `tr(KEY)` or `tr(KEY, TREE)` | P2TR (Taproot) || `rawtr(KEY)` | P2TR with raw output key (no tweak) — **rare**, only when key already includes a commitment || `multi(k, KEY1, KEY2, ...)` | unsorted k-of-n multisig (legacy ordering) || `sortedmulti(k, KEY1, KEY2, ...)` | k-of-n with keys lexicographically sorted at runtime || `multi_a(k, KEY1, KEY2, ...)` | k-of-n multisig in **Tapscript** (uses CHECKSIGADD) || `addr(ADDRESS)` | hard-coded address || `raw(HEX)` | hard-coded scriptPubKey (advanced/debug) || `combo(KEY)` | shorthand for pk + pkh + wpkh + sh-wpkh (legacy compat) |## KeysA KEY is one of:- Hex pubkey (66 char compressed or 130 uncompressed).- WIF privkey (signing-capable descriptor).- xpub / xprv (extended key).- xpub with derivation: `xpub.../84h/0h/0h/0/*` or `xpub.../<0;1>/*` (multipath BIP389).### Key originPrefix `[fingerprint/path]` declares where this key came from in amaster tree:```[d34db33f/84h/0h/0h]xpub.../<0;1>/*```- `d34db33f` = fingerprint of master key (4-byte hex).- `84h/0h/0h` = path used to reach this xpub from master.- `<0;1>/*` = multipath: receive (0) and change (1) derivation chains.Key origin is **mandatory** for any cross-wallet coordination(multisig, hardware signing). Without it, signers can't tell whichdevice should sign.## ChecksumsEvery descriptor ends with `#XXXXXXXX` (8 chars, BCH code over thecharacter set). Wallet APIs typically auto-compute via`getdescriptorinfo`.## RangesA descriptor with `*` in derivation is a **ranged descriptor**. Importspecifies a range:```json{ "desc": "wpkh([d34db33f/84h/0h/0h]xpub.../<0;1>/*)#abcd1234", "active": true, "range": [0, 999], "next_index": 0, "timestamp": "now"}```Range = inclusive integer range of indices to scan.## Examples### Single-sig watch-only```wpkh([d34db33f/84h/0h/0h]xpub.../<0;1>/*)#chk```### 2-of-3 multisig (P2WSH)```wsh(sortedmulti(2, [d34db33f/48h/0h/0h/2h]xpub.../<0;1>/*, [b15ec0de/48h/0h/0h/2h]xpub.../<0;1>/*, [c0ffee00/48h/0h/0h/2h]xpub.../<0;1>/*))#chk```### Taproot single-sig with key-only```tr([d34db33f/86h/0h/0h]xpub.../<0;1>/*)#chk```### Taproot key-path + 2-of-3 script-path (Tapscript multisig)```tr([fp/86h/0h/0h]xpub.../<0;1>/*, multi_a(2, [a/86h/0h/0h]xpub1.../<0;1>/*, [b/86h/0h/0h]xpub2.../<0;1>/*, [c/86h/0h/0h]xpub3.../<0;1>/*))#chk```## RPC integration| RPC | Purpose ||-----|---------|| `getdescriptorinfo "desc"` | Compute checksum, validate syntax || `deriveaddresses "desc" range` | Generate addresses for a range || `importdescriptors` | Add to descriptors wallet (watch-only or signing) || `listdescriptors` | List descriptors in current wallet |## Common bugs- Missing key-origin → can't be used in multisig coordination.- Hardened path component without an xprv → derivation fails (you can't derive hardened from xpub).- Forgetting checksum on import in some implementations → rejection.- Mixing `multi` (unsorted, key order matters for multisig signing) vs `sortedmulti` — multi requires same exact order on every signer.## See also- [psbt/SKILL.md](../psbt/SKILL.md)- [miniscript/SKILL.md](../miniscript/SKILL.md)- [../../wallets/hd/SKILL.md](../../wallets/hd/SKILL.md)

Frequently asked questions