Token导航 LogoToken导航

Agent Skill · 研究检索

webflow-cli%3adesigner-extension(Webflow CLI 3adesigner extension 搜索)

webflow-cli%3adesigner-extension 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

webflow-cli%3adesigner-extension 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为调用外部服务;许可证信息还不明确,暂无第三方扫描结果,按安装量在研究检索类的 73,675 个 Skill 里排第 20,822。

总安装 5,080周安装 216GitHub Stars 62下载 1,780核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:webflow-cli%3adesigner-extension(Webflow CLI 3adesigner extension 搜索)
来源仓库:https://github.com/webflow/webflow-skills
仓库路径:skills/webflow-cli%3Adesigner-extension
安装命令:
npx skills add https://github.com/webflow/webflow-skills --skill webflow-cli:designer-extension
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/webflow/webflow-skills --skill webflow-cli:designer-extension

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息。webflow-cli%3adesigner-extension 属于研究检索类 Skill,可作为该场景下的辅助能力补充。适合根据关键词、任务场景或来源线索快速定位候选结果。可结合来源仓库、安装命令和原始 README 继续核验具体用法。

安装前建议确认权限范围和维护状态,避免触发联网或文件读写。涉及外部请求时应注意频率限制和数据隐私合规要求。

来源仓库内路径:skills/webflow-cli%3Adesigner-extension

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/webflow/webflow-skills --skill webflow-cli:des…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

webflow-cli%3adesigner-extension 怎么安装?

在终端执行 npx skills add https://github.com/webflow/webflow-skills --skill webflow-cli:designer-exte…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

webflow-cli%3adesigner-extension 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

webflow-cli%3adesigner-extension 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

webflow-cli%3adesigner-extension 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

webflow-cli%3adesigner-extension 用的人多吗?

公开数据是累计安装 5,080 次,近一周安装 216 次,下载 1,780 次,GitHub 62 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

webflow-cli%3adesigner-extension 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 没有第三方扫描结果,安全性只能靠自己读源码判断。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 要求有安全扫描结论才肯安装的团队。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
webflow-cli%3adesigner-extension

Webflow CLI 3adesigner extension 搜索 · 本页

5,08062调用外部服务未明确未收录

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Designer Extension

Create and develop Designer Extensions for Webflow with template selection, local development server, and bundling for distribution.

Important Note

ALWAYS use Bash tool for all Webflow CLI operations:

  • Execute webflow extension commands via Bash tool
  • Use Read tool to examine generated files and schema (never modify)
  • Use Glob tool to discover project files
  • Verify CLI installation: webflow --version
  • Check authentication: webflow auth login (if needed)
  • 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: Environment Verification

  1. Verify CLI installed: Run webflow --version to confirm CLI is installed
  2. Check project state: Check if already in an extension project (look for webflow.json with extension schema)
  3. Identify operation type: Determine if user wants to:

- List available templates - Initialize new extension - Bundle existing extension - Serve extension locally

Phase 2: Template Listing & Selection

  1. List templates (if user asks or before init): Run webflow extension list
  2. Show available templates:

- default - Basic HTML/CSS/JavaScript template - react - React-based template - typescript-alt - Alternative TypeScript template

  1. Ask user to select template if initializing new extension

Phase 3: Extension Initialization

  1. Choose project name: Ask user for project directory name
  2. Run init command: Execute webflow extension init <project-name> <template>
  3. Read generated schema: Use Read tool to examine webflow.json
  4. Show schema structure: Display the 5 schema fields:

- name (required) - Extension name as it appears in Webflow - apiVersion (required) - API version (2) - publicDir (required) - Directory to build from (dist) - appIntents (optional) - Element types that can create connections - appConnections (optional) - Connection configurations

  1. Install dependencies: Run npm install in project directory

Phase 4: Local Development

  1. Start dev server: Execute webflow extension serve [port]
  2. Show dev server info:

