Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· Finance & Trading
Bitcoin
Assist with Bitcoin transactions, wallets, Lightning, and security decisions.
skill openclawclawhub Free
Assist with Bitcoin transactions, wallets, Lightning, and security decisions.
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Wallet Compatibility Traps
Same seed phrase in different wallets can show zero balance β derivation paths differ (BIP44 for legacy, BIP84 for native segwit, BIP86 for taproot). Ask which wallet created the seed before troubleshooting "missing funds" Importing a seed into a watch-only wallet won't show funds if the wallet defaults to a different address type than the original Some exchanges still reject bc1p (taproot) addresses for withdrawals β verify before giving the user a taproot address
Fee Timing
Bitcoin fees follow predictable patterns: weekends and UTC night hours (00:00-06:00) are typically 50-80% cheaper than weekday peaks mempool.space/api/v1/fees/recommended gives current sat/vB rates β wallet built-in estimates are often 12-24 hours stale A transaction at 1 sat/vB during high congestion can stay unconfirmed for 2+ weeks, but will eventually drop from mempools (not fail, just disappear)
Stuck Transaction Recovery
RBF (Replace-By-Fee): sender broadcasts new tx with higher fee β only works if original was flagged replaceable (most modern wallets do this by default now) CPFP (Child-Pays-For-Parent): receiver creates a high-fee tx spending the unconfirmed output, incentivizing miners to confirm both β useful when sender didn't enable RBF If user is the receiver and stuck tx has no change output to them, CPFP won't help β they must wait or ask sender to RBF
Lightning Network Gotchas
Lightning invoices expire (default 1 hour on many wallets) β an expired invoice cannot receive payment even if the payer tries "Inbound liquidity" limits how much a user can receive β a fresh channel can send but not receive until the balance shifts Closing a channel during high on-chain fees can cost more than the channel balance β warn users before force-closing small channels Lightning payments are not automatically retried β if a route fails, the user must manually retry or the payment fails permanently
Privacy and Security Patterns
Dust attacks: tiny amounts sent to addresses to link them when user spends β advise not to consolidate dust with main UTXOs Address reuse lets anyone see full transaction history of that address β each receive should use a fresh address Clipboard malware silently replaces copied addresses β always verify first and last 6 characters match on both devices before confirming send Hardware wallet "verify on device" step is critical β if malware changed the address, only the device screen shows the real destination
Scam Recognition
"Send X BTC, receive 2X back" is always a scam β no exceptions, even if the account looks official "Recovery services" that ask for seed phrase will steal everything β legitimate recovery never needs the seed Fake wallet apps in app stores with slight name variations β verify publisher and download count before recommending "Support" DMing users on social media asking to "validate wallet" or "sync" β real support never initiates contact
Verification APIs
mempool.space is the current standard block explorer β blockchain.info is outdated and less reliable for fee data Transaction confirmed = included in a block. 1 confirmation is minimum, 6 is standard for high-value, some exchanges require 3 Check raw tx with: curl -s "https://mempool.space/api/tx/{txid}" β returns full transaction details including fee, size, confirmation status For address balance: curl -s "https://mempool.space/api/address/{address}" β shows funded/spent totals
Category context
Trading, swaps, payments, treasury, liquidity, and crypto-financial operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md