flags

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

1.03x

Quality

—

Does it follow best practices?

Impact

98%

1.03x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

100%

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

A compact, well-structured CLI skill: it provides an executable command, exact flag syntax, a channel legend, and targeted common-mistake guidance with no wasted tokens. It fits the rubric's simple-skill profile cleanly and scores strongly across all dimensions.

Dimension	Reasoning	Score
Conciseness	The body is lean and table/list-driven with no padding or explanation of concepts Claude already knows; every section (Options, Channels, Legend, Instructions, Common Mistakes) earns its place.	3 / 3
Actionability	It gives a concrete, copy-paste-ready command (`yarn flags $ARGUMENTS`) plus exact option syntax (`--diff <ch1> <ch2>`, `--cleanup`, `--csv`), matching the fully-executable anchor.	3 / 3
Workflow Clarity	A clear 3-step sequence (run, explain, highlight diffs) for a simple read-only task; per the simple-skills note, no validation checkpoint is required because the operation is non-destructive.	3 / 3
Progressive Disclosure	Under 50 lines with no need for external references, yet organized into clear, well-labeled sections — meeting the under-50-lines guidance for a top score with just good organization.	3 / 3
	Total	12 / 12 Passed

Description

85%

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

A well-constructed description with an explicit trigger clause, concrete actions, and a distinct niche. Its only weakness is trigger-term coverage, which centers on the core vocabulary but omits several common synonyms users may say.

Suggestions

Broaden trigger terms to include natural variations users might say, e.g. "experiments," "toggles," "rollouts," or "A/B tests," alongside "feature flags."

Consider adding a short noun-phrase prefix (e.g. "Inspect feature flags and release-channel behavior.") so the "what" reads as a capability statement before the "Use when" clause.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "check feature flag states, compare channels, or debug why a feature behaves differently across release channels" — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	The explicit "Use when..." clause supplies the "when" and the enumerated actions supply the "what," clearly answering both per the score-3 anchor.	3 / 3
Trigger Term Quality	Covers relevant natural terms ("feature flags," "compare channels," "debug") but misses common variations a user might say such as "experiments," "toggles," "rollout," or "A/B test," so it is not comprehensive.	2 / 3
Distinctiveness Conflict Risk	It carves a clear niche around feature flags and release channels with distinct triggers, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	11 / 12 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
Commit: e71a639

Reviewed: 4 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.