NotebookLM CLI
Analysis
The skill is a transparent NotebookLM CLI wrapper, but it gives an agent broad authenticated account-changing powers such as deletion and public sharing.
Findings (4)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
node {baseDir}/scripts/notebooklm.mjs delete --notebook <notebook_id> --yes
node {baseDir}/scripts/notebooklm.mjs share add user@example.com --permission editor
node {baseDir}/scripts/notebooklm.mjs share public --enableThe documented workflow exposes destructive no-confirm deletion and public/editor sharing through the agent-invocable wrapper, without explicit approval or safety-scoping guidance.
const result = spawnSync("notebooklm", args, { stdio: "inherit" });The script executes a local CLI binary with pass-through arguments. This is expected for a CLI wrapper, but it means the skill’s behavior depends on the local `notebooklm` executable.
Source: unknown Homepage: none
The registry metadata does not provide provenance or a homepage for the skill, while the skill relies on an external local CLI dependency.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
- NotebookLM CLI authenticated (run `login` if needed).
The skill depends on a local authenticated NotebookLM session, so commands run with the user’s NotebookLM account privileges.
