Summary
I built an AI-assisted recovery skill on top of btcrecover and would love your feedback.
Repo: https://github.com/welliv/btcrecover-skill
What it is
An open-source AI skill (SKILL.md standard) that guides non-technical users through wallet recovery using btcrecover as the backend. Users describe their situation in plain English; the skill classifies the problem (password, seed, forensics, or hybrid), builds the right btcrecover command, explains it, and waits for user approval before running anything.
Key design decisions
- Advisor-not-actor — the skill generates commands, the user runs them. Never auto-executes.
- Three-tier security — offline-first (Tier 1), local agent + cloud API (Tier 2), full online (Tier 3) with explicit consent gates for each.
- Post-recovery protocol — sweep reminder, test transaction gate (clipboard hijacker detection), then nuke-session.sh for secure destruction of all session data.
- No third-party dependencies — btcrecover runs locally, no external services required.
- Your donation address goes first — btcrecover's donation link appears before the skill's own in every file.
Why your input would be especially valuable
Since btcrecover is the foundation, I want to make sure:
- The commands the skill generates match your intended usage patterns
- The edge cases it handles (seed recovery, passphrase recovery, wallet extraction) align with how btcrecover works
- Nothing I'm doing could conflict with future btcrecover features or API changes
What I'm asking
If you have time, a quick look at the repository or any feedback on the approach would mean a lot. No pressure — I know maintainer time is scarce.
Thanks for btcrecover. It made this project possible.
— welliv
Summary
I built an AI-assisted recovery skill on top of btcrecover and would love your feedback.
Repo: https://github.com/welliv/btcrecover-skill
What it is
An open-source AI skill (SKILL.md standard) that guides non-technical users through wallet recovery using btcrecover as the backend. Users describe their situation in plain English; the skill classifies the problem (password, seed, forensics, or hybrid), builds the right btcrecover command, explains it, and waits for user approval before running anything.
Key design decisions
Why your input would be especially valuable
Since btcrecover is the foundation, I want to make sure:
What I'm asking
If you have time, a quick look at the repository or any feedback on the approach would mean a lot. No pressure — I know maintainer time is scarce.
Thanks for btcrecover. It made this project possible.
— welliv