- Default port: 1337 (unless user specifies different port) - Local URL: http://localhost:[port] - How to load in Designer

  1. Provide loading instructions:

- Open Webflow Designer - Load extension from local URL - Test functionality

Phase 5: Bundling for Upload

  1. Run bundle command: Execute webflow extension bundle
  2. Show bundle output: Display bundle.zip location and size
  3. Provide upload instructions: Guide for uploading to Webflow
  4. Document next steps: Testing and distribution guidance

Examples

Example 1: List Available Templates

User prompt:

Show me the available Designer Extension templates

Response:

🔍 Designer Extension Templates

Listing available templates...
Executing: webflow extension list

Output:
Available templates:
1. default        - Basic HTML, CSS, and JavaScript
2. react          - React-based extension
3. typescript-alt - Alternative TypeScript template

To create a new extension:
webflow extension init <project-name> <template>

Example:
webflow extension init my-extension react

Example 2: Initialize New Extension

User prompt:

Create a new Designer Extension called gallery-manager using React

Step 1: Initialize Project

📋 Initialize Designer Extension

Project name: gallery-manager
Template: react

Executing: webflow extension init gallery-manager react

Output:
✓ Created extension project at ./gallery-manager
✓ Generated project structure
✓ Created webflow.json with extension schema
✓ Set up React template

📁 Project Structure:
./gallery-manager/
├── webflow.json         # Extension schema
├── package.json         # Dependencies
├── src/
│   ├── index.html
│   ├── index.tsx
│   └── styles.css
├── dist/                # Build output
└── README.md

Installing dependencies...
Executing: cd gallery-manager && npm install

✓ Dependencies installed (45 packages)

Step 2: Show Schema

📋 Extension Schema (webflow.json)

Reading webflow.json...

{
  "name": "Gallery Manager",
  "apiVersion": "2",
  "publicDir": "dist",
  "appIntents": {},
  "appConnections": []
}

Schema Fields:
✓ name (required)      - Extension name in Webflow
✓ apiVersion (required) - API version: 2
✓ publicDir (required)  - Build directory: dist
  appIntents (optional) - Element connection types
  appConnections (optional) - Connection configs

Extension ready for development!

Example 3: Serve Extension Locally

User prompt:

Run the extension on my local dev server

Default Port (1337):

🚀 Starting Development Server

Executing: webflow extension serve

Output:
✓ Building extension
✓ Starting dev server
✓ Extension ready

📋 Development Server Running

Local URL: http://localhost:1337
Status: ✓ Active

How to Load in Designer:
1. Open Webflow Designer
2. Open any site
3. Load extension from URL: http://localhost:1337

Press Ctrl+C to stop server

Custom Port:

User: "Run on port 3000 instead"

🚀 Starting Development Server

Executing: webflow extension serve 3000

Output:
✓ Building extension
✓ Starting dev server on port 3000
✓ Extension ready

📋 Development Server Running

Local URL: http://localhost:3000
Status: ✓ Active

Load in Designer: http://localhost:3000

Example 4: Bundle Extension

User prompt:

Bundle my extension for upload

Step 1: Bundle

📦 Bundling Extension

Executing: webflow extension bundle

Output:
✓ Building production bundle
✓ Creating bundle.zip
✓ Bundle created successfully

Bundle Details:
- File: bundle.zip
- Location: ./dist/bundle.zip
- Size: 245 KB

✅ Bundle ready for upload!

Step 2: Upload Instructions

📤 Upload Instructions

Your extension is bundled and ready to upload.

Upload Steps:
1. Go to Webflow Designer Extensions dashboard
2. Upload bundle.zip
3. Test the extension
4. Submit for review (if distributing)

Bundle location: ./dist/bundle.zip

Example 5: Complete Workflow

User prompt:

Create a new Designer Extension for managing colors

Step 1: List Templates

🔍 Designer Extension Workflow

First, let me show available templates.

Executing: webflow extension list

Available templates:
1. default        - Basic HTML/CSS/JavaScript
2. react          - React-based (recommended)
3. typescript-alt - TypeScript alternative

