Lightning Security Module

This skill appears to implement the claimed remote-signer architecture, but several things to check before installing: - Required tools: the manifest lists no required binaries, but the scripts need Docker/docker-compose, lnd/lncli, jq, curl, openssl, tar/base64 (and git/Go if building from source). Make sure those are installed and that you trust them. - Sensitive outputs: the setup and export scripts write the seed mnemonic and wallet passphrase to disk (~/.lnget/signer) and export an admin macaroon in the credentials bundle by default. An admin macaroon grants full RPC rights — for production you should bake a signing-only macaroon as recommended in the docs instead of exporting admin.macaroon. - Missing sourced libs: several scripts source ../lib/*.sh (rest.sh, config-gen.sh). Those files are not in the manifest you provided; verify they exist in the environment and review them before running. Sourcing external shell code can execute arbitrary commands. - Image provenance: the script pulls lightninglabs/lnd from Docker Hub. If you proceed, prefer pinned versions, verify image digests/signatures, or build from source in a controlled environment. - Transfer risk: the credentials bundle is intentionally packaged as a base64 tarball for easy copy-paste — that convenience makes accidental or malicious exfiltration easier. Transfer bundles only over trusted channels and consider encrypting them in transit. - Operational advice: run the signer on a dedicated, well-hardened machine (air-gapped or firewall-restricted), use a scoped/signing-only macaroon in production, rotate macaroons, protect filesystem permissions, and audit any helper scripts that are sourced. Given the above mismatches and risky defaults, treat this skill as suspicious until you verify the missing helper scripts, confirm runtime dependencies, and change the default export to a least-privilege macaroon and an operationally secure transfer method.