ClawHub

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...

⭐ 4· 1k·2 current·2 all-time
byQuantyra@analsharqy
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
✓
Purpose & Capability
Name/description (Vercel React Best Practices) align with the provided files: a large, rule-based guide for React and Next.js performance. The skill requests no binaries, env vars, or installs, which is proportionate for a documentation/instruction-only skill.
ℹ
Instruction Scope
SKILL.md and AGENTS.md are guidance for writing/reviewing/refactoring code and are explicit about being optimized for agents/LLMs. The instructions do not request unrelated files, credentials, or external endpoints. Note: because the guidance is intended for automated refactoring, an agent using this skill could make code changes—users should plan to review diffs and run tests.
✓
Install Mechanism
No install spec and no code execution files — the skill is instruction-only (markdown files). This is low risk from an installation perspective (nothing is downloaded or written by an installer).
✓
Credentials
The skill declares no environment variables, credentials, or config paths and the content does not reference secrets. There is no disproportionate credential or environment access requested.
✓
Persistence & Privilege
Flags: always is false and user-invocable is true (normal). The skill can be invoked autonomously (platform default), which is expected for skills; there are no indicators it requests permanent elevated presence or modifies other skills.
Assessment
This skill is a large, instruction-only guide for optimizing React/Next.js performance and appears internally consistent. Before enabling it: 1) Verify the publisher/source if you need an official Vercel endorsement (the package metadata claims Vercel but 'Source' and 'Homepage' are absent). 2) If you allow autonomous agent refactors, require code-review (pull request or diff) and run your test suite/CI before merging changes. 3) Keep backups or branches before applying automated fixes. 4) If you prefer tighter control, only invoke the skill manually and avoid granting it any additional credentials. If you can confirm the origin (official Vercel repo or trusted mirror), confidence in the skill increases.

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

latestvk972sck4886mjzcddcxgdxdha9833w85

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments