Pp Webflow

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/developer-tools/webflow/SKILL.md,
     regenerated post-merge by tools/generate-skills/. Hand-edits here are
     silently overwritten on the next regen. Edit the library/ source instead.
     See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

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:

   npx -y @mvanhorn/printing-press-library install webflow --cli-only

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:

go install github.com/mvanhorn/printing-press-library/library/developer-tools/webflow/cmd/webflow-pp-cli@latest

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. Note the split: the generated endpoint commands call the API directly, while the seven audit commands (seo audit, drift, publish preview, overview, redirects audit, collections completeness, items bulk-set) read the local mirror and need sync --full to have run first.

Anti-triggers

Do not use this CLI for:

• Do not use this CLI to change a site's visual design, styles, or layout. Those live in the Webflow Designer and are not exposed by the Data API.
• Do not use this CLI to build or deploy Webflow Cloud apps, DevLink component libraries, or Designer Extensions. The official @webflow/webflow-cli owns those workflows.
• Do not use this CLI to create or move elements on a page canvas. Only text content through the page DOM endpoints is reachable; structural editing requires the Designer app bridge.
• Do not use this CLI to crawl or audit the rendered public website. It reads Webflow's stored configuration, not the HTML a browser receives.

Unique Capabilities

These capabilities aren't available in any other tool for this API.

Local state that compounds

• seo audit — Find every page on a site with a missing, duplicated, or over-length SEO title or description before it costs you traffic.

  Reach for this instead of paging the pages endpoint yourself when you need the site-wide metadata problems ranked, not the raw page objects.

  webflow-pp-cli seo audit 580e63e98c9a982ac9b8b741 --agent

• drift — See exactly which CMS items were edited in staging but never published, field by field.

  Reach for this before any publish when you need to know what is actually about to go live rather than trusting the staging view.

  webflow-pp-cli drift 580e63fc8c9a982ac9b8b745 --agent

• overview — One row per site you have synced locally: pages, collections, unpublished items, SEO findings, days since last publish.

  Reach for this when the question starts with 'across all my sites'; every other tool forces you to ask it one site at a time. Covers the sites present in the local mirror, so sync every site you care about first.

  webflow-pp-cli overview --agent --select sites.displayName,sites.unpublishedItems,sites.daysSincePublish

Publish safety

• publish preview — See everything that would change if you published this site right now: pages edited since the last publish, draft pages, and unpublished CMS items, alongside the site's redirect-rule count.

  Reach for this as the pre-flight check before calling the publish endpoint, especially in CI where a surprise publish is expensive to undo.

  webflow-pp-cli publish preview 580e63e98c9a982ac9b8b741 --agent

• redirects audit — Catch redirects that shadow a live page, point nowhere, loop, or duplicate another rule.

  Reach for this during launch hygiene; the redirect endpoints let you read and write rules but never tell you which ones are wrong.

  webflow-pp-cli redirects audit 580e63e98c9a982ac9b8b741 --agent

Bulk content work

• items bulk-set — Apply the same field value to many CMS items selected by a condition. Previews the change set by default; --apply writes it, paced so you never hit a rate limit mid-run.

  Reach for this instead of looping the update endpoint yourself; it previews the change set first and survives a 60-request-per-minute ceiling.

  webflow-pp-cli items bulk-set 580e63fc8c9a982ac9b8b745 --match status=draft --set author=editorial --agent

• collections completeness — Per-field fill rate across a whole collection, so you can spot required fields nobody filled and schema fields nobody uses.

  Reach for this before a content batch goes live when you need to know which fields are systematically empty rather than checking items one at a time.

  webflow-pp-cli collections completeness 580e63fc8c9a982ac9b8b745 --agent

Command Reference

asset-folders — Manage asset folders

• webflow-pp-cli asset-folders <asset_folder_id> — Get details about a specific Asset Folder Required scope | assets:read

assets — Assets are files that are uploaded to your Webflow account.

• webflow-pp-cli assets delete — Delete an Asset Required Scope: assets: write
• webflow-pp-cli assets get — Get details about an asset Required scope | assets:read
• webflow-pp-cli assets patch — Update details of an Asset. Required scope | assets:write

collections — Collections are CMS collections of items.

