wesley dashboard builder

Requesting TELEGRAM_BOT_TOKEN and TELEGRAM_CHAT_ID is coherent with the skill's photo-upload and Telegram integration. However, the documentation also repeatedly references a specific VPS IP, container name, and workspace paths (72.62.30.28, openclaw-yyvg-...), which is unexpected for a generic dashboard-builder skill and suggests either embedded vendor-specific deployment steps or possibly instructions targeted at a particular remote environment.

SKILL.md includes operational commands that modify remote infrastructure: scp/ssh to [email protected], docker cp/exec, editing docker-compose.yml, creating cloudflared tunnels and writing credentials under /root/.cloudflared, and adding systemd/autostart scripts. Those instructions go well beyond generating HTML/CSS/JS and require high privileges on a host; they could be dangerous if you do not control the referenced VPS. The skill also instructs enabling permissive CORS (CORS(app, origins=['*'])) and installing packages with --break-system-packages — both high-impact ops that should be reviewed.

No install spec and no code files are present — the skill is instruction-only, which minimizes direct supply-chain risk (nothing is auto-downloaded or written by an installer). The security surface is therefore the instructions themselves rather than any bundled executable code.

The only required environment variables are TELEGRAM_BOT_TOKEN (primary) and TELEGRAM_CHAT_ID, which are proportionate to the stated Telegram upload/display functionality. Reminder: Telegram bot tokens grant broad control over the bot and should be treated as sensitive secrets; the skill's docs also suggest using that token to upload/receive media and to share links, which is consistent but sensitive.

While the skill itself is not marked always:true, its instructions explicitly direct creation of persistent services (auto-start scripts, docker-compose changes, cloudflared tunnels, and permanent credentials files under /root). That operational guidance asks the user to create persistent privileges on the target host and expose local services to the public internet — actions that carry significant security and persistence implications if performed against a host you do not own or fully control.