← Back to Skills Marketplace
836
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install clawctl
Description
Coordination layer for OpenClaw agent fleets (tasks, messaging, activity feed, dashboard).
README (SKILL.md)
Setup
clawctl init # create the database
export CLAW_AGENT=your-name # set identity (falls back to $USER with warning)
export CLAW_DB=~/.openclaw/clawctl.db # optional, this is the default
Operational Rhythm
Follow this pattern every session:
clawctl checkin— register presence, see unread countclawctl inbox --unread— read messages before picking up workclawctl next— find highest-priority actionable task (orclawctl list --mine)clawctl claim \x3Cid>thenclawctl start \x3Cid>— take ownership and beginclawctl msg \x3Cagent> "update" --task \x3Cid>— coordinate during workclawctl done \x3Cid> -m "what I did"thenclawctl next— complete and move on
Only claim tasks assigned to you or matching your role. Completing an already-done task is a safe no-op.
Decision Tree
| Situation | Command |
|---|---|
| New task | clawctl add "Subject" -d "Details" |
| Find work | clawctl next then clawctl claim \x3Cid> |
| Blocked | clawctl block \x3Cid> --by \x3Cblocker-id> and notify via clawctl msg |
| Finished | clawctl done \x3Cid> -m "Result" |
| Hand off | clawctl msg \x3Cagent> "Ready for you" --task \x3Cid> --type handoff |
| Ready for review | clawctl review \x3Cid> |
| Catch up | clawctl feed --last 20 or clawctl summary |
| Link artifacts | Add --meta '{"note":"path/to/file"}' to done, claim, start, or block |
Task Statuses
pending → claimed → in_progress → done
↘ blocked ↗ ↘ cancelled
↘ review ↗
list excludes done/cancelled by default. Use --all for history (newest first).
Commands
Tasks
| Command | Description |
|---|---|
add SUBJECT |
Create task. -d desc, -p 0|1|2 priority, --for AGENT assign, --parent ID |
list |
Active tasks. --mine, --status STATUS, --owner AGENT, --all |
next |
Highest-priority actionable task for current agent |
claim ID |
Claim task. --force overrides ownership, --meta JSON |
start ID |
Begin work (in_progress). --meta JSON |
done ID |
Complete. -m note, --force, --meta JSON |
review ID |
Mark ready for review. --meta JSON |
cancel ID |
Cancel task. --meta JSON |
block ID --by OTHER |
Mark blocked. --meta JSON |
board |
Kanban board grouped by status |
Messages
| Command | Description |
|---|---|
msg AGENT BODY |
Send message. --task ID, --type TYPE (comment, status, handoff, question, answer, alert) |
broadcast BODY |
Alert all agents |
inbox |
Read messages. --unread for unread only |
Fleet
| Command | Description |
|---|---|
checkin |
Heartbeat — update presence, report unread count |
register NAME |
Register agent. --role TEXT |
fleet |
All agents with status and current task |
whoami |
Identity, role, and DB path |
Monitoring
| Command | Description |
|---|---|
feed |
Activity log. --last N, --agent NAME, --meta |
summary |
Fleet overview with counts and recent events |
dashboard |
Web UI. --port INT, --stop, --verbose |
Usage Guidance
This skill appears to be what it says: a local coordination CLI + optional Flask dashboard backed by SQLite. Before installing or running it, consider the following:
- Install method: the registry metadata omits an install step even though a Python package (pyproject.toml) is included. You should install into a virtualenv (pip install . or pip install -e . for development) rather than running unknown files globally.
- Database safety: run initial tests with a temporary DB to avoid touching your real data (example: CLAW_DB=/tmp/test.db clawctl init). The README/CLAUDE.md recommend this.
- Dashboard token and exposure: the dashboard writes a persistent token to ~/.openclaw/.clawctl-token and, by default, binds to 0.0.0.0. If you run the dashboard on a multi-user or public-facing host, ensure the token file is protected (filesystem permissions) and the port is not publicly accessible, or bind to localhost instead.
- Environment vars: the code reads CLAW_AGENT and CLAW_DB (with sensible defaults). The skill metadata did not declare these env vars — be aware they influence behavior and identity fallback to $USER will occur with a one-time warning.
- Review the code if you need stricter guarantees: SQL is parameterized and DB access patterns look race-aware; there are no obvious network calls to external services or obfuscated code. If you require tighter isolation, run inside a container or VM and use a temp DB.
If you want, I can extract the full list of CLI commands or point out exact lines where the dashboard writes the token and binds to the network so you can audit or modify them before use.
Capability Analysis
Type: OpenClaw Skill
Name: clawctl
Version: 0.1.0
The OpenClaw AgentSkills skill bundle 'clawctl' is a coordination layer for agent fleets, utilizing a local SQLite database and an optional Flask web dashboard. The code demonstrates strong security practices, including parameterized SQL queries in `clawctl/db.py` to prevent SQL injection, HTML escaping in `dashboard/index.html` to mitigate XSS, and controlled execution of the dashboard server via `subprocess.Popen` in `clawctl/cli.py` with fixed arguments. Data is stored locally in user-owned directories (`~/.openclaw/clawctl.db`, `~/.openclaw/.clawctl-token`), and there is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts against the agent. All functionalities are aligned with the stated purpose of a local coordination tool.
Capability Assessment
Purpose & Capability
Name/description match the code and SKILL.md: CLI (clawctl), DB layer, and Flask dashboard implement task board, messaging, activity feed, and a web UI. The declared required binary (clawctl) is appropriate. Minor inconsistency: registry/install metadata treats this as instruction-only, but the package source (pyproject, Python package files) is included — not dangerous but the packaging/installation story is unclear.
Instruction Scope
SKILL.md instructs running clawctl CLI commands and setting CLAW_AGENT/CLAW_DB; runtime instructions stay within the coordination/dashboard scope. Commands allow including JSON metadata that may reference local file paths (e.g. --meta '{"note":"path/to/file"}'), but the skill does not instruct the agent to read arbitrary system files or exfiltrate data. Dashboard persists a token file under ~/.openclaw/.clawctl-token — expected for local web UI auth.
Install Mechanism
No network install or remote download specs are present; source includes a standard pyproject.toml with only Click and Flask dependencies. This is low risk compared with remote fetch installs. The absence of an install spec means users must install the package (pip) or otherwise provide the clawctl binary.
Credentials
The skill does not request any external credentials and uses only CLAW_AGENT and CLAW_DB (both optional; defaults exist). Those env vars are referenced throughout the code and SKILL.md but are not listed in requires.env metadata — this mismatch is minor but worth documenting. No unrelated secrets or cloud credentials are requested.
Persistence & Privilege
always:false and no skill-wide privileged flags are used. The dashboard creates and persists a local token file at ~/.openclaw/.clawctl-token and runs a Flask server bound to 0.0.0.0 by default (intended for LAN/Tailscale access). That network exposure is expected for a dashboard but requires the user to be careful about where they run it and who can access the token file or the listening port.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install clawctl - After installation, invoke the skill by name or use
/clawctl - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release of clawctl: coordination tool for OpenClaw agent fleets.
- Provides task management (add, claim, start, complete, block, review, cancel).
- Built-in messaging between agents, including inbox, broadcast, and task-specific messages.
- Fleet operations: agent registration, presence check-in, whoami, and live dashboard.
- Activity monitoring with feed, summary, and board views.
- Simple operational rhythm and command decision tree for efficient workflow.
Metadata
Frequently Asked Questions
What is Clawctl?
Coordination layer for OpenClaw agent fleets (tasks, messaging, activity feed, dashboard). It is an AI Agent Skill for Claude Code / OpenClaw, with 836 downloads so far.
How do I install Clawctl?
Run "/install clawctl" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Clawctl free?
Yes, Clawctl is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Clawctl support?
Clawctl is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Clawctl?
It is built and maintained by lludlow (@lludlow); the current version is v0.1.0.
More Skills