• webflow-pp-cli collections delete — Delete a collection using its ID. Required scope | cms:write
• webflow-pp-cli collections details — Get the full details of a collection from its ID. Required scope | cms:read

form-submissions — Manage form submissions

• webflow-pp-cli form-submissions delete — Delete a form submission Required scope | forms:write
• webflow-pp-cli form-submissions get — Get information about a given form submissio. Required scope | forms:read
• webflow-pp-cli form-submissions modify — Update hidden fields on a form submission Required scope | forms:write

forms — Forms are forms that are created on your Webflow site.

• webflow-pp-cli forms <form_id> — Get information about a given form. Required scope | forms:read

pages — Pages are the pages in your Webflow site.

• webflow-pp-cli pages get-metadata — Get metadata information for a single page. Required scope | pages:read
• webflow-pp-cli pages update-settings — Update Page-level metadata, including SEO and Open Graph fields. Required scope | pages:write

sites — Sites are the sites in your Webflow workspace.

• webflow-pp-cli sites delete — Delete a site. <Warning title='Enterprise Only'>This endpoint requires an Enterprise workspace.
• webflow-pp-cli sites get — Get details of a site. Required scope | sites:read
• webflow-pp-cli sites list — List of all sites the provided access token is able to access. Required scope | sites:read
• webflow-pp-cli sites update — Update a site. <Warning title='Enterprise Only'>This endpoint requires an Enterprise workspace.

token — Manage token

