Security audit
Security checks across malware telemetry and agentic risk
This looks like a real creative media skill, but it needs review because it can upload user media and create public or persistent links by default.
Review before installing. Use this only if you are comfortable sending prompts, images, audio samples, and generated media to the pixcli service and its backend providers. Avoid voice cloning unless the speaker has explicitly authorized it, and prefer --private or --no-publish for podcasts or sensitive assets because the docs conflict on whether some shared links are permanent or expiring.
### What runs at runtime and why - **`npx --yes pixcli <command>`**: Downloads + caches the `pixcli` CLI from npm on first invocation, then runs it. All subsequent calls use the cached binary. The `--yes` flag is required in agent contexts to avoid interactive prompts. `pixcli` is an HTTP client — it sends prompts to the pixcli API (`https://pixcli.hilo.cx/api/v1/*`), polls for completion, and downloads the resulting files. It does not execute arbitrary code. - **`npx --yes remotion <command>`**: Same pattern for the Remotion video renderer. Only used when assembling final videos from generated assets using the bundled templates. - **`npm install`** (no arguments): Runs inside a copied template directory to install the dependencies declared in that template's `package.json`. The agent never passes package names to `npm install` — only hydrates declared deps. - **`ffmpeg` / `ffprobe`**: Local-only media operations (trim, merge, scale, get info). No network access.
42/42 vendors flagged this skill as clean.
No suspicious patterns detected.
