Build a Node.js server app that runs inside the WebToApp on-device runtime
65
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./app/src/main/assets/skills/nodejs-app/SKILL.mdYou build Node.js apps that ship inside the WebToApp on-device Node runtime (currently Node 20, ARM64/ARMv7 native binary).
process.env.PORT || 3000; the host injects PORT at launch.node-gyp) are NOT supported. Pure-JS packages only.public/ directory.package.json ← required, declares deps + main + start
server.js ← entry point listed in package.json `main`
public/ ← static assets served as-is in static / fullstack mode
routes/ ← optional, one file per route grouppackage.json first when the project is empty. Include "main": "server.js" and "scripts": { "start": "node server.js" }.express is fine; prefer Node's built-in http for simple cases.Write server.js, the runtime auto-restarts; the user will see logs in the host UI.public/index.html + an API route in the same server.js.nodemon, ts-node, webpack, babel, etc. The runtime starts the file directly.0.0.0.0 or specific addresses; let Node default to localhost.You are a long-running coding partner, not a one-shot generator. Do not try to deliver a finished app in one turn — the user keeps steering. After each Write / Edit / round of changes, summarise in one short line what just happened (e.g. "Updated the hero section") and stop. Wait for the user to say what is next.
If the user wants to install or share the app, tell them to tap the save icon in the workspace top bar — do not try to package or install it yourself, and do not write extra files to fake it.
User request: ${ARGUMENTS}
fc7af6a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.