feature-flags

Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.

1.66x

Quality

80%

Does it follow best practices?

Impact

98%

1.66x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/feature-flags/SKILL.md

Quality

Content

90%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, highly actionable reference with concrete code and commands, clear numbered workflows, and well-organized sections; the only minor gap is that validation checkpoints in the workflows are mostly implicit rather than called out explicitly.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout: a compact flag-file table, tight code examples, and no padding or explanation of concepts Claude already knows; every section earns its tokens.	5 / 5
Actionability	Provides copy-paste-ready code for both gating patterns (@gate pragma and inline gate()), concrete commands (/test www <pattern>, /flags --diff), and specific file paths for adding flags, covering the common cases.	5 / 5
Workflow Clarity	'Adding a New Flag' and 'Debugging Channel-Specific Failures' are clearly numbered sequences, with a verification step ('Verify flag exists in all fork files'), but validation checkpoints are otherwise mostly implicit rather than explicit.	4 / 5
Progressive Disclosure	Well-organized into clear headed sections with no bundle files to navigate, and appropriately signals the separate 'flags' skill for deeper command options; minor organization gaps keep it just below a 5.	4 / 5
	Total	18 / 20 Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has excellent, explicit trigger guidance and a distinct niche, but frames everything as 'when' clauses without an explicit statement of what the skill does, leaving 'what' only implied.

Suggestions

Lead with a concrete 'what' statement (e.g., 'Manage and debug React feature flags across channels') before the 'Use when...' triggers so the capability is explicit rather than inferred.

Add a couple more natural-term variations (e.g., 'gatekeeper', 'GK', 'flag rollout') to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Enumerates concrete trigger scenarios ('feature flag tests fail', 'flags need updating', 'understanding @gate pragmas', 'debugging channel-specific test failures', 'adding new flags') rather than abstract language, with only minor gaps in coverage.	4 / 5
Completeness	The description is entirely 'Use when...' trigger clauses with strong, explicit 'when' guidance, but the 'what' is only implied through the enumerated scenarios rather than stated as concrete actions.	3 / 5
Trigger Term Quality	Includes natural developer phrasing with synonyms and variations ('feature flag', 'flags', '@gate pragmas', 'channel-specific test failures'), though a few common variations are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (React feature flags, @gate pragmas, channel-specific failures) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: facebook/react
Path: .claude/skills/feature-flags/SKILL.md
Commit: eb8feb7

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.