Webflow Cli:Troubleshooter logo

Webflow Cli:Troubleshooter

Organization
webflow
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.

Overview

Publisherwebflow
Repositorywebflow-skills
Skill namewebflow-cli:troubleshooter
Stars
122
Forks
18
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by webflow on GitHub. Read the source before you install it.

Installation

Install the Webflow Cli:Troubleshooter AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/webflow/webflow-skills.git /tmp/webflow-skills
mkdir -p .claude/skills
cp -r /tmp/webflow-skills/plugins/webflow-skills/skills/webflow-cli-troubleshooter .claude/skills/webflow-webflow-cli-troubleshooter
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Webflow Cli:Troubleshooter in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Webflow Cli:Troubleshooter on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Webflow Cli:Troubleshooter is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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:

bash
webflow --version
# or
webflow -V

Command Help:

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

Verbose Output:

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

Debug Bundler:

bash
# 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

Frequently asked questions

What does the Webflow Cli:Troubleshooter AI 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.

Why use Webflow Cli:Troubleshooter on TypingMind?

Because you install it once and use it with any model. Webflow Cli:Troubleshooter is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Webflow Cli:Troubleshooter in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/webflow/webflow-skills/tree/main/plugins/webflow-skills/skills/webflow-cli-troubleshooter. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Webflow Cli:Troubleshooter?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Webflow Cli:Troubleshooter?

As many as you like. As long as a model supports skills, you can use Webflow Cli:Troubleshooter with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Webflow Cli:Troubleshooter AI skill free?

Yes. It is published on GitHub by webflow under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