flow
Use when you need to run Flow type checking, or when seeing Flow type errors in React code.
72
56%
Does it follow best practices?
Impact
100%
1.72xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/flow/SKILL.mdQuality
Discovery
40%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 provides a reasonable 'when to use' trigger but is very weak on describing what the skill actually does. It reads more like a trigger condition than a complete skill description, lacking specific capabilities and actions. The Flow-specific terminology helps with distinctiveness but the overall description is too thin to effectively guide skill selection.
Suggestions
Add specific capabilities the skill provides, e.g., 'Runs Flow type checker, diagnoses and fixes Flow type annotations, configures .flowconfig, and resolves type mismatches in React components.'
Expand trigger terms to include common variations like '.flowconfig', '@flow pragma', 'flow-typed', 'static type checking', and specific file extensions.
Strengthen the 'what' portion by listing 2-4 concrete actions the skill performs beyond just 'running' type checking.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'run Flow type checking' which is a single vague action, and 'seeing Flow type errors' which describes a condition rather than a concrete capability. It doesn't list specific actions like 'configure Flow, fix type annotations, resolve type mismatches, add type definitions'. | 1 / 3 |
Completeness | It has a 'Use when...' clause which addresses the 'when' question reasonably well, but the 'what does this do' part is very weak — it only implies running type checking without describing what the skill actually does or what capabilities it provides. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Flow', 'type checking', 'type errors', and 'React code' which users might naturally mention. However, it misses variations like 'flow-typed', '.flowconfig', 'type annotations', '@flow', or 'static typing'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Flow' specifically distinguishes it from TypeScript or other type systems, but 'React code' and 'type errors' are broad enough that it could overlap with general React debugging or TypeScript skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise and well-structured skill that efficiently communicates the essentials of running Flow type checking. Its main weakness is the lack of concrete examples of error output and fix workflows, which would make it more actionable. The common mistakes section identifies issues but doesn't provide executable solutions.
Suggestions
Add an example of typical Flow error output and how to interpret/fix it (e.g., a missing type import with the fix)
Add an explicit feedback loop: run flow -> see errors -> fix -> re-run until clean
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every token earns its place. No unnecessary explanations of what Flow is or how type checking works. The table format for renderers is efficient and scannable. | 3 / 3 |
Actionability | Provides the concrete command (`yarn flow $ARGUMENTS`) but lacks example output of type errors or specific examples of how to fix common issues. The common mistakes section describes problems but doesn't show concrete fixes. | 2 / 3 |
Workflow Clarity | Steps are listed but there's no validation/feedback loop for handling errors. For a type-checking workflow, it would benefit from explicit guidance on what to do when errors are found (fix -> re-run cycle) rather than just 'report type errors with file locations'. | 2 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines. The content is well-organized with clear sections (renderers table, instructions, common mistakes) and doesn't need external references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- facebook/react
- Commit
705268d
- Reviewed
Table of Contents
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.