MCPInstall

webflow-cli:troubleshooter

Diagnose and fix Webflow CLI issues including installation problems, authentication failures, build errors, and bundle problems. Uses CLI diagnostic flags (--version, --help, --verbose, --debug-bundler) for troubleshooting.

Installs
1K
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/webflow/webflow-skills --skill webflow-cli:troubleshooter
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads webflow-cli:troubleshooter automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Webflow CLI Troubleshooter

Diagnose and resolve Webflow CLI issues with diagnostic commands and automated fixes.

Important Note

ALWAYS use Bash tool for all diagnostic operations:

  • Execute diagnostic commands via Bash tool
  • Use Read tool to examine configuration files
  • Verify CLI installation: webflow --version
  • Check authentication: webflow auth login (if needed)
  • Use CLI diagnostic flags: --verbose, --debug-bundler, --help
  • DO NOT use Webflow MCP tools for CLI workflows
  • All CLI commands require proper descriptions (not context parameters)

Package Manager Detection:

  • Check for lock files: package-lock.json (npm), pnpm-lock.yaml (pnpm), yarn.lock (yarn)
  • If no lock file found, ask user which package manager to use (npm/pnpm/yarn)
  • Use detected package manager for all install/build commands

Instructions

Phase 1: Issue Identification

  1. Ask user to describe issue: What command failed or what error occurred
  2. Determine error category:
    • CLI not installed or wrong version
    • Authentication failed
    • Build/bundle failed
    • Command not recognized
  3. Capture error message: Get exact error output

Phase 2: Run Diagnostics

  1. Check CLI installation: Run webflow --version
  2. Check authentication: Run webflow auth login if needed
  3. Run command with --verbose: Execute failed command with --verbose flag for detailed output
  4. Use --debug-bundler (if bundle issue): Run with --debug-bundler flag to see bundler config
  5. Check --help: Run webflow <command> --help to verify command syntax

Phase 3: Analyze & Fix

  1. Identify root cause: Parse error messages and diagnostic output
  2. Present fix: Show specific solution based on CLI error
  3. Apply fix: Execute fix commands
  4. Verify: Re-run original command to confirm resolution

Examples

Example 1: CLI Not Installed

User prompt:

Getting "webflow: command not found"

Diagnostics:

🔍 Checking CLI Installation

Executing: webflow --version

Error: bash: webflow: command not found

❌ Webflow CLI not installed

Fix:

📋 Fix: Install Webflow CLI

Executing: npm install -g @webflow/cli

✓ CLI installed

Verifying...
Executing: webflow --version

Output: @webflow/cli/1.5.2

✅ Issue resolved

Example 2: Build Failed

User prompt:

Build is failing but I don't know why

Diagnostics:

🔍 Running Build with Diagnostics

Executing: webflow library bundle --verbose

Output:
[verbose] Loading webflow.json
[verbose] Found library config
[verbose] Building components from ./src/**/*.webflow.tsx
[verbose] Running bundler
Error: Failed to resolve import './missing-file.ts'

❌ Build failed: Missing import file

Fix:

📋 Fix: Missing Import

Issue: Component imports './missing-file.ts' which doesn't exist

Solutions:
1. Create the missing file
2. Fix the import path
3. Remove the import if not needed

Check your component imports and ensure all files exist.

Example 3: Bundle Configuration Issue

User prompt:

Bundle is failing with webpack errors

Diagnostics:

🔍 Checking Bundle Configuration

Executing: webflow library bundle --debug-bundler

Output:
[debug-bundler] Final bundler configuration:
{
  "entry": "./src/Component.tsx",
  "output": {
    "path": "/dist",
    "filename": "bundle.js"
  },
  "resolve": {
    "extensions": [".ts", ".tsx", ".js"]
  }
}

Error: Module not found: Can't resolve 'styled-components'

❌ Bundle failed: Missing dependency

Fix:

📋 Fix: Install Missing Dependency

Executing: npm install styled-components

✓ Dependency installed

Retrying bundle...
Executing: webflow library bundle

✓ Bundle created successfully

✅ Issue resolved

Guidelines

CLI Diagnostic Commands

Version Check:

webflow --version
# or
webflow -V

Command Help:

webflow --help                    # General help
webflow library --help            # Library commands help
webflow library bundle --help     # Specific command help

Verbose Output:

# Add --verbose to any command for detailed debugging
webflow library bundle --verbose
webflow cloud deploy --verbose
webflow extension bundle --verbose

Debug Bundler:

# Show final bundler configuration
webflow library bundle --debug-bundler
webflow extension bundle --debug-bundler

Common Issues & Fixes

Issue: CLI Not Found

  • Diagnostic: webflow --version fails
  • Fix: npm install -g @webflow/cli
  • Verify: webflow --version shows version

Issue: Wrong CLI Version

  • Diagnostic: webflow --version shows old version
  • Fix: npm update -g @webflow/cli
  • Verify: Latest version installed

Issue: Command Not Recognized

  • Diagnostic: "Unknown command" error
  • Fix: Check command with webflow --help
  • Verify: Use correct command syntax

Issue: Authentication Failed

  • Diagnostic: "Not authenticated" error
  • Fix: webflow auth login
  • Verify: Authentication succeeds