Which template would you like to use? (default/react/typescript-alt)

*User selects: react*

Step 2: Initialize

📋 Creating Extension

Project name: color-manager
Template: react

Executing: webflow extension init color-manager react

✓ Project created at ./color-manager
✓ webflow.json generated
✓ React template configured

Installing dependencies...
✓ npm install complete

📋 Extension Schema:
{
  "name": "Color Manager",
  "apiVersion": "2",
  "publicDir": "dist",
  "appIntents": {},
  "appConnections": []
}

Step 3: Start Development

🚀 Starting Dev Server

Executing: webflow extension serve

✓ Server running at http://localhost:1337

Load in Designer:
1. Open Webflow Designer
2. Load extension from: http://localhost:1337
3. Start developing!

Server running... (Press Ctrl+C to stop)

Guidelines

Phase 1: CLI Verification

Installation Check:

# Check if CLI is installed
webflow --version

# If not installed, guide user:
npm install -g @webflow/cli

Authentication (if needed):

# Site authentication if required
webflow auth login

Phase 2: Template Management

List Templates Command:

webflow extension list

Available Templates:

  • default - Basic HTML, CSS, and JavaScript template
  • react - React-based extension with modern tooling
  • typescript-alt - Alternative TypeScript template

Phase 3: Initialization

Init Command:

webflow extension init <project-name> <template>

Arguments:

  • <project-name> (required) - Name of the new project directory
  • <template> (required) - One of: default, react, typescript-alt

Example Commands:

# Initialize with default template
webflow extension init my-extension default

# Initialize with React template
webflow extension init my-extension react

# Initialize with TypeScript template
webflow extension init my-extension typescript-alt

Project Structure After Init:

/project-name/
├── webflow.json         # Extension schema (required)
├── package.json         # Dependencies
├── src/                 # Source files
│   ├── index.html
│   ├── index.tsx (or .js)
│   └── styles.css
├── dist/                # Build output directory
└── README.md

Phase 4: Extension Schema

Schema in webflow.json:

{
  "name": "<Your Extension Name>",
  "apiVersion": "2",
  "publicDir": "dist",
  "appIntents": {
    "image": ["manage"],
    "form": ["manage"]
  },
  "appConnections": [
    "myAppImageConnection",
    "myAppFormConnection"
  ]
}

Schema Fields:

FieldDescriptionDefaultRequired
nameExtension name as it appears in Webflow-Yes
apiVersionAPI version to use for extension2Yes
publicDirDirectory to build and serve extension fromdistYes
appIntentsElement types that can create connections{}No
appConnectionsConnection configurations for extension[]No

Required Fields:

  • name - Must be unique and descriptive
  • apiVersion - Currently must be "2"
  • publicDir - Directory where built files are placed (default: "dist")

Optional Fields:

  • appIntents - Defines which element types can connect to your extension

- Example: {"image": ["manage"], "form": ["manage"]}

  • appConnections - Array of connection identifiers

- Example: ["myAppImageConnection", "myAppFormConnection"]

Phase 5: Local Development

Serve Command:

# Serve on default port (1337)
webflow extension serve

# Serve on custom port
webflow extension serve 3000

Arguments:

  • [port] (optional) - Port number to serve on (default: 1337)

Development Server:

Loading in Designer:

  1. Open Webflow Designer
  2. Open any site
  3. Go to Extensions menu
  4. Load extension from local URL: http://localhost:[port]
  5. Extension appears in Designer

Phase 6: Bundling

Bundle Command:

webflow extension bundle

Output:

  • Creates bundle.zip file in project directory
  • Contains all built files from publicDir
  • Ready to upload to Webflow

Bundle Contents:

  • Built JavaScript and CSS files
  • HTML entry points
  • Assets from publicDir
  • Extension schema

Error Handling

CLI Not Installed:

❌ Webflow CLI Not Found

Designer Extensions require the Webflow CLI.

