Vercel React Best Practices

v0.1.0

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.j...

0· 155·0 current·0 all-time
byMarcellus@iammarcellus
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description (React/Next.js performance guidance) match the provided content: a large set of rules and examples. The repository files are documentation and examples appropriate for an AI agent that helps write/refactor React/Next.js code.
Instruction Scope
SKILL.md and the included rule files are guidance for code-writing/refactoring and do not instruct the agent to read unrelated system files, access credentials, or send data to unexpected endpoints. The docs reference libraries and URLs (e.g., GitHub, Vercel docs) only as references.
Install Mechanism
No install spec and no code to install; the skill is instruction-only so nothing will be downloaded or executed on install.
Credentials
The skill declares no required environment variables, binaries, or config paths. There are references to third-party libraries in examples (e.g., better-all, swr) but no credentials or secret access are requested.
Persistence & Privilege
always: false and no special privileges requested. The skill does not request persistent system-level changes or access to other skills' configurations.
Assessment
This skill appears coherent and low-risk because it's documentation-only and requests no credentials or installs. Before using: (1) confirm the source—metadata lists 'vercel' but the registry source/homepage is unknown; verify you trust the author if you plan to treat it as an authoritative standard; (2) if you allow agents to perform automated refactors, require code backups and human review of changes (the skill's purpose is to guide code edits); (3) note the examples reference external libraries and patterns—ensure those dependencies and licensing fit your project. No technical red flags were found in the package contents.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ey781jfweaqcja3zwskzj25839hc0

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments