Agent skill · software engineering · aradotso
openclaw-control-center
Local-first, security-first control center for OpenClaw agents — visibility dashboard with readonly defaults, token attribution, collaboration tracing, and safe write operations.
Why this skill is useful
Provides specific commands and configurations for managing OpenClaw agents that the AI wouldn't reliably generate on its own.
What it needs
Requires git, npm installed locally. About 6k tokens when loaded. Last updated 2026-07-09. 70 stars on the source repository.
What this skill does
openclaw-control-center Skill by ara.so — Daily 2026 Skills collection OpenClaw Control Center transforms OpenClaw from a black box into a local, auditable control center. It provides visibility into agent activity, token spend, task execution chains, cross-session collaboration, memory state, and document sources — with security-first defaults that keep all mutations off by default. What It Does Overview: System health, pending items, risk signals, and operational summary Usage: Daily/7d/30d token spend, quota, context pressure, subscription window Staff: Who is actively executing vs. queued — not just "has tasks" Collaboration: Parent-child session handoffs and verified cross-session messages (e.g. Main ⇄ Pandas) Tasks: Task board, approvals, execution chains, run evidence Memory: Per-agent memory health, searchability, and source file editing Documents: Shared and agent-core documents opened from actual source files Settings: Connector wiring status, security risk summary, update status Installation Open: http://127.0.0.1:4310/?section=overview&lang=zh http://127.0.0.1:4310/?section=overview&lang=en Use npm run dev:ui over UIMODE=true npm run dev — more stable, especially on Windows shells. Project Structure Critical constraint: Only modify files inside control-center/. Never modify ~/.openclaw/openclaw.json. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aradotso/openclaw-control-center