Checks and compares feature flag configurations. Helps debug environmental differences and cleanup tasks.
Install
mkdir -p .claude/skills/flags && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/610" && unzip -o skill.zip -d .claude/skills/flags && rm skill.zipInstalls to .claude/skills/flags
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.Key capabilities
- →List feature flag states across environments
- →Compare flag configurations between release channels
- →Identify flags requiring cleanup
- →Output flag data in CSV format
How it works
It queries the feature flag system for specific channels and compares the enabled/disabled status of flags to highlight discrepancies.
Inputs & outputs
When to use flags
- →Checking current flag states
- →Comparing flags between two channels
- →Debugging environment-specific behavior
- →Auditing flags for cleanup
About this skill
Feature Flags
Arguments:
- $ARGUMENTS: Optional flags
Options
| Option | Purpose |
|---|---|
| (none) | Show all flags across all channels |
--diff <ch1> <ch2> | Compare flags between channels |
--cleanup | Show flags grouped by cleanup status |
--csv | Output in CSV format |
Channels
www,www-modern- Meta internalcanary,next,experimental- OSS channelsrn,rn-fb,rn-next- React Native
Legend
✅ enabled, ❌ disabled, 🧪 __VARIANT__, 📊 profiling-only
Instructions
- Run
yarn flags $ARGUMENTS - Explain the output to the user
- For --diff, highlight meaningful differences
Common Mistakes
- Forgetting
__VARIANT__flags - These are tested both ways in www; check both variants - Comparing wrong channels - Use
--diffto see exact differences
When not to use it
- →Modifying flag states directly
- →Debugging non-flag related environment issues
Prerequisites
Limitations
- →Limited to existing flag metadata
- →Requires knowledge of channel naming conventions
How it compares
It provides a structured comparison tool rather than requiring manual inspection of individual environment configurations.
Compared to similar skills
flags side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| flags (this skill) | 5 | 6mo | No flags | Beginner |
| axiom-ios-build | 3 | 1mo | No flags | Advanced |
| vercel-advanced-troubleshooting | 3 | 27d | Caution | Advanced |
| vercel-debug-bundle | 3 | 27d | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by facebook
View all by facebook →You might also like
axiom-ios-build
CharlesWiltgen
Use when ANY iOS build fails, test crashes, Xcode misbehaves, or environment issue occurs before debugging code. Covers build failures, compilation errors, dependency conflicts, simulator problems, environment-first diagnostics.
vercel-advanced-troubleshooting
jeremylongshore
Execute apply Vercel advanced debugging techniques for hard-to-diagnose issues. Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles for Vercel support escalation. Trigger with phrases like "vercel hard bug", "vercel mystery error", "vercel impossible to debug", "difficult vercel issue", "vercel deep debug".
vercel-debug-bundle
jeremylongshore
Execute collect Vercel debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Vercel problems. Trigger with phrases like "vercel debug", "vercel support bundle", "collect vercel logs", "vercel diagnostic".
stac-troubleshooter
StacDev
Diagnose Stac build, deploy, rendering, caching, and navigation issues using repeatable checks. Use when users report stac build finding no screens, deploy mismatches, runtime unknown widget/action errors, cache staleness, or migration regressions.
replit-incident-runbook
jeremylongshore
Execute Replit incident response procedures with triage, mitigation, and postmortem. Use when responding to Replit-related outages, investigating errors, or running post-incident reviews for Replit integration failures. Trigger with phrases like "replit incident", "replit outage", "replit down", "replit on-call", "replit emergency", "replit broken".
electron-pro
jshsakura
Use when a task needs Electron-specific implementation or debugging across main/renderer/preload boundaries, packaging, and desktop runtime behavior.