Hotspot Aggregator

Things to check before installing or running: - Ensure curl and jq are available: the scripts call curl and jq although the skill metadata did not list required binaries. Without them the scripts will fail. - Understand the network behavior: by default the skill uses demo data, but setting USE_REAL_API=true (and optionally PROXY) makes the scripts perform HTTP requests to external endpoints (weibo, baidu, zhihu, and a third‑party aggregator api.oioweb.cn). Only enable live mode if you trust those endpoints and your environment's network/credentials policy. - Review absolute paths: the scripts read/write under /root/clawd/memory/hotspots. Confirm that path is acceptable in your environment and does not overlap with sensitive data or other skills. - Third‑party API trust: api.oioweb.cn is a third‑party aggregator (not an official Douyin endpoint). Evaluate whether you trust that service before enabling real API mode. - Config and notifyChannel: the config.json contains notifyChannel but the scripts do not implement any notification delivery — if you expect push notifications, verify or implement the mechanism safely. - Minimal privileges: run the skill in a sandbox or non-privileged account first to confirm behavior. If you need a higher assurance, inspect network traffic (or run with USE_REAL_API=false) and review the scripts line-by-line — the code is simple shell, so manual review is feasible. Summary: functionally coherent but metadata omissions and network/absolute-path choices are the main concerns; review and test in a limited environment before trusting it in production.