flow

Use when you need to run Flow type checking, or when seeing Flow type errors in React code.

1.72x

Quality

—

Does it follow best practices?

Impact

100%

1.72x

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.

This is a tight, well-organized single-purpose skill: lean prose, executable commands, a clear sequence, and clean sectioning. It respects token budget while remaining fully actionable.

Dimension	Reasoning	Score
Conciseness	The body is lean with a renderers table, numbered steps, and a short common-mistakes list, adding only what Claude doesn't already know.	3 / 3
Actionability	It gives copy-paste-ready commands (`yarn flow $ARGUMENTS`, `yarn flow-ci`) with a sensible default fallback, fully executable guidance.	3 / 3
Workflow Clarity	A clear numbered 3-step sequence for a simple, non-destructive type-checking task; the destructive/batch validation cap does not apply here.	3 / 3
Progressive Disclosure	Under 50 lines with no need for external references, it is well-organized into labeled sections (Renderers, Instructions, Common Mistakes).	3 / 3
	Total	12 / 12 Passed

Description

90%

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 is concise, uses an explicit trigger clause, and targets a clear niche with natural user phrasing. Its only weakness is that it lists relatively few concrete actions, capping specificity at 2.

Suggestions

Add a couple more concrete actions (e.g., "fix type errors", "review suppressions") to lift specificity toward 3.

Consider mentioning the available renderers or the `yarn flow-ci` comprehensive mode to better signal the skill's full capability set.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple of actions ("run Flow type checking", "seeing Flow type errors") but does not enumerate a comprehensive list of concrete actions, matching the level-2 anchor.	2 / 3
Completeness	It states what the skill does ("run Flow type checking") and gives an explicit "Use when..." trigger, clearly answering both what and when.	3 / 3
Trigger Term Quality	Phrases like "Flow type checking", "Flow type errors", and "React code" are natural terms a user would actually say when needing this skill, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Flow is a specific niche with distinct triggers tied to a named tool, 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.