CtrlK
BlogDocsLog inGet started
Tessl Logo

react-flow-architect

Build production-ready ReactFlow applications with hierarchical navigation, performance optimization, and advanced state management.

41

Quality

42%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/react-flow-architect/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

39%Scale 1-5

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

This skill provides a broad collection of ReactFlow patterns with concrete TypeScript code, but suffers from significant verbosity, lack of workflow structure, and monolithic organization. It reads more like a reference cookbook than an actionable skill, explaining many React patterns Claude already knows while missing key helper function implementations and any coherent build sequence.

Suggestions

Add a clear numbered workflow (e.g., 1. Set up basic graph → 2. Add tree navigation → 3. Optimize performance → 4. Add state management) with validation checkpoints at each stage.

Extract the GraphAnalyzer, auto-layout integration, and advanced features into separate referenced files to reduce the main skill to a concise overview with pointers.

Remove explanations of standard React patterns (memo, useCallback, useRef, reducer) and focus only on ReactFlow-specific guidance that Claude wouldn't already know.

Provide implementations for referenced helper functions (buildIncrementalUpdate, calculateBreadcrumbPath, generateLayoutCacheKey, applyDagreLayout) or remove references to them.

DimensionReasoningScore

Conciseness

The skill is significantly verbose at ~400+ lines. It explains many patterns Claude already knows (React memoization, useCallback, useRef, reducer patterns, Map for O(1) lookups). The 'Common Problems & Solutions' section restates what was already covered. The final two sentences and 'When to Use' section add zero value. The GraphAnalyzer class is largely filler with naive heuristics.

2 / 5

Actionability

The code examples are concrete, typed TypeScript/TSX, and mostly executable. However, several snippets reference undefined functions (buildIncrementalUpdate, buildFullGraph, areSetsEqual, calculateBreadcrumbPath, generateLayoutCacheKey, applyDagreLayout) without providing their implementations, creating gaps. The complete example at the end is a good anchor but still has missing helper functions.

4 / 5

Workflow Clarity

There is no clear sequenced workflow for building a ReactFlow application. The skill presents isolated patterns (tree navigation, performance, state management) without connecting them into a coherent build process. There are no validation checkpoints, no step-by-step instructions for integrating the patterns, and no guidance on order of operations or verification steps.

2 / 5

Progressive Disclosure

All content is inlined in a single monolithic file with no references to supporting files. The GraphAnalyzer script, detailed reducer patterns, layout integration, and focus mode code would all benefit from being in separate referenced files. There are no bundle files, and the skill makes no attempt to split content despite its length and breadth of topics.

2 / 5

Total

10

/

20

Passed

Description

45%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 identifies a specific technology (ReactFlow) but relies on abstract capability phrases rather than concrete actions. It completely lacks a 'Use when...' clause, making it harder for Claude to know when to select this skill. The trigger term coverage is narrow, missing many natural phrases users might use when requesting flow/graph-based UI work.

Suggestions

Add a 'Use when...' clause with trigger terms like 'flow diagram', 'node graph', 'workflow builder', 'react-flow', 'canvas editor', or 'drag-and-drop nodes'.

Replace abstract phrases like 'performance optimization' and 'advanced state management' with concrete actions such as 'create interactive node graphs', 'configure custom edge types', 'implement minimap and controls', 'manage node/edge state with Zustand'.

Include file extensions or library references users might mention, such as 'reactflow', '@xyflow/react', or '.tsx flow components'.

DimensionReasoningScore

Specificity

Names the domain (ReactFlow) and mentions a few capabilities ('hierarchical navigation', 'performance optimization', 'advanced state management'), but these are somewhat abstract rather than concrete actions. No specific verbs like 'create nodes', 'handle edge connections', or 'implement zoom/pan'.

3 / 5

Completeness

Provides a partial 'what' (build ReactFlow apps with certain features) but has no 'when' clause at all. Per the rubric, a missing 'Use when...' clause caps completeness at 3, and the 'what' itself is only moderately clear, placing this at a 2.

2 / 5

Trigger Term Quality

Includes 'ReactFlow' as a key trigger term, and 'production-ready' and 'state management' are somewhat natural. However, it misses common user terms like 'node graph', 'flow diagram', 'drag and drop nodes', 'react-flow', 'graph editor', 'workflow builder', or 'canvas'.

3 / 5

Distinctiveness Conflict Risk

ReactFlow is a specific library, which gives it a fairly distinct niche. However, terms like 'performance optimization' and 'advanced state management' are generic enough to potentially overlap with general React development skills. The ReactFlow specificity keeps it mostly distinct.

4 / 5

Total

12

/

20

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (620 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

9

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.