3-layer site launcher: tunnel any HTML instantly (no account), deploy to Cloudflare Pages (permanent), then buy a domain and link it via DNS. Use when a user...

This skill implements the tunnel → Pages → domain workflow, but it contains inconsistencies you should resolve before installing or supplying credentials. Key points to consider: - Do not provide unrelated credentials: package.json asks for a NETA_TOKEN (Neta AI) that the script never uses — do not supply that token unless the maintainer explains why it's needed. - Only provide Cloudflare tokens with least privilege: create custom API tokens scoped narrowly to Pages Edit and Zone DNS Edit for the specific account/zone, and prefer using per-action tokens instead of your global account key. - Expect the script to run system commands: it will call brew (to install cloudflared), npx (which downloads packages at runtime), wrangler, and cloudflared. Run in a trustworthy environment (or sandbox) if you are concerned about dynamic installs. - Ask the maintainer or reviewer to fix the manifest mismatch: the registry metadata and package.json should consistently declare required env vars; the skill should not request unrelated tokens. - Review the code yourself or have a trusted reviewer check it before pasting tokens into prompts. If you proceed, prefer manual invocation rather than granting autonomous agent invocation until the manifest inconsistencies are resolved.

Type: OpenClaw Skill Name: buy-domain-helper Version: 1.5.0 The skill contains a shell injection vulnerability in 'site.js' within the 'deploy' command, where the 'dir' and 'projectName' arguments are passed unsanitized to 'execSync'. Furthermore, 'package.json' requires a 'NETA_TOKEN' (for an unrelated AI service) that is never utilized in the code, which is a red flag for potential credential harvesting. The 'tunnel' command also performs an automatic 'brew install' of 'cloudflared', which is an intrusive side effect for a skill bundle.