lnd macaroon bakery
PassAudited by ClawScan on May 1, 2026.
Overview
This is a coherent Lightning node macaroon-management helper, but it handles powerful lnd credentials and creates persistent bearer tokens that should be reviewed carefully before use.
Install only if you intend to manage lnd macaroons. Run baking commands deliberately, keep admin.macaroon out of agent configs, inspect generated macaroons, use the least-privileged role, and confirm local lncli/jq/Docker tooling is trusted.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If misused, a generated macaroon could grant an agent access to Lightning node functions such as paying invoices, viewing balances, managing channels, or signing operations.
The skill explicitly uses lnd authentication material, including an admin or macaroon-generation-capable macaroon, to create new credentials.
You need lncli installed locally and copies of the node's TLS cert and a macaroon with `macaroon:generate` permission (typically admin.macaroon).
Use the narrowest role possible, avoid exposing admin.macaroon to agents, inspect each macaroon before deployment, and store generated macaroons with restrictive permissions.
Choosing an overly broad preset or custom permission list could give an agent more financial or node-control authority than intended.
The preset roles include permissions that can enable payment, channel-management, and signing capabilities. This is aligned with the skill's purpose, but the impact is high if the wrong role is granted.
"uri:/lnrpc.Lightning/SendPaymentSync" ... "uri:/lnrpc.Lightning/OpenChannelSync" ... "uri:/signrpc.Signer/SignOutputRaw"
Require human review of the selected role or custom URI list before baking a macaroon, especially for pay-only, channel-admin, signer-only, or custom permissions.
A user may install the skill without realizing it relies on locally installed command-line tools whose provenance and configuration affect the outcome.
The script depends on external tools such as lncli and jq, and optionally Docker, while the registry metadata lists no required binaries.
elif ! command -v lncli &>/dev/null; then ... "${LNCLI_CMD[@]}" listpermissions | jq -rVerify that lncli, jq, and Docker if used are installed from trusted sources and match the lnd node you intend to manage.