ClawHub

Plugin UI Architecture

v1.0.1

Installs UI plugin architecture into OpenClaw, enabling plugins to register custom views, navigation items, and settings panels.

⭐ 0· 1.1k·2 current·2 all-time
by@maverick-software
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
The name/description (UI plugin architecture) align with the delivered artifacts: type additions, server gateway method, runtime registry, and client-side UI registry. No unrelated environment variables, binaries, or external services are requested.
ℹ
Instruction Scope
The SKILL.md and INSTALL_INSTRUCTIONS.md instruct editing many server and UI source files, adding gateway handlers, and loading the registry on client connect — this is expected for this feature. Minor inconsistency: SKILL.md references a skills path '~/clawd/skills/...' while INSTALL_INSTRUCTIONS.md uses '~/clawdbot' (likely a typo) which could confuse an automated installer. Installation requires write access to the codebase and restarting the gateway.
✓
Install Mechanism
This is an instruction-only skill with no install spec or remote downloads; nothing will be written by the skill itself unless you or your agent follow the manual steps. That lowers supply-chain risk.
✓
Credentials
No credentials, env vars, or config paths are requested. The only requirements are access to the OpenClaw source tree (~/clawdbot or $CLAWDBOT_DIR), pnpm, and the ability to restart the gateway — all proportionate to making the described code changes.
✓
Persistence & Privilege
The skill does not request always:true or autonomous privileges. The installation workflow requires persistent edits to the application source (expected for adding framework-level UI support) but the skill itself does not persist credentials or modify other skills' configs.
Assessment
This skill appears to do what it says: it adds types, server handlers, and a client-side registry so plugins can register UI tabs. Before installing: 1) Review/backup your repository (the steps change many files). 2) Test in a development environment and run the builds (pnpm build, pnpm ui:build) — the installer will need write and restart privileges. 3) Verify any security model around plugins: ensure only trusted plugins can call registerView/registerNavGroup (server-side registration attaches pluginId but review authorization controls). 4) Fix the small path typo ("~/clawd" vs "~/clawdbot") in automation. If you're comfortable making code changes and restarting the gateway, this skill is coherent with its purpose; otherwise have a developer apply the changes manually and review them in PR form.

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

latestvk9715y3kv6b9v95qe9em3htcsx80r6k4

License

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

Comments