Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.
86
80%
Does it follow best practices?
Impact
98%
1.66xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/feature-flags/SKILL.mdNew flag registration across all channels
Flag in main file
100%
100%
Default value set
100%
100%
www fork file created
100%
100%
native-fb fork file created
100%
100%
test-renderer fork file created
100%
57%
__VARIANT__ in www fork
0%
100%
__VARIANT__ in native-fb fork
0%
100%
test-renderer not __VARIANT__
100%
100%
Flag name consistent
100%
100%
Fork files re-export main
87%
100%
All four files present
100%
100%
Correct @gate pragma vs gate() inline usage
@gate pragma used
0%
100%
@gate on unavailable-feature tests
0%
100%
gate() inline used
100%
100%
gate() on behavior-difference tests
100%
100%
Correct gate() syntax
100%
100%
No @gate on behavior-difference tests
100%
100%
3+ @gate tests
0%
100%
2+ inline gate() tests
100%
100%
No jest.skip substitution
100%
100%
Correct flag names in gating
57%
100%
Channel-specific failure debugging workflow
/flags --diff command
0%
100%
/test www command
72%
100%
__VARIANT__ double-test
0%
100%
Fork file completeness check
53%
100%
@gate condition check
81%
100%
__VARIANT__ explanation
0%
100%
/flags view step
0%
71%
Checklist file present
100%
100%
Structured steps
100%
100%
Concrete commands
100%
100%
705268d
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.