webflow-mcp:custom-code-management
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.
What this skill does
# Custom Code Management Add, review, and manage inline custom scripts on a Webflow site — analytics, tracking pixels, chat widgets, or any custom JavaScript. ## Important Note **ALWAYS use Webflow MCP tools for all operations:** - 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 ### 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 ### 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 ### 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 ### 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 ### 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 ## Guidelines - **`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
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.