Skip to content

fix(skills): rewrite custom-code-management with full workflow and missing sections #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yan-xie-webflow merged 2 commits into from
Apr 7, 2026
+69 −32
Merged

fix(skills): rewrite custom-code-management with full workflow and missing sections #20

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9c6cc30
fix(skills): rewrite custom-code-management with full workflow and mi…
yan-xie-nk Apr 6, 2026
c7249c1
refactor(skills): condense custom-code-management to ~90 lines
yan-xie-nk Apr 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
101 changes: 69 additions & 32 deletions plugins/webflow-skills/skills/custom-code-management/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,50 +1,87 @@
---
name: custom-code-management
description: Add, review, or remove inline custom scripts on a Webflow site (up to 10,000 chars). Use for analytics, tracking pixels, chat widgets, or any custom JavaScript.
description: Add, review, or remove inline custom scripts on a Webflow site (up to 10,000 chars). Use for analytics, tracking pixels, chat widgets, or any custom JavaScript. Also manages page-level scripts.
---

# Custom Code Management

## Concepts
Add, review, and manage inline custom scripts on a Webflow site — analytics, tracking pixels, chat widgets, or any custom JavaScript.

Webflow custom code: **register** (store script) → **apply** (attach to site). Inline scripts only via MCP (max 10,000 chars).

## Important note
## Important Note

**ALWAYS use Webflow MCP tools for all operations:**
Use the following tools for all operations:
- `data_scripts_tool` with actions `list_registered_scripts` / `list_applied_scripts` - List scripts
- `data_scripts_tool` with action `add_inline_site_script` - Register inline script (no `<script>` tags)
- `data_scripts_tool` with action `delete_all_site_scripts` - Remove ALL scripts (no selective delete)
- `data_sites_tool` with action `list_sites` - List available sites
- Use Webflow MCP's `webflow_guide_tool` to get best practices **before any other tool call**
- Use Webflow MCP's `data_sites_tool` with action `list_sites` to identify available sites
- Use Webflow MCP's `data_scripts_tool` with action `list_registered_scripts` to list all registered scripts
- Use Webflow MCP's `data_scripts_tool` with action `list_applied_scripts` to list scripts applied to pages
- Use Webflow MCP's `data_scripts_tool` with action `add_inline_site_script` to register a new inline script
- Use Webflow MCP's `data_scripts_tool` with action `delete_all_site_scripts` to remove ALL site scripts (no selective delete)
- Use Webflow MCP's `data_scripts_tool` with action `get_page_script` to get custom code for a specific page
- Use Webflow MCP's `data_scripts_tool` with action `upsert_page_script` to add or update page-level custom code
- Use Webflow MCP's `data_scripts_tool` with action `delete_all_page_scripts` to remove all custom code from a page
- All tool calls must include the required `context` parameter (15-25 words, third-person perspective)

## Instructions

### View Scripts
1. Call `data_sites_tool` with action `list_sites` if needed, then call both list tools in parallel
2. Display registration and application status
### Phase 1: Discovery
1. **Call `webflow_guide_tool` first** — always the first MCP tool call
2. **Get the site**: Use `data_sites_tool` with action `list_sites`. If only one site, use it automatically.

### Phase 2: Analysis
3. **List scripts**: Call `list_registered_scripts` and `list_applied_scripts` in parallel
4. **Check page-level scripts** (if relevant): Use `get_page_script` for specific pages
5. **Present findings**: Name, version, location (header/footer), registration vs application status

### Phase 3: Planning & Confirmation
Before any mutation, present the plan and require explicit confirmation:
- Adding scripts: user must type **"add"**
- Removing ALL site scripts: user must type **"delete all"** (warn: no selective delete)
- Page-level changes: user must type **"update"**

### Phase 4: Execution
6. **Add site script**: `add_inline_site_script` with displayName, sourceCode, version, location, canCopy
7. **Remove all site scripts**: `delete_all_site_scripts`
8. **Add/update page script**: `upsert_page_script`
9. **Remove page scripts**: `delete_all_page_scripts`

### Phase 5: Verification
10. Re-list scripts to confirm success
11. Report what changed (name, location, version, char count)
12. Remind user to publish — suggest using `safe-publish` skill

## Examples

### Add Script
1. Gather: name, code, location (header/footer)
2. Validate: under 10,000 chars, no `<script>` tags
3. Preview with character count, require **"add"** to confirm
4. Call `data_scripts_tool` with action `add_inline_site_script` with displayName, sourceCode, version, location, canCopy
5. Remind user to publish
### Example 1: View scripts
**User:** "What scripts are on my site?"
1. `webflow_guide_tool` → `data_sites_tool` → `list_registered_scripts` + `list_applied_scripts` in parallel
2. Present summary of all scripts

### Remove Scripts
1. List current scripts
2. Warn: removes ALL scripts (no selective delete)
3. Require **"delete all"** to confirm
4. Remind user to publish
### Example 2: Add Google Tag Manager
**User:** "Add GTM to my site"
1. `webflow_guide_tool` → `data_sites_tool` → ask for GTM container ID
2. Preview script, require "add" → `add_inline_site_script` (header, version "1.0.0")
3. Verify and remind to publish

## Constraints
### Example 3: Remove all scripts
**User:** "Remove all scripts"
1. `webflow_guide_tool` → `data_sites_tool` → list current scripts
2. Warn: removes ALL scripts. Require "delete all" → `delete_all_site_scripts`
3. Verify and remind to publish

- Max 10,000 characters per script
- Do NOT include `<script>` tags (Webflow adds them)
- displayName + version must be unique
- Site-level only (no page-specific via MCP)
- Hosted scripts not available via MCP
### Example 4: Page-specific tracking
**User:** "Add conversion tracking to my thank-you page"
1. `webflow_guide_tool` → `data_sites_tool` → `get_page_script` to check existing
2. Preview, require "update" → `upsert_page_script`
3. Verify and remind to publish

## Response Format
## Guidelines

After adding a script, respond with the script name, location, and version. Suggest using the `safe-publish` skill to publish changes.
- **`webflow_guide_tool` always first** — before any other MCP tool
- **No `<script>` tags** — Webflow adds them automatically
- **Max 10,000 characters** per script; `displayName` + `version` must be unique
- **Site-level** scripts (`add_inline_site_script`) apply to all pages; **page-level** scripts (`upsert_page_script`) apply to one page
- **No selective delete** — `delete_all_site_scripts` removes everything; always list scripts first so user knows what will be lost
- **Hosted/external scripts** not available via MCP — inline only
- Recommend **header** for analytics (GA, GTM); **footer** for chat widgets and non-critical scripts
- If `displayName + version` exists, suggest incrementing the version
- Always remind users to **publish** after changes
Loading