Frontend Builder
v1.0.0Generates production-ready React TSX frontend components from natural-language UI goals for non-programmers, including setup instructions and dependencies.
⭐ 0· 576·1 current·1 all-time
byHagen Hoferichter@h4gen
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description ask for React TSX components; declared requirements (node, npm, npx) and the instructions to install frontend-design-ultimate, shadcn-ui, and react-expert via npx are coherent with that purpose. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
SKILL.md focuses on collecting UI inputs, orchestrating three upstream skills, and producing a single TSX output plus setup instructions. It does not instruct reading arbitrary host files, secrets, or system state beyond expecting a React/TS/Tailwind project and running installation commands when needed.
Install Mechanism
The skill is instruction-only (no install spec). It instructs using npx -y clawhub@latest install ... and npx shadcn@latest init/add which will download and run code from npm at install time. This is expected for a meta-skill that composes other skills, but users should be aware these commands fetch third-party packages and may modify project files.
Credentials
No environment variables or credentials are requested. The required tools (node, npm, npx) are appropriate and proportional to a tool that generates and installs frontend code.
Persistence & Privilege
always is false and the skill does not request permanent agent presence or elevated privileges. The SKILL.md does instruct running install commands that modify the local project, which is expected behavior and limited in scope to the user's workspace.
Assessment
This skill appears internally consistent with its stated purpose. Before installing or running its suggested commands: 1) verify you trust the 'clawhub' npm package and the upstream skills it will fetch (they will be downloaded and executed via npx); 2) run install/init commands in a sandboxed or version-controlled project (shadcn init/add and other installers can modify files); 3) review any generated TSX and dependency commands before applying to production (check licenses and third-party package versions); 4) if you prefer not to let the agent run installers automatically, decline those steps and run them manually after inspection. Confidence is high because the skill is instruction-only and requests only appropriate tools, but running its install commands will pull third-party code so exercise normal supply-chain caution.Like a lobster shell, security has layers — review code before you run it.
latestvk97b859ma28snxamw0wr9ewvss815k1b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🧩 Clawdis
Binsnode, npm, npx