✓
Purpose & Capability
Name, description and runtime instructions all describe a headless browser (CDP/MCP/Puppeteer/Playwright) and the required actions (download binary, run serve, connect via WS) match that purpose.
!
Instruction Scope
The SKILL.md explicitly instructs the agent to download and execute precompiled binaries from external URLs and to modify user shell config (~/.bashrc) to persist telemetry settings. Those actions go beyond in-process guidance and grant the skill the ability to place and run code on the host — acceptable for a tool installer but higher-risk and should be constrained (sandboxing, verification).
ℹ
Install Mechanism
There is no formal install spec in the registry package; the instructions tell the agent to curl binaries from GitHub Releases and to pull a Docker image from Docker Hub. Using GitHub/Docker Hub is standard, but the skill provides no checksums, signatures, or alternate trusted release URLs — downloading and executing binaries from the network is inherently risky without provenance verification.
!
Credentials
The skill requests no declared credentials, which is proportionate. However it documents that telemetry is enabled by default (and provides LIGHTPANDA_DISABLE_TELEMETRY to disable it) and shows examples using proxy auth or Authorization headers. Default telemetry collection without clear privacy details and the skill writing to ~/.bashrc to persist settings are privacy/credential risks. The SKILL.md references environment effects that are not declared in the skill manifest.
ℹ
Persistence & Privilege
The skill does not set always:true and does not modify other skills. It does instruct persistent changes (moving binary to /usr/local/bin, echoing env exports to ~/.bashrc) which create lasting system state; these are typical for an installer but are notable persistence actions the user should review.
What to consider before installing
This skill appears to be what it claims (a headless browser) but carries typical installer risks: it tells the agent to download and run prebuilt binaries and to modify shell config to persist telemetry settings. Before installing, verify the upstream project (GitHub repo, releases and release checksums/signatures), prefer running the binary inside a container or isolated VM, do not run as root, set LIGHTPANDA_DISABLE_TELEMETRY=true if you want to avoid default data collection, avoid exposing the MCP/CDP ports to untrusted networks, and inspect the Docker image source. If you need stronger assurance, request the upstream project's release checksums or build from source in an isolated environment and confirm maintainer identities. If you can, run initial tests inside Docker or a disposable VM rather than on a production host.