OpenClaw Channel UI Assistant

Problem

Channel UI changes often fail on operational details: the wrong directory is guessed, dev and prod paths get mixed, production is overwritten without a backup, Nginx location blocks are duplicated, or the user receives a localhost or private network link that cannot be opened. This skill turns that workflow into a constrained process: identify the channel, apply changes in the test directory, and publish only after an explicit confirmation step.

Workflow

• Channel selection: after detecting intent such as creating a page or configuring UI, it lists available channels and menu levels without exposing server paths.
• Test-first edits: once a channel is chosen, changes are written only to that channel's dev directory, such as /data/dev/manage or /data/dev/tencent-cvm.
• Menu validation: for multi-level channels such as Tencent Cloud and Volcano Cloud, each menu level must have a real accessible link instead of # or javascript:void(0) placeholders.
• Header logo checks: it automatically verifies the header company logo path, the clickable container, and the redirect behavior, while preventing non-header icons from being replaced.
• Port 8080 preview: it only adds or updates the current channel location in /etc/nginx/conf.d/aipage.conf, runs nginx -t, and validates that the external test URL returns 200, 301, or 302.
• Controlled release: only after the release phrase and a second confirmation does it back up the production directory and then mirror the test directory fully, removing stale production files.

Boundaries

The skill only operates on mapped channels and whitelisted directories under /data. It does not allow path traversal or writes to unmapped paths. Without the explicit release trigger and confirmation, it must not modify production. If a public IPv4 address cannot be obtained, it should not emit a placeholder link; it should report the failure and ask for an accessible external address.