Openclaw Health Audit

OpenClaw 系统健康审计与自动修复 — 监控 prompt 体积、Cron 合规、Session 清理、Token 消耗

This skill appears to do what it says: local inspection of OpenClaw files, optional registration of a 48h health-check cron job, and conservative auto-fixes (cron/session). Before installing, consider: 1) Back up ~/.openclaw/cron/jobs.json and ~/.openclaw/.lib/session_model_state.json so you can revert changes. 2) Run the wizard and health_monitor in --dry-run first (audit_wizard.py offers this). 3) Confirm the agent/system that will execute cron job payloads (the 'agentTurn' payload instructs sending reports via Telegram/Discord) — ensure those outbound connectors and recipients are trusted because reports will contain local audit data. 4) The documentation contains a small contradiction (claims 'Does NOT send data to external servers' yet describes sending via Telegram/Discord); treat reporting as network-capable behavior originating from your configured agent, not from the Python scripts themselves. 5) If you rely on the openclaw CLI for usage-cost, ensure its stored credentials are scoped appropriately. If you want higher assurance, inspect scripts (they are included) and run them in a controlled environment before enabling auto-fix or registering the cron job.

Type: OpenClaw Skill Name: openclaw-health-audit Version: 1.5.0 The skill performs high-risk operations including modifying OpenClaw Cron jobs (jobs.json) and session state files (session_model_state.json) to perform 'auto-repairs.' It also registers a persistent Cron job for periodic monitoring via audit_wizard.py. While these actions are aligned with the stated purpose of system health auditing and cost optimization, the ability to modify system configuration and state files constitutes a significant attack surface. The scripts health_monitor.py and audit_wizard.py handle these sensitive file operations. No evidence of data exfiltration or unauthorized external network calls was found.