← Back to Skills Marketplace

status-monitor

Name: status-monitor
Author: yahao333

by Jax Hao Yang · GitHub ↗ · v1.0.5 · MIT-0

cross-platform ✓ Security Clean

201

Downloads

Stars

Active Installs

Versions

Install in OpenClaw

/install status-monitor

Description

Manages OpenClaw Agent status upload scripts, periodically syncing agent online status to the cloud monitoring platform

Usage Guidance

This skill is coherent: it periodically reads your OpenClaw agent list and uploads agent IDs to the dashboard at https://openclaw-agent-monitor.vercel.app (or an override URL). Before installing: 1) Confirm you trust the dashboard operator and domain — the skill will store an agent token in plaintext under ~/.openclaw/credentials and use it to authenticate uploads. 2) Review the contents of ~/.openclaw/openclaw.json to ensure only non-sensitive agent IDs are being uploaded. 3) If you prefer not to store a token in a file, avoid starting the daemon and instead run one-off uploads manually. 4) Note the small metadata mismatch: the registry lists no required env vars but the script honors MONITOR_PLATFORM_TOKEN and OPENCLAW_MONITOR_URL — treat those as the actual credentials/config the skill expects. If you are unsure about trusting the remote service, do not provide the token or install the daemon.

Capability Analysis

Type: OpenClaw Skill Name: status-monitor Version: 1.0.5 The 'status-monitor' skill is a legitimate utility designed to sync OpenClaw agent status to a remote monitoring dashboard. The core logic in `status_uploader.py` collects agent IDs from the local `openclaw.json` file and transmits them to a specified Vercel-hosted endpoint (`openclaw-agent-monitor.vercel.app`) using a user-provided API token. While the script utilizes background daemonization (via `os.fork`) and network communication, these capabilities are strictly aligned with its stated purpose of persistent status monitoring, and no evidence of malicious data exfiltration or unauthorized command execution was found.

Capability Assessment

✓ Purpose & Capability

Name/description match the implementation: the Python script reads ~/.openclaw/openclaw.json to extract agent IDs and POSTs them to a monitor URL. No unrelated binaries, credentials or config paths are requested beyond what is needed to upload agent IDs and manage a local daemon.

✓ Instruction Scope

SKILL.md instructions stay within scope: they describe checking for a token, guiding the user to obtain it, saving it under ~/.openclaw/credentials/openclaw-status-monitor.json, and running the included status_uploader.py in cron or daemon mode. The runtime instructions reference only the monitor URL, token locations, the openclaw.json agent list, logs, and PID files — all consistent with the stated task.

✓ Install Mechanism

No install spec — instruction-only with a bundled Python script. No downloads from arbitrary URLs or package installs. The code file is present in the skill bundle (scripts/status_uploader.py) and is not obfuscated.

ℹ Credentials

Registry metadata declares no required env vars/primary credential, but the script and SKILL.md reference MONITOR_PLATFORM_TOKEN (and optionally OPENCLAW_MONITOR_URL). The token is the expected credential for this function, but the registry metadata does not declare it — minor inconsistency. The script stores the token in plaintext under ~/.openclaw/credentials and will use it in an x-agent-token header; this is expected but sensitive.

✓ Persistence & Privilege

Skill is not always:true and is user-invocable. It writes only its own credential/config and log/pid files under ~/.openclaw; it does not modify other skills or system-wide settings. Daemon behavior and forking are expected for a periodic uploader.

How to Use

Make sure OpenClaw is installed (local or Docker)
Run the install command in chat: /install status-monitor
After installation, invoke the skill by name or use /status-monitor
Provide required inputs per the skill's parameter spec and get structured output

Version History

v1.0.5

- No code or documentation changes detected in this version. - Functionality and documentation remain unchanged from the previous release.

v1.0.4

- No file changes detected in this version. - Documentation (SKILL.md) updated: main sections are now in English; commands and example phrases are clarified and shown both in English and Chinese. - Instructions, command examples, and user flows are reworded or reformatted for improved readability. - All technical details, error messages, and usage flows remain unchanged. - No functional or code updates included in this release.

v1.0.3

- Dropped deprecated script: scripts/update_last_active.py has been removed. - Documentation updated to clarify two upload modes: OpenClaw cron single-run (default), and optional long-running daemon mode. - Removed references to the now-deleted update_last_active.py and emphasized status_uploader.py as the single upload script. - No impact to core sync or monitoring functionality.

v1.0.2

- Added recommended use of --fork for starting the status monitor as a true background daemon process. - Updated all service management instructions and examples to use the new --fork option. - Added support and documentation for "restart" (重启) commands to restart the upload service. - Improved and clarified service log handling, including auto-rotation for log files exceeding 10MB. - Cleaned up legacy/outdated instructions and emphasized concise startup and error handling guides.

v1.0.1

Major update: Version 3.0.0 of "status-monitor" introduces a management script for regular status uploads. - Added `scripts/status_uploader.py` and `scripts/update_last_active.py` for managing Agent status sync as a background service. - Provided new CLI commands for starting, stopping, and configuring upload intervals (default is 5 minutes). - All status synchronization now handled by the new Python script; offline judgment is delegated to the cloud dashboard. - Updated initialization, error handling, and process management instructions. - Previous random greeting generation and related SOUL.md parsing have been removed.

v1.0.0

openclaw-status-monitor v1.2.0 - 新增定时（默认每30分钟）自动同步 OpenClaw Agent 状态到云端监控平台。 - 增强初始化流程：检测和引导用户配置监控 Token，并提供详细步骤。 - 支持从每个代理的 SOUL.md 个性化生成随机问候语，自动提取关键词与模板匹配，中英文支持。 - 新增手动和自定义同步间隔的触发方式，支持指令如“同步状态”“每10分钟同步一次”等。 - 优化错误处理和日志记录，缺少 Token、Token 无效、SOUL.md 缺失等场景均有友好提示与自动引导。

Metadata

Slug status-monitor

Version 1.0.5

License MIT-0

All-time Installs 0

Active Installs 0

Total Versions 6

Frequently Asked Questions

What is status-monitor?

Manages OpenClaw Agent status upload scripts, periodically syncing agent online status to the cloud monitoring platform. It is an AI Agent Skill for Claude Code / OpenClaw, with 201 downloads so far.

How do I install status-monitor?

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

Is status-monitor free?

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

Which platforms does status-monitor support?

status-monitor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created status-monitor?

It is built and maintained by Jax Hao Yang (@yahao333); the current version is v1.0.5.

More Skills