Skip to content
TrustedSkillsbeta
Back to all skills

Flowkit Naming

Official
webflow·vlatest·other·MIT

Generates creative website section names using Flowkit’s AI, streamlining content organization and boosting design efficiency.

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:flowkit-naming, 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:flowkit-naming -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.

Scanned
1 file, 868 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 generate consistent, unique names for FlowKit resources and configurations. It ensures that generated identifiers adhere to specific naming conventions required by Webflow's development ecosystem.

When to use it

  • Creating new FlowKit projects or components where resource uniqueness is critical.
  • Automating the setup of multiple related workflows that require distinct, readable identifiers.
  • Integrating AI-generated code into existing Webflow environments to prevent naming collisions.
  • Standardizing output across different agents interacting with the same FlowKit instance.

Key capabilities

  • Generates unique names for FlowKit resources automatically.
  • Enforces consistent naming conventions within generated configurations.
  • Prevents identifier conflicts in complex or scaled project structures.

Example prompts

  • "Generate a unique name for a new FlowKit workflow component following standard Webflow conventions."
  • "Create a set of distinct identifiers for five related automation tasks I'm building in FlowKit."
  • "Suggest a naming scheme for my FlowKit resources that ensures clarity and avoids collisions with existing assets."

Tips & gotchas

Ensure the AI agent has access to your current project context to avoid generating names that already exist. While this skill handles uniqueness, manually reviewing generated names is recommended for complex projects to maintain semantic clarity.