Skip to content
TrustedSkillsbeta
Back to all skills

Feature Flags

Official
facebook·vlatest·other·MIT

Feature Flags enable controlled rollout & testing of new features, allowing for rapid iteration and risk mitigation without impacting all users.

Repository

Install on your platform

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

  1. 1

    Run this in your project

    terminal
    $ npx skills add react/react --skill feature-flags -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

facebook

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 facebook/react at d083ec1da1.

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

Commit
d083ec1da1
Manifest
.claude/skills/feature-flags/SKILL.md
Scanned
1 file, 74 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

The feature-flags skill enables developers to manage and control feature availability in applications using flags. It allows toggling features on or off dynamically without requiring code changes, enabling A/B testing, gradual rollouts, and conditional logic based on user segments or environments.

When to use it

  • You need to test a new feature with a subset of users before full deployment.
  • You want to enable or disable functionality based on user roles, regions, or device types.
  • You are implementing canary releases or need to roll out features gradually.

Key capabilities

  • Dynamic configuration of feature flags
  • Support for multiple environments (e.g., development, staging, production)
  • Integration with backend systems for centralized flag management

Example prompts

  • "Enable the dark mode feature for users in Europe only."
  • "Toggle off the experimental search algorithm for all users."
  • "Create a new feature flag to control access to the beta dashboard."

Tips & gotchas

  • Ensure your backend or configuration system is properly set up to manage flags securely.
  • Avoid overusing flags; they should be used strategically for features that require conditional behavior or testing.