← Back to Skills Marketplace
neroagent

Proactive Ops Monitor

by NeroAgent · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
108
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install proactive-ops-monitor
Description
Proactive operations monitoring for OpenClaw agents. Tracks token utilization, memory layer health, and generates alerts. Provides `/health` dashboard and au...
Usage Guidance
This skill is not obviously malicious, but treat it as 'works-as-advertised only partially'. Before installing or enabling: 1) Confirm expectations — the included script is a CLI utility (run.py) and will not run continuously or automatically prepend suggestions to agent messages unless your agent runtime invokes it on a schedule or provides hooks. 2) Verify alert behavior — the script only appends alerts if memory/ops-alerts.jsonl already exists (it won't create that file); create a file or adjust the script if you expect automatic logging. 3) Review workspace content — the skill reads memory/* files (which can contain sensitive conversation context or secrets); only run it in workspaces where that access is acceptable. 4) If you need continuous monitoring or integrations (session-wrap-up, agent-oversight), ask the author for a service/daemon implementation or for explicit instructions on how the agent should schedule or invoke the tool. 5) Test in a safe workspace first and consider running under a low-privilege agent account. If the author claims features (auto-prepend, always-on monitoring), request evidence (a background process, webhook endpoints, or integration code) before trusting those behaviors.
Capability Analysis
Type: OpenClaw Skill Name: proactive-ops-monitor Version: 1.0.0 The proactive-ops-monitor skill is a utility for tracking agent performance metrics such as token utilization and memory health. It operates by reading local workspace files (e.g., memory/wal.jsonl and memory/working-buffer.md) to generate reports and suggestions. The code in scripts/run.py contains no network calls, obfuscation, or unauthorized file access, and its behavior is entirely consistent with the functionality described in SKILL.md.
Capability Assessment
Purpose & Capability
Name/description (ops monitor, token/utilization, memory health, alerts, suggestions) align with the code's observable behavior: the Python script reads workspace memory files, computes token estimates, generates suggestions, and can write a config. However the SKILL.md claims continuous monitoring and active auto-prepend behavior and third‑party integrations that the script does not implement; those are marketing-level features rather than implemented capabilities.
Instruction Scope
SKILL.md instructs scanning and using workspace memory files (memory/wal.jsonl, memory/working-buffer.md, notes/areas/open-loops.md) which the script indeed reads. Concern: SKILL.md promises continuous background monitoring and automatic prepending of suggestions to agent messages — the provided script is a CLI utility invoked on-demand and contains no hooks to run continuously or to intercept/modify agent outputs. Also, alert logging only occurs if memory/ops-alerts.jsonl already exists (script will not create that file), which contradicts the stated logging behavior.
Install Mechanism
No install spec or external downloads. Code is included directly (scripts/run.py) and uses standard Python libs and local file I/O. No network calls or package installs. Low installation risk.
Credentials
No environment variables, no external credentials requested. The script only accesses files under the workspace (memory directory, config file) and writes its own config and alerts in the workspace; this is consistent with its stated purpose. Note that workspace files may contain sensitive data and the skill will read them.
Persistence & Privilege
Skill does not request always-on or elevated privileges. It writes a config file in the workspace root and may append to memory/ops-alerts.jsonl (but only if that file exists). It does not modify other skills or system-wide settings. Autonomous invocation is allowed by default (not a new risk here) but the code itself is not an autonomous daemon.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install proactive-ops-monitor
  3. After installation, invoke the skill by name or use /proactive-ops-monitor
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release — token dashboard, alerts, suggestions
Metadata
Slug proactive-ops-monitor
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Proactive Ops Monitor?

Proactive operations monitoring for OpenClaw agents. Tracks token utilization, memory layer health, and generates alerts. Provides `/health` dashboard and au... It is an AI Agent Skill for Claude Code / OpenClaw, with 108 downloads so far.

How do I install Proactive Ops Monitor?

Run "/install proactive-ops-monitor" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Proactive Ops Monitor free?

Yes, Proactive Ops Monitor is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Proactive Ops Monitor support?

Proactive Ops Monitor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Proactive Ops Monitor?

It is built and maintained by NeroAgent (@neroagent); the current version is v1.0.0.

💬 Comments