Agent skill · software engineering · mvanhorn
pp-netlify
Every Netlify API endpoint, plus a local SQLite mirror of your whole account so you can search, diff, and audit across all sites at once — offline and agent-native. Trigger phrases: `list my netlify sites`, `check netlify deploys`, `search netlify form submissions`, `audit netlify dns`, `compare netlify env vars`, `use netlify`, `run netlify`.
Why this skill is useful
Adds a CLI tool that provides unique cross-site commands for managing multiple Netlify accounts, including offline search and auditing capabilities.
What it needs
Requires netlify-pp-cli installed locally. About 9k tokens when loaded. Last updated 2026-08-06. 1,890 stars on the source repository.
What this skill does
Netlify — Printing Press CLI Prerequisites: Install the CLI This skill drives the netlify-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first: 1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows: 2. Verify: netlify-pp-cli --version 3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill. If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead: If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds. The official netlify-cli is stateless and per-site. netlify-pp-cli syncs your sites, deploys, DNS, env vars, and form submissions into a local database, then adds cross-site commands no other tool has: env-drift compares variables across sites, submissions search runs offline full-text search over every form, dns-audit flags dangling records, and overview shows the health of every site in one view. When to Use This CLI Use this CLI when you manage more than one Netlify site and need account-wide answers: comparing env vars across sites, searching form submissions, auditing DNS, or reviewing recent deploys. It is also the right tool for agents that need structured JSON output and typed exit codes over the Netlify API. Anti-triggers Do not use this CLI for: Do not use this CLI to run local dev servers or netlify dev — use the official netlify-cli for local development. Do not use it to build or bundle site assets; it manages the account via the API, it does not compile sites. Unique Capabilities These capabilities aren't available in any other tool for this API. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills mvanhorn/netlify