Windows Api Monitor

监控并统计Windows环境下OpenClaw API调用，支持实时分析、历史追踪及阈值告警，生成多维度使用报告。

This skill generally matches its stated purpose (reading OpenClaw logs to report API usage), but I recommend caution before running it on a machine with sensitive prompts or private data. Actionable steps: - Inspect the repository locally before running: open the scripts to confirm no unexpected network calls or obfuscation. Pay special attention to any code that uses requests, urllib, smtplib, or subprocess to call external endpoints. - Note the manifest/documentation mismatch: SKILL.md references several scripts that are not included. That suggests the package may be incomplete or stale — expect runtime errors. - Because the tool reads ~/.openclaw/logs and can include detailed logs in reports (include_details=true), assume reports may contain sensitive prompts/responses. If you must run it, either set include_details=false and set security.encrypt_sensitive=true (and verify the code actually performs encryption/redaction) or run the tool on a copy of the logs that you have redacted. - The config supports webhook/email alerts. Do not configure webhook URLs or SMTP credentials unless you trust the destination; test in a local, isolated environment (VM) first. - Consider running the scripts in a sandbox/VM account with limited data (or on a non-production machine) and review generated reports in reports/ before allowing persistent scheduling (Task Scheduler or continuous mode). - If you rely on this skill for production monitoring, obtain a complete, verified release that contains the missing referenced files and fix the apparent code truncation/bugs; otherwise treat this package as untrusted.

Type: OpenClaw Skill Name: windows-api-monitor Version: 1.0.0 The windows-api-monitor skill is a legitimate utility designed to track and report API usage and costs for the OpenClaw agent on Windows. It functions by parsing local log files (typically in ~/.openclaw/logs) and generating statistical reports or alerts based on user-defined quotas in settings.yaml and quotas.json. The code (api_monitor.py, auto_checker.py, etc.) is transparent, well-documented, and lacks any indicators of malicious intent such as data exfiltration, unauthorized remote execution, or obfuscation.