ClawHub

React Expert

v0.1.0

Use when building React 18+ applications requiring component architecture, hooks patterns, or state management. Invoke for Server Components, performance optimization, Suspense boundaries, React 19 features.

⭐ 4· 6.8k·52 current·54 all-time
byVeera@veeramanikandanr48
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/description (React 18+/19, Server Components, hooks, state mgmt) match the SKILL.md and the bundled reference documents. There are no unrelated required binaries, env vars, or config paths that would be unexpected for a React guidance skill.
✓
Instruction Scope
Runtime instructions are implementation-focused (analyze requirements, choose patterns, implement TypeScript components, optimize, test). The included reference examples show typical fetch/db examples for server components, but the skill does not instruct the agent to read local files, system configs, or to exfiltrate secrets. No vague 'gather whatever context you need' directives granting undue access.
✓
Install Mechanism
No install spec; instruction-only skills are lowest-risk as they write nothing to disk and install nothing automatically.
✓
Credentials
The skill requests no environment variables or credentials. Example server snippets reference db access and external fetches as normal illustrative code — these do not translate into required credentials being requested by the skill itself.
✓
Persistence & Privilege
Flags show always:false and normal autonomous invocation allowed. The skill does not request permanent presence or system-level changes; nothing indicates it will modify other skills or agent-wide settings.
Assessment
This appears to be a coherent, instruction-only React guidance skill. It neither installs code nor asks for credentials. When using it, treat suggested code like any external snippet: review network endpoints (example fetch URLs) before running, avoid pasting secrets into code, and only provide real backend credentials to code you control. If you plan to implement server-side examples, ensure database/API credentials remain in your secure environment (not pasted into chat) and audit any generated server-action code before deploying.

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

latestvk974tre43717c6qwqn9f61hp09808n80

License

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

Comments