• webflow-pp-cli token authorized-by — Information about the Authorized User Required Scope | authorized_user:read
• webflow-pp-cli token introspect — Information about the authorization token <Note>Access to this endpoint requires a bearer token from a [Data Client

webhooks — Webhooks are the webhooks in your Webflow site.

• webflow-pp-cli webhooks get — Get a specific Webhook instance Required scope: sites:read
• webflow-pp-cli webhooks remove — Remove a Webhook Required scope: sites:read

workspaces — Manage workspaces

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

webflow-pp-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.

Recipes

Rank SEO problems across a site without a crawler

webflow-pp-cli seo audit 580e63e98c9a982ac9b8b741 --agent --select findings.pageSlug,findings.issue,findings.severity

Reads the local pages mirror and returns only the three fields an agent needs to build a fix list, instead of the full page objects.

Check what a publish would actually change

webflow-pp-cli publish preview 580e63e98c9a982ac9b8b741 --json

Joins publish timestamps, page updates, unpublished item counts, and pending redirects into one pre-flight answer.

Find CMS items edited in staging but never published

webflow-pp-cli drift 580e63fc8c9a982ac9b8b745 --json

Diffs the staged and live copies of every item in the collection field by field.

Retag many items in one paced pass

webflow-pp-cli items bulk-set 580e63fc8c9a982ac9b8b745 --match category=news --set category=updates

Selects matching items from the local mirror and prints the change set. It previews by default; add --apply to execute against the API.

Search every synced page, item, and submission at once

webflow-pp-cli search "pricing" --limit 20 --json

Full-text search across the local mirror, which no other Webflow tool offers.

Auth Setup

Webflow accepts two token shapes on the same Authorization: Bearer header. A site token is generated per site under Site settings, Apps & Integrations, API access. A workspace token starts with ws- and covers every site in the workspace. Set either one as WEBFLOW_API_TOKEN in your environment; that is the only way to supply a static token, since this CLI has no set-token command. login runs the OAuth2 flow instead, and auth status shows what is currently loaded. Scopes matter more than the token shape: a token created without data scopes authenticates fine and then returns 403 OAuthForbidden: You are missing the following scopes on the first real call. doctor tells you whether a token loaded and whether the API is reachable; it does not enumerate scopes. Use token introspect for that, and read the 403 body, which names the exact scope you are missing. One endpoint sits outside all of this: workspaces audit-logs needs an Enterprise workspace plus a workspace token carrying workspace_activity:read, a scope the OAuth2 flow cannot grant at all.

Run webflow-pp-cli doctor to verify setup.

Agent Mode

Add --agent to any command. Expands to: --json --compact --no-input --no-color --yes.

• Pipeable — JSON on stdout, errors on stderr

• Filterable — --select keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:

  webflow-pp-cli asset-folders mock-value --agent --select id,name,status

• Previewable — --dry-run shows the request without sending

• Offline-friendly — sync/search commands can use the local SQLite store when available

• Non-interactive — never prompts, every input is a flag

• Explicit retries — use --idempotent only when an already-existing create should count as success, and use --ignore-missing only when a missing delete target should count as success

Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse .results for data and .meta.source to know whether it's live or local. A human-readable N results (live) summary is printed to stderr only when stdout is a terminal AND no machine-format flag (--json, --csv, --compact, --quiet, --plain, --select) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout.

Paths and state

Agents should treat the CLI's path resolver as part of the runtime contract:

• Use --home <dir> for one invocation, or set WEBFLOW_HOME=<dir> to relocate all four path kinds under one root.

• Use per-kind env vars only when a specific kind must diverge: WEBFLOW_CONFIG_DIR, WEBFLOW_DATA_DIR, WEBFLOW_STATE_DIR, WEBFLOW_CACHE_DIR.

• Resolution order is per-kind env var, --home, WEBFLOW_HOME, XDG (XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_STATE_HOME, XDG_CACHE_HOME), then platform defaults.

• config contains settings like config.toml and profiles. data contains credentials.toml, data.db, cookies, and auth sidecars. state contains persisted queries, jobs, and teach.log. cache contains regenerable HTTP/cache files.

• Stored secrets live in credentials.toml under the data dir. Existing legacy config.toml secrets are read for compatibility and leave config.toml on the first auth write.

• Run webflow-pp-cli doctor --fail-on warn to surface path and credential-location warnings. agent-context exposes a schema v4 paths block for agents that need the resolved dirs.

• For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags:

  {
    "mcpServers": {
      "webflow": {
        "command": "webflow-pp-mcp",
        "env": {
          "WEBFLOW_HOME": "/srv/webflow"
        }
      }
    }
  }

Fleet precedence: an inherited per-kind env var overrides an explicit --home for that kind. Use WEBFLOW_HOME or per-kind vars as durable fleet levers, and use --home only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing WEBFLOW_HOME, or doctor will not find credentials left under the former root.

Automatic learning

This CLI ships a self-capturing learning loop. The CLI does its own bookkeeping: every invocation is journaled locally, a failed flag followed by a corrected retry auto-derives a flag_alias candidate, and a teach on a query family without a playbook auto-synthesizes a playbook_candidate from the session's journal. Your job is judgment only: recall first, act on surfaced candidates, teach the final answer, playbook amend when you observe a correction. You never record failures by hand.

Step 1: recall before any discovery

Before list/search/drill commands on a new user question, run:

webflow-pp-cli recall "<user's question>" --agent

The response envelope:

{
  "query": "...",
  "normalized": "<normalized form>",
  "query_entities": ["..."],
  "found": true | false,
  "match_score": 0.0,
  "results": [
    { "resource_id": "...", "resource_type": "...", "venue": "...",
      "confidence": 2, "entity_match": "exact|partial|unknown",
      "source": "taught|preseed|pattern", "warnings": ["..."] }
  ],
  "mismatches": [ /* only when --debug-mismatches */ ],
  "warnings": [ /* top-level */ ],
  "candidates": [
    { "id": 12, "class": "flag_alias | playbook_candidate",
      "summary": "...", "sightings": 3, "last_seen": "...",
      "rationale": "...",
      "next_action": ["<trial command>", "webflow-pp-cli learnings confirm 12"] }
  ],
  "playbook": {
    "query_family": "...",
    "playbook": {
      "steps": [ { "cmd": "<command with {slot} substitution>", "purpose": "..." } ],
      "entity_slots": ["$ENTITY"],
      "expected_tool_calls": 3
    },
    "slots_resolved": { "$ENTITY": { "token": "<live token>", "canonical": "<canonical>" } },
    "notes": "<workarounds + gotchas for this query family>"
  },
  "notes": "<duplicate surface for non-playbook callers>"
}

Empty-store short-circuit: if the store has no learnings, playbooks, or candidates yet (recall finds nothing and learnings list and learnings candidates are both empty), skip recall for the rest of this session instead of taxing every query; resume recall-first once something has been taught.