AI 日报 - 自动抓取 LLM/Agent 领域热点信息，生成结构化中文简报。

What to check before installing or running: - Review and fix undeclared env vars: the code calls an Alibaba LLM endpoint using ALIBABA_CLOUD_API_KEY but SKILL.md/registry metadata does not declare it. If you plan to use remote LLMs, only set that secret after you understand what data will be sent. - Do not run push-to-dingtalk.sh until you verify the destination: the script contains a hard-coded OpenClaw/DingTalk session id; running it will send report contents to that session. Remove or replace the session id with your own, or avoid running the script. - Fix TLS settings: ai_daily.py disables SSL verification (ssl.CERT_NONE); this permits silent man-in-the-middle attacks. Update the code to use default SSL verification (do not set verify_mode to CERT_NONE and keep check_hostname True) before running on sensitive networks. - Ensure required binaries are declared and present: the scripts call the 'openclaw' CLI in push/generation examples but the skill only declares python3 and curl. If you don't have OpenClaw CLI configured, those commands will fail; if you do, be aware they can transmit messages. - Consider running in an isolated environment first (container or sandbox) and inspect logs to confirm what external endpoints receive your data. If you need the skill but not external pushes or remote LLM calls, edit the code to disable push scripts and/or the call_llm function and run in 'local-only' / debug mode. - If you are unsure, ask the skill author to (1) explicitly declare all env vars the code uses (including ALIBABA_CLOUD_API_KEY), (2) remove hard-coded session ids or make them configurable, and (3) re-enable proper SSL verification and document why network calls are necessary.

Type: OpenClaw Skill Name: ai-daily-cn Version: 1.2.0 The skill is classified as suspicious primarily due to a critical vulnerability in `scripts/ai_daily.py`. It disables SSL certificate verification (`ssl.CERT_NONE`) for all network requests, making it highly susceptible to Man-in-the-Middle (MITM) attacks. An attacker could intercept and inject malicious content into RSS feeds or API responses, potentially compromising the system. While there is no evidence of intentional malicious behavior like data exfiltration or unauthorized remote control, this severe vulnerability poses a significant security risk, allowing external attacks.