React Flow Code Review
v1.1.0Reviews React Flow code for anti-patterns, performance issues, and best practices. Use when reviewing code that uses @xyflow/react, checking for common mista...
⭐ 0· 63·0 current·0 all-time
byKevin Anderson@anderskev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the SKILL.md content: it provides manual review guidance for @xyflow/react-based code. There are no unrelated requirements (no credentials, no binaries) that would be inconsistent with a code-review helper.
Instruction Scope
SKILL.md contains static guidance, examples, and a checklist for reviewing React Flow code. It does not instruct the agent to read system files, access environment variables, call external endpoints, or perform actions outside the scope of reviewing code snippets. It is descriptive rather than prescriptive (no commands or automated code execution).
Install Mechanism
No install spec is present. This is lowest-risk: nothing is downloaded or written to disk as part of installation.
Credentials
The skill requests no environment variables, credentials, or config paths — appropriate for a documentation/instruction-only code review helper.
Persistence & Privilege
always is false and there are no indications the skill requests persistent presence or modifies other skills/config. Autonomous invocation is allowed by platform default but the skill does not request elevated privileges.
Assessment
This skill is an instruction-only checklist for reviewing React Flow code and appears internally consistent and low-risk. Before installing, note: (1) it provides manual review advice, not automated linting or code changes — you still should run your own linters/tests; (2) it references the package name '@xyflow/react' and specific APIs (Position, useReactFlow, updateNodeData) — confirm these match the library/version you use; (3) because it’s just documentation, it does not require credentials or access to your environment. If you need automated enforcement, prefer a tool that runs local, audited linters or unit tests rather than relying solely on prose guidance.Like a lobster shell, security has layers — review code before you run it.
latestvk979xj1776vw0781a17ns371f983qc7t
License
MIT-0
Free to use, modify, and redistribute. No attribution required.