Skip to content
TrustedSkillsbeta
Back to all skills

Flags

Official
vercel·vlatest·cloud·MIT

Manage and dynamically control feature releases and experiments across your Vercel deployments using flags.

Repository

Install on your platform

This skill no longer installs under the name flags. SKILL.md is marked internal, so the skills CLI hides it.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

vercel

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 vercel/next.js at e7feae7d53.

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

Commit
e7feae7d53
Manifest
.agents/skills/flags/SKILL.md
Scanned
1 file, 46 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

The vercel-flags skill enables AI agents to manage feature toggles directly within Vercel projects, allowing for dynamic control over application behavior without redeploying code. It integrates with Next.js environments to switch features on or off based on specific conditions like user segments or environment settings.

When to use it

  • Roll out new UI components to a subset of users before a global launch.
  • Disable experimental backend logic during peak traffic hours to ensure stability.
  • Toggle A/B test variations instantly without waiting for a build pipeline.
  • Revert a specific feature immediately if a critical bug is detected in production.

Key capabilities

  • Create and manage feature flags via the Vercel dashboard or API.
  • Define targeting rules to show features to specific users, roles, or environments.
  • Integrate seamlessly with Next.js applications for real-time flag evaluation.
  • View flag status and usage analytics within the project overview.

Example prompts

  • "Create a new feature flag named 'dark-mode-beta' that is enabled only for users in the staging environment."
  • "Update the 'new-checkout-flow' flag to target 10% of all active users globally."
  • "Disable the 'experimental-api-endpoint' flag immediately due to reported latency issues."

Tips & gotchas

Ensure your Vercel project has the necessary permissions to modify feature flags before attempting automation. While this skill manages toggles, it does not replace the need for robust code logic that checks these flags within your application source files.