Ops Framework
PassAudited by ClawScan on May 1, 2026.
Overview
The skill is a coherent local jobs monitor, but it intentionally runs configured local commands and sends Telegram alerts, so its job config and Telegram settings should be reviewed before use.
This skill appears purpose-aligned and not deceptive. Before installing or enabling it, inspect every job command in ops-jobs.json, keep write jobs blocked unless explicitly approved, leave autoResume off unless needed, verify the Telegram recipient, and remove any cron/systemd/launchd scheduler entry when you no longer want monitoring.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A misconfigured job could run local commands with the user's normal permissions.
The monitor executes command arrays from job configuration. This is central to the skill, but users must ensure configured jobs are truly intended and read-only where labeled.
proc = subprocess.run( # noqa: S603
argv,
cwd=str(cwd),
capture_output=True,
text=True,Review ops-jobs.json before enabling jobs, keep examples disabled until customized, avoid shell wrappers unless necessary, and enable auto-resume only for commands you trust.
The skill can send Telegram messages using the configured bot account.
The script uses the Telegram bot token from local OpenClaw configuration to send alerts. This is disclosed and purpose-aligned, but it is still credential use.
token = tg.get("botToken") if isinstance(tg, dict) else None
...
url = f"https://api.telegram.org/bot{token}/sendMessage"Use a dedicated Telegram bot/token for monitoring, limit who can access the bot, and rotate the token if the OpenClaw config is exposed.
Job status details may leave the local machine and appear in Telegram.
Progress and alert text is sent to an external Telegram chat. This is expected for the skill, but users should ensure messages do not include sensitive job output.
payload = json.dumps({"chat_id": target, "text": message, "disable_web_page_preview": True}).encode("utf-8")Set the Telegram target deliberately and avoid including secrets, private file contents, or sensitive command output in job status messages.
Scheduled monitoring can keep running in the background and continue sending alerts.
The framework supports ongoing scheduled operation. This is disclosed and central to monitoring, but it can continue running until the scheduler entry is removed.
Run periodic ticks via your OS scheduler (launchd/systemd/cron). The script is designed to be called frequently;
Only add scheduler entries you understand, document where they are installed, and remove or disable them when monitoring is no longer needed.
The installer metadata may not fully prepare users for the local Python and Telegram/OpenClaw configuration the skill expects.
The registry metadata does not declare practical dependencies or configuration use that the docs describe, such as Python 3.10+ and OpenClaw/Telegram configuration.
Required binaries (all must exist): none Required env vars: none Primary credential: none Required config paths: none
Before installing, confirm Python 3.10+ is available and review the OpenClaw/Telegram configuration paths mentioned in SKILL.md.