ClawHub

Ui Control Center

v1.0.0

Manage and maintain the local Agent Control UI with reliable caching, dashboards, tabs, and conflict-free server handling on port 8765.

⭐ 0· 1.2k·5 current·5 all-time
by@motivationationdaily
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the SKILL.md checklist: managing a local Agent Control UI, cache-busting, dashboard/tabs, and avoiding port conflicts on 8765.
ℹ
Instruction Scope
Instructions are narrowly scoped to UI maintenance and include sensible safety rails (bind to 127.0.0.1, avoid blocking event loop). However they are high-level (e.g., “ensure only one server listens on 8765”) and leave implementation choices open; depending on how the agent implements this it could require inspecting system sockets or killing processes — request concrete implementation details or limits before granting runtime privileges.
✓
Install Mechanism
No install spec and no code files — lowest risk from installation. Nothing will be downloaded or written by the skill itself as provided.
✓
Credentials
No environment variables, credentials, or config paths requested; access expectations are minimal and proportional to the stated local UI task.
✓
Persistence & Privilege
Skill is not always-enabled and remains user-invocable. It does not request system-wide configuration changes or permanent presence.
Assessment
This skill is coherent and low-risk as written, but it is only a set of runtime instructions — there is no implementation included. Before installing or allowing autonomous execution, ask for the actual code or implementation plan and confirm: (1) port-conflict handling will not kill unrelated processes or exfiltrate data, (2) the server truly binds to 127.0.0.1, and (3) logs/audit data remain local or are handled per your policy. If you plan to let an agent act on these instructions autonomously, require explicit, limited implementations for any system-level checks (e.g., only probe the specific port, do not run broad process inspectors) and review them first.

Like a lobster shell, security has layers — review code before you run it.

latestvk978ayv81xjnd4mqg6xjc3tw2x8215sm

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments