Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Manage LNbits Lightning Wallet (Balance, Pay, Invoice)
Manage LNbits Lightning Wallet (Balance, Pay, Invoice)
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Enable the assistant to safely and effectively manage an LNbits Lightning Network wallet.
NEVER Expose Secrets: Do NOT display Admin Keys, User IDs, or Wallet IDs. Explicit Confirmation: You MUST ask for "Yes/No" confirmation before paying. Format: "I am about to send [Amount] sats to [Memo/Dest]. Proceed? (y/n)" Check Balance First: Always call balance before pay to prevent errors. ALWAYS Include Invoice + QR: When generating an invoice, you MUST: (a) show the payment_request text for copying, and (b) output MEDIA: followed by the qr_file path on ONE line. NEVER skip this.
If the user does not have an LNbits wallet, you can create one for them on the demo server. python3 {baseDir}/scripts/lnbits_cli.py create --name "My Wallet" Action: Run the command. The CLI prints JSON containing adminkey and base_url to stdout (visible in the terminal). NEVER Expose Secrets (applies here): Do NOT repeat, quote, or display the adminkey or any secret from the output in your chat response. The user sees the command output in their terminal; that is the only place the key should appear. Instruct the user in plain language only, e.g.: "A new wallet was created. The command output above contains your adminkey and base_url. Copy those values from the terminal and add them to your configuration or .env as LNBITS_API_KEY and LNBITS_BASE_URL. Do not paste the adminkey here or in any chat."
Get the current wallet balance in Satoshis. python3 {baseDir}/scripts/lnbits_cli.py balance
Generate a Bolt11 invoice to receive funds. QR code is always included by default. amount: Amount in Satoshis (Integer). memo: Optional description. --no-qr: Skip QR code generation (if not needed). # Invoice with QR code (default) python3 {baseDir}/scripts/lnbits_cli.py invoice --amount 1000 --memo "Pizza" # Invoice without QR code python3 {baseDir}/scripts/lnbits_cli.py invoice --amount 1000 --memo "Pizza" --no-qr โ ๏ธ MANDATORY RESPONSE FORMAT: When generating an invoice, your response MUST include: Invoice text for copying: Show the full payment_request string so user can copy it QR code image: Output MEDIA: followed by the qr_file path on ONE line EXACT FORMAT (follow precisely): Here is your 100 sat invoice: lnbc1u1p5abc123... MEDIA:./clawd/.lnbits_qr/invoice_xxx.png CRITICAL: The MEDIA: and file path MUST be on the SAME LINE. This sends the QR code image to the user.
Convert any Bolt11 string to a QR code image file. python3 {baseDir}/scripts/lnbits_cli.py qr <bolt11_string> Returns: {"qr_file": "./.lnbits_qr/invoice_xxx.png", "bolt11": "..."}
โ ๏ธ REQUIRES CONFIRMATION: Decode first, verify balance, ask user, then execute. # Step 1: Decode to verify amount/memo python3 {baseDir}/scripts/lnbits_cli.py decode <bolt11_string> # Step 2: Pay (Only after user CONFIRMS) python3 {baseDir}/scripts/lnbits_cli.py pay <bolt11_string>
If the CLI returns a JSON error (e.g., {"error": "Insufficient funds"}), summarize it clearly for the user. Do not show raw stack traces.
Writing, remixing, publishing, visual generation, and marketing content production.
Largest current source with strong distribution and engagement signals.