Warp Feature Flag Removal
warpdotdev/warp
Removes a Warp feature flag once it is stable for everyone, deleting the definition, the Cargo entries and every conditional check.
Declare, evaluate, manage, and remove framework feature flags.
No licenceAuto-check passed
Install Feature Flags
$ npx skills add BuilderIO/agent-native --skill feature-flags -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BuilderIO/agent-native feature-flags --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/BuilderIO/agent-native.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/feature-flags .claude/skills/feature-flags && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "feature-flags" agent skill from https://github.com/BuilderIO/agent-native/tree/main/.agents/skills/feature-flags into .claude/skills/feature-flags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/BuilderIO/agent-native/tree/main/.agents/skills/feature-flagsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add BuilderIO/agent-native --skill feature-flags -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BuilderIO/agent-native feature-flags --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/agent-native.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/feature-flags .agents/skills/feature-flags && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "feature-flags" agent skill from https://github.com/BuilderIO/agent-native/tree/main/.agents/skills/feature-flags into .agents/skills/feature-flags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BuilderIO/agent-native --skill feature-flags -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BuilderIO/agent-native feature-flags --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/agent-native.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/feature-flags .cursor/skills/feature-flags && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "feature-flags" agent skill from https://github.com/BuilderIO/agent-native/tree/main/.agents/skills/feature-flags into .cursor/skills/feature-flags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/BuilderIO/agent-native.git --path .agents/skills/feature-flags--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add BuilderIO/agent-native --skill feature-flags -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BuilderIO/agent-native feature-flags --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/agent-native.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/feature-flags .gemini/skills/feature-flags && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "feature-flags" agent skill from https://github.com/BuilderIO/agent-native/tree/main/.agents/skills/feature-flags into .gemini/skills/feature-flags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install BuilderIO/agent-native feature-flagsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add BuilderIO/agent-native --skill feature-flags -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BuilderIO/agent-native.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/feature-flags .github/skills/feature-flags && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "feature-flags" agent skill from https://github.com/BuilderIO/agent-native/tree/main/.agents/skills/feature-flags into .github/skills/feature-flags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BuilderIO/agent-native --skill feature-flags -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BuilderIO/agent-native feature-flags --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/agent-native.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/feature-flags .opencode/skills/feature-flags && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "feature-flags" agent skill from https://github.com/BuilderIO/agent-native/tree/main/.agents/skills/feature-flags into .opencode/skills/feature-flags/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-flags", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
feature-flags- GitHub stars
- 7.1k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 862 words
- Files
- 1
- Skills in repo
- 102
- Repo updated
- First seen
- Licence
- None found
At a glance
Declare, evaluate, manage, and remove framework feature flags.
- Works in 4 steps: Declare → Register → Guard server and client → …
- Shipping a capability gradually
- SKILL.md covers When to use one, Agent workflow, Management contract and Rollout semantics, plus 3 more sections
- Calls pnpm
What it does
Feature Flags is an agent skill from BuilderIO/agent-native. Declare, evaluate, manage, and remove framework feature flags. Use when shipping a capability gradually, targeting users or organizations, or replacing a compile-time rollout switch with a production-safe runtime flag.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: A framework for building agentic apps.
When your agent uses it
- Shipping a capability gradually
- Targeting users
- Replacing a compile-time rollout switch with a production-safe runtime flag
Example prompts
- “/feature-flags”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Declare
- Register
- Guard server and client
- Verify and roll out
What it can do on your machine
Read from SKILL.md and the folder at commit e16da0c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Feature Flags loads about 1.9k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 862 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 862 words (~1,859 tokens).
“A feature flag is a boolean declared in app code, evaluated locally by Core, and managed from the Analytics fleet control plane. Code owns whether a flag exists. Runtime settings own only its rollout state.”
- name
- feature-flags
- scope
- dev
- metadata.internal
- true
Files
Just SKILL.md in .agents/skills/feature-flags of BuilderIO/agent-native.
Open the folder on GitHubat commit e16da0c
Compare with similar skills
Feature Flags next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Feature Flags this skillBuilderIO/agent-native | 7.1k | — | ~1.9k | Automated safety check: Pass | None | |
| Warp Feature Flag Removalwarpdotdev/warp | 65k | 1 repos | ~1.1k | Automated safety check: Pass | AGPL-3.0 | |
| Remove Option Or Flaggetsentry/sentry | 46k | — | ~3k | Automated safety check: Pass | Custom licence | |
| Remove Feature Flagandroidx/androidx | 6.1k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Flagsvercel/next.js | 143k | — | ~746 | Automated safety check: Pass | MIT | |
| Arize Evaluatorgithub/awesome-copilot | 40k | 2 repos | ~8.1k | Automated safety check: Notes | MIT |
Similar skills
- Official
Remove Option Or Flag
getsentry/sentry
Remove a Sentry option or FlagPole feature flag whose rollout is finished, in the correct PR order across sentry, getsentry, and sentry-options-automator.
Remove Feature Flag
androidx/androidx
A skill your agent uses to remove a feature flag when the flag is no longer needed and its current state must be made permanent.
- Official
Flags
vercel/next.js
How to add or modify Next.js experimental feature flags end-to-end.
- Official
Arize Evaluator
github/awesome-copilot
Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and…
LLM Evaluation
davila7/claude-code-templates
Master comprehensive evaluation strategies for LLM applications, from automated metrics to human evaluation and A/B testing.
More from BuilderIO/agent-native
All 102 skills in this repoActions
BuilderIO/agent-native
How to create and run agent actions. An agent skill from BuilderIO/agent-native.
Client Methods
BuilderIO/agent-native
Client method surface rules. An agent skill from BuilderIO/agent-native.
Adding A Feature
BuilderIO/agent-native
The four-area checklist every new feature must complete. An agent skill from BuilderIO/agent-native.
Address Feedback
BuilderIO/agent-native
Triage feedback from docs, issues, Slack threads, or pasted notes into verified bugs, UX proposals, unclear questions, and skipped noise.
Audit Log
BuilderIO/agent-native
Durable, access-scoped, append-only record of who changed what app data, when, and whether it was the agent or a human.
Automations
BuilderIO/agent-native
Event-triggered and schedule-triggered automations with natural-language conditions.
Questions about Feature Flags
What does Feature Flags do?
Declare, evaluate, manage, and remove framework feature flags. Feature Flags is an agent skill from BuilderIO/agent-native. Declare, evaluate, manage, and remove framework feature flags.
When should I use Feature Flags?
Feature Flags fits situations like: shipping a capability gradually; targeting users; replacing a compile-time rollout switch with a production-safe runtime flag.
How do I install Feature Flags in Claude Code?
Run `npx skills add BuilderIO/agent-native --skill feature-flags -a claude-code`. Or copy the skill folder (.agents/skills/feature-flags in BuilderIO/agent-native) into .claude/skills/feature-flags in your project. Claude Code loads it when a task matches its description.
How do I install Feature Flags in Codex?
Run `npx skills add BuilderIO/agent-native --skill feature-flags -a codex`. Or copy the skill folder (.agents/skills/feature-flags in BuilderIO/agent-native) into .agents/skills/feature-flags in your project. Codex loads it when a task matches its description.
Can I use Feature Flags in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BuilderIO/agent-native --skill feature-flags -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feature-flags, .gemini/skills/feature-flags, .github/skills/feature-flags and .opencode/skills/feature-flags in your project.
What does Feature Flags need to run?
Going by SKILL.md and its folder, Feature Flags needs the command-line tools its instructions call (pnpm).
Does Feature Flags access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Feature Flags safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Feature Flags use?
No licence was found for Feature Flags or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Feature Flags use?
About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Feature Flags?
Skills that share tags, products or a category with Feature Flags: Warp Feature Flag Removal (warpdotdev/warp, 65k stars), Remove Option Or Flag (getsentry/sentry, 46k stars), Remove Feature Flag (androidx/androidx, 6.1k stars) and Flags (vercel/next.js, 143k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Feature Flags?
BuilderIO (a GitHub organization) maintains it in BuilderIO/agent-native, which has 7,087 GitHub stars. The repository holds 102 skills in this directory. The repository was last updated on October 8, 2026.
Source: BuilderIO/agent-native on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.