Issue: Build Failed

  • Diagnostic: Run with --verbose flag
  • Fix: Fix errors shown in verbose output
  • Verify: Build succeeds

Issue: Bundle Configuration Error

  • Diagnostic: Run with --debug-bundler flag
  • Fix: Adjust bundler config in webflow.json
  • Verify: Bundle succeeds

Issue: Missing Dependencies

  • Diagnostic: "Module not found" errors
  • Fix: npm install or install specific package
  • Verify: Build/bundle succeeds

Issue: Corrupted node_modules

  • Diagnostic: Unexplained build failures
  • Fix: rm -rf node_modules && npm install
  • Verify: Build succeeds

Error Handling

CLI Not Installed:

❌ Webflow CLI Not Found

Install:
npm install -g @webflow/cli

Verify:
webflow --version

Docs: https://developers.webflow.com/cli

Authentication Required:

❌ Authentication Failed

Fix:
webflow auth login

Follow browser prompts to authenticate

Build/Bundle Failed:

❌ Build Failed

Run with diagnostics:
webflow library bundle --verbose --debug-bundler

This shows:
- Detailed build steps
- Import resolution
- Bundler configuration
- Exact error location

Fix the errors shown in output

Unknown Error:

❌ Unknown Issue

Gather info:
1. What command are you running?
2. Run command with --verbose flag
3. Check command syntax with --help
4. Share full error output

This helps identify the specific problem

File Operations

Reading Config Files:

# View webflow.json
Read: webflow.json

# View package.json
Read: package.json

# View build output
Read: dist/

Discovering Files:

# Find config files
Glob: **/webflow.json

# Find components
Glob: src/**/*.webflow.tsx

# Find logs
Glob: **/*.log

Best Practices

Always Start With:

  1. Check CLI version: webflow --version
  2. Check command syntax: webflow <command> --help
  3. Run with verbose: Add --verbose flag

For Build/Bundle Issues:

  1. Use --verbose for detailed output
  2. Use --debug-bundler to see config
  3. Check import paths
  4. Verify dependencies installed

For Authentication Issues:

  1. Run webflow auth login
  2. Follow browser prompts
  3. Verify workspace access

For Installation Issues:

  1. Check Node.js version: node --version
  2. Install CLI globally: npm install -g @webflow/cli
  3. Verify installation: webflow --version

Quick Reference

Workflow: identify → diagnose → fix → verify

Diagnostic Flags:

  • --version / -V - Check CLI version
  • --help / -h - Show command help
  • --verbose - Detailed debugging output
  • --debug-bundler - Show bundler config

Common Fixes:

  • Not installed → npm install -g @webflow/cli
  • Wrong version → npm update -g @webflow/cli
  • Auth failed → webflow auth login
  • Build failed → Check --verbose output
  • Bundle error → Check --debug-bundler output
  • Missing deps → npm install

Documentation: https://developers.webflow.com/cli

FAQ

What does the webflow-cli:troubleshooter skill do?

Diagnose and fix Webflow CLI issues including installation problems, authentication failures, build errors, and bundle problems. Uses CLI diagnostic flags (--version, --help, --verbose, --debug-bundler) for troubleshooting.

How do I install webflow-cli:troubleshooter?

Run npx skills add https://github.com/webflow/webflow-skills --skill webflow-cli:troubleshooter in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/webflow-cli:troubleshooter/ (personal) or .claude/skills/webflow-cli:troubleshooter/ (project).

Which AI agents can use webflow-cli:troubleshooter?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is webflow-cli:troubleshooter safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains webflow-cli:troubleshooter?

It is published by webflow in webflow/webflow-skills. It has 1,011 recorded installs.

More from webflow/webflow-skills

View all →

webflow-cli:cloud

webflow/webflow-skills

Create, build, and deploy Webflow Cloud apps from the CLI (site-attached or project apps), and manage existing ones — apps, domains, environments, deployments, build/runtime logs, and environment variables including secrets. Use when initializing or deploying a Cloud app, importing an existing GitHub repository, setting up CI/CD (GitHub Actions or GitHub-linked deploys), setting or importing secrets, retrying or rolling back a deployment, diagnosing a failed build, or resolving app/environment/workspace IDs from webflow.json or env vars.

DevOps & Cloud1K installs

webflow-cli:code-component

webflow/webflow-skills

Create and deploy reusable React components for Webflow Designer. Configure existing React projects with webflow.json, build and bundle code, validate output, and deploy to workspace using library share. Use when building custom components for designers.

webflow-cli:designer-extension

webflow/webflow-skills

Build Designer Extensions for custom Webflow Designer functionality. Lists available templates, initializes extension projects from templates (default/react/typescript-alt), bundles extensions for upload, and serves locally for development.

Audit Webflow Code Components for architecture decisions - prop exposure, state management, slot opportunities, and Shadow DOM compatibility. Focused on Webflow-specific patterns, not generic React best practices.

Generate new Webflow Code Component boilerplate with React component, definition file, and optional styling. Automatically checks prerequisites and can set up missing config/dependencies.

webflow-cli:devlink

webflow/webflow-skills

Export Webflow Designer components to React/Next.js code for external projects. Configure devlink settings in webflow.json, sync design updates with devlink sync, validate generated code, show diffs, and provide integration examples. Use when building with Webflow designs in React/Next.js.

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.