Installation:
npm install -g @webflow/cli

After installation, verify:
webflow --version

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

Invalid Template:

❌ Invalid Template

Error: Template "vue" not found

Available templates:
- default
- react
- typescript-alt

Retry with valid template:
webflow extension init my-extension react

Port Already in Use:

❌ Development Server Failed to Start

Error: Port 1337 is already in use

Solutions:
1. Stop other process on port 1337
2. Use different port:
   webflow extension serve 3000

Find process using port:
lsof -ti:1337 | xargs kill -9

Missing webflow.json:

❌ Extension Schema Not Found

Error: webflow.json not found in current directory

This directory is not an extension project.

Solutions:
1. Initialize new extension:
   webflow extension init <name> <template>
2. Navigate to existing extension directory
3. Create webflow.json with required schema

Bundle Failed:

❌ Bundle Creation Failed

Error: Build failed with errors

Common Causes:
- Missing dependencies (run: npm install)
- Build errors in source files
- Invalid webflow.json schema
- Missing publicDir directory

Fix errors and retry:
webflow extension bundle

File Operations

Reading Extension Files: Always use Read tool (never modify):

# View extension schema
Read: webflow.json

# View package dependencies
Read: package.json

# View source files
Read: src/index.html
Read: src/index.tsx

Discovering Project Files: Use Glob tool to find files:

# Find all source files
Glob: src/**/*

# Find configuration files
Glob: *.json

# Find built files
Glob: dist/**/*

Never Use Write/Edit Tools:

  • Don't create or modify webflow.json with Write tool
  • Don't edit generated files
  • Let CLI generate all project files
  • Only read files to show content

Progress Indicators

For Init:

📋 Creating Extension...

[████████████████████████] 100%

✓ Project created
✓ Dependencies installed
Elapsed: 12s

For Bundle:

📦 Bundling Extension...

[████████████████████████] 100%

✓ Bundle created: bundle.zip
Elapsed: 5s

For Serve:

🚀 Starting Server...

[████████████████████████] 100%

✓ Server ready at http://localhost:1337
Elapsed: 3s

Best Practices

Template Selection:

  • Use react template for modern component-based development
  • Use default template for simple extensions or learning
  • Use typescript-alt for TypeScript-based projects

Development Workflow:

  1. List available templates
  2. Initialize project with chosen template
  3. Install dependencies
  4. Serve locally for development
  5. Test in Designer
  6. Bundle for upload
  7. Upload to Webflow

Schema Configuration:

  • Always include required fields: name, apiVersion, publicDir
  • Set appropriate appIntents if your extension connects to elements
  • Define appConnections for element integrations
  • Keep name descriptive and unique

Local Development:

  • Use default port 1337 for consistency
  • Keep dev server running during development
  • Test frequently in Designer
  • Check console for errors

Bundling:

  • Bundle only when ready for upload or distribution
  • Verify build completes without errors
  • Check bundle.zip size
  • Test bundled version before uploading

Quick Reference

Workflow: list templates → init → serve → develop → bundle → upload

Key Commands:

  • webflow extension list - Show available templates
  • webflow extension init <project-name> <template> - Create new extension
  • webflow extension serve [port] - Start dev server (default: 1337)
  • webflow extension bundle - Create bundle.zip for upload

Templates: default, react, typescript-alt

Schema Fields (webflow.json):

  • name (required) - Extension name
  • apiVersion (required) - API version (2)
  • publicDir (required) - Build directory
  • appIntents (optional) - Element connection types
  • appConnections (optional) - Connection configs

Dev Server: http://localhost:1337 (or custom port)

Bundle Output: bundle.zip in project directory

Documentation: https://developers.webflow.com/designer/reference/introduction

平台分布

Codex

37.73%
按下载量换算672

Claude

29.72%
按下载量换算529

Cursor

19.95%
按下载量换算355

Gemini CLI

10.4%
按下载量换算185

安全审计

暂无安全审计结果可展示。

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills