Monitor

Before installing, review and control these points: - Inspect monitor definitions (~/monitor/monitors.json) and avoid storing secrets (API keys, auth headers) in plain JSON. Use environment variables or secure stores where possible. - Be cautious with 'custom' checks: they run arbitrary commands you supply. Do not add untrusted commands that could access or transmit sensitive data. - Only provide webhook URLs or channels you trust. Alert payloads may include status, timestamps, and any logged output; a misconfigured webhook can leak information. - Limit granted access (SSH, Docker) to only the hosts/services you intend to monitor; the skill asks for explicit permission but will act on whatever is listed in 'requires'. - Set filesystem permissions on ~/monitor so only the intended user can read logs and configs (e.g., chmod 700 ~/monitor). - If you need stronger isolation, run this agent under a restricted user account or in an environment with limited network access, and review scheduled intervals to avoid resource or network abuse. Overall: the skill appears coherent for its stated purpose, but take care around custom commands, webhook targets, and any sensitive data that could be captured in logs or alert payloads.