skills/lnget/SKILL.md
Use lnget to fetch resources from L402-protected URLs that require Lightning payments. Covers basic fetching, payment limits (max cost, max routing fee), token cache management, and Lightning backend status. Use when an HTTP request returns 402 Payment Required and a Lightning micropayment is needed, or when downloading files behind a Lightning paywall.
npx skillsauth add roasbeef/claude-files lngetInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use lnget to fetch resources that require L402 Lightning payments.
Use lnget when:
# Fetch and print to stdout
lnget https://api.example.com/data
# Save to file
lnget -o output.json https://api.example.com/data
# Quiet mode
lnget -q https://api.example.com/data | jq .
# Set max payment (default: 1000 sats)
lnget --max-cost 500 https://api.example.com/data
# Set max routing fee (default: 10 sats)
lnget --max-fee 5 https://api.example.com/data
# Don't auto-pay (just show 402 response)
lnget --no-pay https://api.example.com/data
# JSON output (default)
lnget https://api.example.com/data
# Human-readable output
lnget --human https://api.example.com/data
# List cached tokens
lnget tokens list
# Remove expired/unused token
lnget tokens remove example.com
# Clear all tokens
lnget tokens clear --force
# Check connection status
lnget ln status
# Get node info
lnget ln info
# Fetch and parse JSON
data=$(lnget -q https://api.example.com/data)
echo "$data" | jq '.result'
lnget -o file.zip https://api.example.com/file.zip
lnget -c -o large.zip https://api.example.com/large.zip
if lnget tokens show example.com >/dev/null 2>&1; then
echo "Token cached"
fi
Config file: ~/.lnget/config.yaml
Key settings:
l402.max_cost_sats: Maximum automatic payment (default: 1000)l402.max_fee_sats: Maximum routing fee (default: 10)ln.mode: Backend type (lnd, lnc, neutrino)output.format: Default output format (json, human)--human for human-readable output~/.lnget/config.yamldevelopment
Clear-writing guide distilled from Steven Pinker's "The Sense of Style." Use when writing or revising prose that must be clear to a reader — documentation, design docs, specs, explanations, essays, emails, reports, RFCs, release notes — or when asked to make writing clearer, tighter, less academic, or less jargon-laden. Activate for "make this clearer", "tighten this", "why is this hard to read", "edit this for clarity", or any prose-quality pass.
development
Interactively debug Go programs in a single context using Delve (dlv) driven through tmux. Use when a bug requires runtime inspection — stepping through code, examining variables, walking goroutines, attaching to a live process, or debugging a hanging integration test — rather than just reading the source. Triggers include "step through this", "set a breakpoint", "attach to the running server", "why is this goroutine stuck", "debug this failing test".
development
Find similar vulnerabilities and bugs across codebases using pattern-based analysis. Use when hunting bug variants, building CodeQL/Semgrep queries, analyzing security vulnerabilities, or performing systematic code audits after finding an initial issue.
development
Refines an existing Go test suite — removes trivial/duplicate tests, strengthens weak assertions, reshapes tests around invariants, and closes branch-coverage gaps. Uses code-guided coverage and (when available) gremlins mutation-testing survivor data rather than relying on line coverage alone. Use when test quality is uneven, after a test-generation pass, before opening a PR, or as a quality gate on critical paths (consensus, channel state, payment flows). Triggers: "refine these tests", "tests are bloated", "tighten assertions", "remove trivial tests", "audit test quality", "/test-refine".