SenseCraft HMI Web Content Generator
v1.0.0Generate beautiful web content for SenseCraft HMI e-ink displays. AI-powered layout selection, e-ink optimization. Creates artistic, minimalist pages optimiz...
⭐ 0· 265·0 current·0 all-time
byJack Shao@killingjacky
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (e-ink web content generator) matches the shipped files and runtime behavior: design references, layout templates, a configuration wizard, code to create a local project, and a local HTTP server that hosts generated HTML. Dependencies (Node/npm/express, pm2 optionally for process management) are reasonable for this purpose.
Instruction Scope
Runtime instructions are focused on reading the shipped reference docs, prompting the user for screen/layout choices, generating HTML into a local data directory, and serving it via a local HTTP server. The SKILL.md additionally instructs starting the server with pm2 and recommends exposing localhost through reverse-proxy/tunneling tools (ngrok, frp, cloudflare tunnel) — functionally coherent but increases blast radius because it tells the user to publish a local service to the public internet and embed a token in a URL.
Install Mechanism
There is no platform install spec (instruction-only), but the included init_project.js will run npm init and npm install express in the skill's data directory when invoked, and it writes a server.js file to disk. Using npm to fetch express is expected, but the script performs disk writes and spawns child processes (execSync). This is coherent with the skill's runtime needs but is higher-risk than a purely instruction-only skill because it creates files and pulls packages at runtime.
Credentials
The skill declares no required environment variables, credentials, or config paths. The runtime files operate only on files under the skill's baseDir/data and the shipped references; no unrelated cloud credentials or system tokens are requested.
Persistence & Privilege
always is false and autonomous invocation is allowed (normal). The skill instructs the user to run a long‑running local HTTP service (pm2 suggested) and to expose it via tunnels; that grants the skill the ability to host content persistently while pm2 is running, but it does not request system-wide config changes or modify other skills. Running a background server is within scope but increases persistence and exposure.
Assessment
This skill is coherent with its stated purpose, but take these precautions before using it:
- Review the server.js and wizard.js files locally (they are included) so you understand what will be written and served; the init script will create files under {baseDir}/data and run npm install express when invoked.
- The skill's workflow recommends exposing http://localhost:19527 (with a token query) to the public internet using tunnels (ngrok, frp, Cloudflare Tunnel). Exposing a local service has real risk: anyone who obtains the tokenized URL can view the page and any files you serve. Only publish if you understand and accept that exposure and rotate/regenerate tokens if needed.
- Prefer secure tunneling configuration: use authenticated tunnels, restrict origins where possible, and avoid forwarding ports that allow access to other local services. Do not use TCP tunnels that might expose other ports.
- The init script uses npm to install express and uses child_process.execSync; run these scripts in a controlled environment and inspect output before executing. If you do not want files created on disk, do not run init_project.js.
- The SKILL.md suggests using pm2 but does not install it — installing global process managers requires elevated privileges and should be done intentionally.
- If you intend to use any text-to-image model integration mentioned in the docs, confirm that your OpenClaw instance or environment is configured securely and that any generated images are stored only in the intended data/public/images/ directory.
- If you are unsure, run the skill in an isolated machine/container or review the code with someone who knows Node.js. If you want tighter security, avoid exposing the service publicly and use local previews only.Like a lobster shell, security has layers — review code before you run it.
latestvk970h0vsgvccsr954sqmye3w1982gdmq
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
