为 IOC（智能运营中心）生成智能巡检报告。自动分析设备状态、报警记录、能耗数据，生成专业的巡检日报/周报。支持连接 PostgreSQL 数据库读取实时数据，输出 Markdown/HTML 报告。适用于物业管理、商业综合体、工业园区等场景。

Do NOT run this skill until you review and modify its configuration. Specific steps to consider: - Open config.yaml in the skill directory and remove or replace the shipped database host, user, and plaintext password (hightop.xin, port 55432, user 'postgres', password shown). Treat these as untrusted sample credentials. - If you want the skill to access your database, explicitly edit the config to point to your DB (or remove the file so the script falls back to env vars), and set credentials via environment variables rather than leaving plaintext in the repo. - Be aware SKILL.md suggests editing ~/.openclaw/skills/... but the script will use the bundled config.yaml in the skill directory if present — this mismatch can lead to accidental connections to the remote host. - Audit scripts/generate_report.py (and any other scripts) fully for any network calls or unexpected behavior before running. Run in an isolated environment (sandbox, VM, or container) with network egress controlled until you confirm it only connects to the DB you expect. - If you do not intend to connect to any external DB, remove or overwrite the provided config.yaml and run with simulated data (psycopg2 missing or mock mode) until you have a safe config. - If you are concerned about data leakage or misuse, reject installation; the inclusion of remote credentials is poor hygiene and could indicate careless or malicious packaging.

Type: OpenClaw Skill Name: ioc-patrol-report Version: 1.0.0 The skill bundle contains hardcoded, plaintext credentials (host, username, and password) for a remote PostgreSQL database (hightop.xin:55432) within the config.yaml file. While the logic in scripts/generate_report.py is consistent with the stated purpose of generating facility management reports, the inclusion of active remote credentials in a distributed package is a significant security vulnerability. There is no clear evidence of intentional malice, but the presence of specific, non-placeholder credentials for an external server is a high-risk configuration.