
webflow-cli:troubleshooter
โ 100by webflow ยท part of webflow/webflow-skills
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.
This is the playbook your agent receives when the skill activates โ you don't need to read it to use the skill, but it's here to audit before installing.
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
- Ask user to describe issue: What command failed or what error occurred
- Determine error category:
- CLI not installed or wrong version
- Authentication failed
- Build/bundle failed
- Command not recognized
- Capture error message: Get exact error output
Phase 2: Run Diagnostics
- Check CLI installation: Run
webflow --version - Check authentication: Run
webflow auth loginif needed - Run command with --verbose: Execute failed command with
--verboseflag for detailed output - Use --debug-bundler (if bundle issue): Run with
--debug-bundlerflag to see bundler config - Check --help: Run
webflow <command> --helpto verify command syntax
Phase 3: Analyze & Fix
- Identify root cause: Parse error messages and diagnostic output
- Present fix: Show specific solution based on CLI error
- Apply fix: Execute fix commands
- 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 installedFix:
๐ Fix: Install Webflow CLI
Executing: npm install -g @webflow/cli
โ CLI installed
Verifying...
Executing: webflow --version
Output: @webflow/cli/1.5.2
โ
Issue resolvedExample 2: Build Failed
User prompt:
Build is failing but I don't know whyDiagnostics:
๐ 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 fileFix:
๐ 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 errorsDiagnostics:
๐ 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 dependencyFix:
๐ Fix: Install Missing Dependency
Executing: npm install styled-components
โ Dependency installed
Retrying bundle...
Executing: webflow library bundle
โ Bundle created successfully
โ
Issue resolvedGuidelines
CLI Diagnostic Commands
Version Check:
webflow --version
# or
webflow -VCommand Help:
webflow --help # General help
webflow library --help # Library commands help
webflow library bundle --help # Specific command helpVerbose Output:
# Add --verbose to any command for detailed debugging
webflow library bundle --verbose
webflow cloud deploy --verbose
webflow extension bundle --verboseDebug Bundler:
# Show final bundler configuration
webflow library bundle --debug-bundler
webflow extension bundle --debug-bundlerCommon Issues & Fixes
Issue: CLI Not Found
- Diagnostic:
webflow --versionfails - Fix:
npm install -g @webflow/cli - Verify:
webflow --versionshows version
Issue: Wrong CLI Version
- Diagnostic:
webflow --versionshows 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
--verboseflag - Fix: Fix errors shown in verbose output
- Verify: Build succeeds
Issue: Bundle Configuration Error
- Diagnostic: Run with
--debug-bundlerflag - Fix: Adjust bundler config in webflow.json
- Verify: Bundle succeeds
Issue: Missing Dependencies
- Diagnostic: "Module not found" errors
- Fix:
npm installor 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/cliAuthentication Required:
โ Authentication Failed
Fix:
webflow auth login
Follow browser prompts to authenticateBuild/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 outputUnknown 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 problemFile 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: **/*.logBest Practices
Always Start With:
- Check CLI version:
webflow --version - Check command syntax:
webflow <command> --help - Run with verbose: Add
--verboseflag
For Build/Bundle Issues:
- Use
--verbosefor detailed output - Use
--debug-bundlerto see config - Check import paths
- Verify dependencies installed
For Authentication Issues:
- Run
webflow auth login - Follow browser prompts
- Verify workspace access
For Installation Issues:
- Check Node.js version:
node --version - Install CLI globally:
npm install -g @webflow/cli - 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
--verboseoutput - Bundle error โ Check
--debug-bundleroutput - Missing deps โ
npm install
Documentation: https://developers.webflow.com/cli
npx skills add https://github.com/webflow/webflow-skills --skill webflow-cli:troubleshooterRun this in your project โ your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.
Licensed under MITโ you can use, modify, and redistribute it under that license's terms.
View the full license file on GitHub โ