Skip to content
TrustedSkillsbeta
Back to all skills

Custom Code Management

Official
webflow·vlatest·agents·MIT

Automate Webflow code deployments, version control, and conflict resolution using custom scripts and integrations.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Installs under a different name. Its SKILL.md names it webflow-mcp:custom-code-management, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add webflow/webflow-skills --skill webflow-mcp:custom-code-management -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

webflow

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned webflow/webflow-skills at c8a1650d40.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
c8a1650d40
Manifest
plugins/webflow-skills/skills/custom-code-management/SKILL.md
Scanned
1 file, 88 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to automate Webflow code deployments, manage custom inline scripts (like analytics trackers or chat widgets), and handle version control within a Webflow site. It leverages Webflow's Model Context Protocol (MCP) tools for all operations, ensuring best practices are followed and providing structured access to script management functions. The skill facilitates adding, reviewing, and updating these scripts across the entire website or specific pages.

When to use it

  • You need to add a tracking pixel or analytics code to your Webflow site.
  • You want to review the existing custom scripts on your Webflow site.
  • You need to update an existing inline script with a new version or modified code.
  • You require a way to remove all custom scripts from your entire Webflow website (use with caution).
  • You want to retrieve the custom code currently applied to a specific page on your Webflow site.

Key capabilities

  • Script Listing: Lists registered and applied inline scripts across the Webflow site.
  • Page Script Retrieval: Retrieves custom code associated with individual pages.
  • Script Addition: Registers new inline scripts, specifying display name, source code, version, location (header/footer), and copy status.
  • Script Updating: Adds or updates page-level custom code.
  • Script Removal: Removes all site scripts (no selective deletion).
  • Guided Workflow: Requires the use of webflow_guide_tool for best practices, followed by specific data tools to manage scripts.
  • Confirmation Steps: Requires explicit user confirmation ("add", "delete all", or "update") before making changes.

Example prompts

  • "What scripts are currently registered on my Webflow site?"
  • "Add Google Tag Manager code to my website."
  • "Show me the custom code for the homepage of my Webflow site."

Tips & gotchas

  • MCP Dependency: All operations must be performed using the specified Webflow MCP tools. Always start with webflow_guide_tool.
  • No Selective Deletion: The skill currently only supports removing all scripts from a site at once; selective deletion is not possible.
  • Context Parameter Required: All tool calls require a context parameter (approximately 15-25 words) describing the action being performed in third person.