Agent skill · mvanhorn

pp-webflow

The whole Webflow Data API, plus a local database that lets you audit SEO, diff staging against live, and preview a publish before you trigger it. Trigger phrases: `audit the SEO on my Webflow site`, `what would change if I publish this Webflow site`, `which Webflow CMS items are not published yet`, `bulk update my Webflow collection items`, `check my Webflow redirects`, `list my Webflow pages`, `use webflow`, `run webflow`.

What it needs

About 11k tokens when loaded.

What this skill does

Webflow — Printing Press CLI Prerequisites: Install the CLI This skill drives the webflow-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: webflow-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.5 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. Webflow's own CLI stops at sites, CMS, forms, and assets. Every page-level operation you actually need has an endpoint and no command: SEO metadata, page copy, redirects, robots.txt, custom code. This CLI covers all 117 Data API operations and adds a local SQLite mirror on top. The seven audit commands read that mirror rather than the API, so run sync --full once before seo audit, drift, publish preview, overview, redirects audit, collections completeness, or items bulk-set; without it they return empty. When to Use This CLI Reach for this CLI when the task involves a Webflow site's structure or content rather than its visual design. It is the right tool for auditing SEO metadata across many pages, comparing staged CMS content against what is live, previewing or triggering a publish, bulk-editing collection items, managing redirects and robots.txt, and reading or rewriting page copy through the page DOM. It is also the right tool whenever the question spans more than one site. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills mvanhorn/webflow

View the source on GitHub

Browse the @skills marketplace