Mole Bug Patterns
tw93/Mole
A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.
Critical Bitcoin terminology rules to prevent confusion between bech32m (encoding) and taproot (address type).
Install Btc Terminology
$ npx skills add hiromaily/go-crypto-wallet --skill btc-terminology -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hiromaily/go-crypto-wallet btc-terminology --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hiromaily/go-crypto-wallet.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/btc-terminology .claude/skills/btc-terminology && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "btc-terminology" agent skill from https://github.com/hiromaily/go-crypto-wallet/tree/main/.claude/skills/btc-terminology into .claude/skills/btc-terminology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "btc-terminology", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hiromaily/go-crypto-wallet/tree/main/.claude/skills/btc-terminologyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hiromaily/go-crypto-wallet --skill btc-terminology -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hiromaily/go-crypto-wallet btc-terminology --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hiromaily/go-crypto-wallet.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/btc-terminology .agents/skills/btc-terminology && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "btc-terminology" agent skill from https://github.com/hiromaily/go-crypto-wallet/tree/main/.claude/skills/btc-terminology into .agents/skills/btc-terminology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "btc-terminology", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hiromaily/go-crypto-wallet --skill btc-terminology -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hiromaily/go-crypto-wallet btc-terminology --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hiromaily/go-crypto-wallet.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/btc-terminology .cursor/skills/btc-terminology && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "btc-terminology" agent skill from https://github.com/hiromaily/go-crypto-wallet/tree/main/.claude/skills/btc-terminology into .cursor/skills/btc-terminology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "btc-terminology", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hiromaily/go-crypto-wallet.git --path .claude/skills/btc-terminology--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hiromaily/go-crypto-wallet --skill btc-terminology -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hiromaily/go-crypto-wallet btc-terminology --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hiromaily/go-crypto-wallet.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/btc-terminology .gemini/skills/btc-terminology && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "btc-terminology" agent skill from https://github.com/hiromaily/go-crypto-wallet/tree/main/.claude/skills/btc-terminology into .gemini/skills/btc-terminology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "btc-terminology", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hiromaily/go-crypto-wallet btc-terminologyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hiromaily/go-crypto-wallet --skill btc-terminology -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hiromaily/go-crypto-wallet.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/btc-terminology .github/skills/btc-terminology && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "btc-terminology" agent skill from https://github.com/hiromaily/go-crypto-wallet/tree/main/.claude/skills/btc-terminology into .github/skills/btc-terminology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "btc-terminology", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hiromaily/go-crypto-wallet --skill btc-terminology -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hiromaily/go-crypto-wallet btc-terminology --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hiromaily/go-crypto-wallet.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/btc-terminology .opencode/skills/btc-terminology && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "btc-terminology" agent skill from https://github.com/hiromaily/go-crypto-wallet/tree/main/.claude/skills/btc-terminology into .opencode/skills/btc-terminology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "btc-terminology", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
btc-terminology- GitHub stars
- 128
- Token cost
- ~1.3k tokens
- SKILL.md length
- 292 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
Critical Bitcoin terminology rules to prevent confusion between bech32m (encoding) and taproot (address type).
- Works in 2 steps: Taproot (BIP341) = SegWit version 1… → Bech32m (BIP350) = Encoding format that…
- Working on BTC-related code
- SKILL.md covers 🚨 CRITICAL: Bech32m vs Taproot, Quick Reference Table, Common Mistakes and Technical Background, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Btc Terminology is an agent skill from hiromaily/go-crypto-wallet. Critical Bitcoin terminology rules to prevent confusion between bech32m (encoding) and taproot (address type). Use when working on BTC-related code, config files, or shell scripts.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Shell scripting. It works with Bitcoin. The repository describes itself as: Cryptocurrency wallet for trading for Bitcoin, Bitcoin cash, Ethereum, ERC20, XRP Leger (Ripple). The licence is MIT.
When your agent uses it
- Working on BTC-related code
- Tasks that involve Shell scripting
Example prompts
- “/btc-terminology”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Taproot (BIP341) = SegWit version 1 address type (P2TR - Pay-to-Taproot)
- Bech32m (BIP350) = Encoding format that fixes checksum issues in original Bech32
What it can do on your machine
Read from SKILL.md and the folder at commit 798ab10. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, bash and go).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Btc Terminology loads about 1.3k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 292 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from hiromaily/go-crypto-wallet at commit 798ab10, republished under its MIT licence (© hiromaily). 292 words, ~1,284 tokens.
Download SKILL.mdSave it as
.claude/skills/btc-terminology/SKILL.md (or your agent's skills folder).- name
- btc-terminology
- description
- Critical Bitcoin terminology rules to prevent confusion between bech32m (encoding) and taproot (address type). Use when working on BTC-related code, config files, or shell scripts.
BTC Terminology Rules
🚨 CRITICAL: Bech32m vs Taproot
This is a common source of bugs. Do NOT confuse these terms:
| Term | What It Is | Where Used |
|---|---|---|
| bech32m | Encoding format (HOW address is serialized) | Bitcoin Core RPC, shell scripts |
| taproot | Address type (WHAT the address represents) | Config files, domain model |
Key Rule: bech32m ≠ taproot — They are related but NOT interchangeable.
Quick Reference Table
| Context | Correct Term | Example |
|---|---|---|
| Config YAML/TOML files | taproot | address_type: "taproot" |
| Environment variables | taproot | WALLET_ADDRESS_TYPE="taproot" |
| Bitcoin Core CLI/RPC | bech32m | bitcoin-cli getnewaddress "" bech32m |
| Shell scripts (receiver addresses) | bech32m | getnewaddress "" bech32m |
Go domain code (internal/domain/address/) | taproot | AddrTypeTaproot |
Go Bitcoin Core interface (internal/domain/bitcoin/) | bech32m | AddressTypeTaproot = "bech32m" |
Common Mistakes
❌ WRONG
# Config file - DON'T use bech32m
address_type: "bech32m" # WRONG!# Shell script - DON'T use taproot for Bitcoin Core RPC
bitcoin-cli getnewaddress "" taproot # WRONG!✅ CORRECT
# Config file - Use taproot
address_type: "taproot" # CORRECT!# Shell script - Use bech32m for Bitcoin Core RPC
bitcoin-cli getnewaddress "" bech32m # CORRECT!Technical Background
Why Two Different Terms?
- Taproot (BIP341) = SegWit version 1 address type (P2TR - Pay-to-Taproot)
- Bech32m (BIP350) = Encoding format that fixes checksum issues in original Bech32
All Taproot addresses are encoded using bech32m, but:
- User-facing config uses "taproot" (what you want)
- Bitcoin Core RPC uses "bech32m" (how it's encoded)
Address Format Comparison
| Encoding | SegWit Version | Address Type | Prefix | Config Value |
|---|---|---|---|---|
| Base58 | N/A | P2PKH | 1... | legacy |
| Base58 | N/A | P2SH | 3... | p2sh-segwit |
| Bech32 | v0 | P2WPKH | bc1q... | bech32 |
| Bech32m | v1 | P2TR | bc1p... | taproot |
Codebase Mapping
The project has two different type definitions:
// internal/domain/bitcoin/address_type.go
// For Bitcoin Core RPC communication
AddressTypeTaproot AddressType = "bech32m" // Bitcoin Core uses "bech32m"
// internal/domain/address/types.go
// For user-facing configuration
AddrTypeTaproot AddrType = "taproot" // User sees "taproot"Conversion between these is handled by mapper functions:
// internal/infrastructure/api/btc/btc/mapper.go
// FromAddressType: "bech32m" (Bitcoin Core) → "taproot" (user-facing)
// ToAddressType: "taproot" (user-facing) → "bech32m" (Bitcoin Core)Verification Checklist
When working with Taproot/Bech32m code:
- Config files (YAML/TOML) use
address_type: "taproot" - Environment variables use
WALLET_ADDRESS_TYPE="taproot" - Bitcoin Core RPC calls in shell scripts use
bech32m - Shell scripts generating receiver addresses use
bech32m - Go code uses correct type for the layer:
- Domain/config layer:
AddrTypeTaproot(value:"taproot") - Bitcoin Core interface:
AddressTypeTaproot(value:"bech32m")
- Domain/config layer:
Related Files
| File | Purpose |
|---|---|
internal/domain/address/types.go | User-facing AddrType definitions |
internal/domain/bitcoin/address_type.go | Bitcoin Core AddressType definitions |
internal/infrastructure/api/btc/btc/mapper.go | Type conversion functions |
docs/chains/btc/taproot/user-guide.md | Taproot user guide |
Related Documentation
© hiromaily, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/btc-terminology of hiromaily/go-crypto-wallet.
Open the folder on GitHubat commit 798ab10
Compare with similar skills
Btc Terminology next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Btc Terminology this skillhiromaily/go-crypto-wallet | 128 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Mole Bug Patternstw93/Mole | 70k | — | ~2k | Automated safety check: Pass | GPL-3.0 | |
| CLI DeveloperJeffallan/claude-skills | 12k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| JSON Processing with jqcharmbracelet/crush | 29k | — | ~746 | Automated safety check: Pass | Custom licence | |
| Crush Shell Builtinscharmbracelet/crush | 29k | — | ~790 | Automated safety check: Pass | Custom licence | |
| Stacks PR Reviewstacks-network/stacks-core | 3.1k | — | ~1.1k | Automated safety check: Pass | GPL-3.0 |
Similar skills
CLI Developer
Jeffallan/claude-skills
Walks through designing, building and polishing a command-line tool: user workflow and command hierarchy, implementation in commander, click, typer or cobra, completions and cross-platform testing.
JSON Processing with jq
charmbracelet/crush
Explains the jq command built into Crush for querying, filtering and reshaping JSON, including its supported flags and where it differs from standard jq.
Crush Shell Builtins
charmbracelet/crush
Explains how to add a new in-process builtin command to Crush's embedded POSIX shell, so it is intercepted before reaching the OS, with context polling and exit-status rules.
Stacks PR Review
stacks-network/stacks-core
Review repository changes as they would be reviewed in a pull request.
Ff Worktrees
damus-io/damus
Fast-forward master and every git worktree branch up to a target ref (default github/master), skipping any worktree with unmerged commits.
More from hiromaily/go-crypto-wallet
All 17 skills in this repoBch Development
hiromaily/go-crypto-wallet
Bitcoin Cash (BCH) API implementation rules. An agent skill from hiromaily/go-crypto-wallet.
DB Migration
hiromaily/go-crypto-wallet
Database schema and migration workflow. An agent skill from hiromaily/go-crypto-wallet.
Devops
hiromaily/go-crypto-wallet
CI/CD and DevOps workflow. An agent skill from hiromaily/go-crypto-wallet.
Docs Update
hiromaily/go-crypto-wallet
Documentation update workflow. An agent skill from hiromaily/go-crypto-wallet.
Fix PR Review
hiromaily/go-crypto-wallet
Address PR review comments by selecting appropriate skills based on modified files.
Git Workflow
hiromaily/go-crypto-wallet
Git branch management, commit conventions, and PR creation workflow.
Related
Works with
Categories
Questions about Btc Terminology
What does Btc Terminology do?
Critical Bitcoin terminology rules to prevent confusion between bech32m (encoding) and taproot (address type). Btc Terminology is an agent skill from hiromaily/go-crypto-wallet. Critical Bitcoin terminology rules to prevent confusion between bech32m (encoding) and taproot (address type).
When should I use Btc Terminology?
Btc Terminology fits situations like: working on BTC-related code; tasks that involve Shell scripting.
How do I install Btc Terminology in Claude Code?
Run `npx skills add hiromaily/go-crypto-wallet --skill btc-terminology -a claude-code`. Or copy the skill folder (.claude/skills/btc-terminology in hiromaily/go-crypto-wallet) into .claude/skills/btc-terminology in your project. Claude Code loads it when a task matches its description.
How do I install Btc Terminology in Codex?
Run `npx skills add hiromaily/go-crypto-wallet --skill btc-terminology -a codex`. Or copy the skill folder (.claude/skills/btc-terminology in hiromaily/go-crypto-wallet) into .agents/skills/btc-terminology in your project. Codex loads it when a task matches its description.
Can I use Btc Terminology in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hiromaily/go-crypto-wallet --skill btc-terminology -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/btc-terminology, .gemini/skills/btc-terminology, .github/skills/btc-terminology and .opencode/skills/btc-terminology in your project.
What does Btc Terminology need to run?
SKILL.md names no scripts, command-line tools or credentials: Btc Terminology is instructions for the agent only.
Does Btc Terminology access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Btc Terminology safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Btc Terminology use?
Btc Terminology is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Btc Terminology use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Btc Terminology?
Skills that share tags, products or a category with Btc Terminology: Mole Bug Patterns (tw93/Mole, 70k stars), CLI Developer (Jeffallan/claude-skills, 12k stars), JSON Processing with jq (charmbracelet/crush, 29k stars) and Crush Shell Builtins (charmbracelet/crush, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Btc Terminology?
hiromaily (a GitHub user) maintains it in hiromaily/go-crypto-wallet, which has 128 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on April 22, 2026.
Source: hiromaily/go-crypto-wallet on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.