Tender Analysis System

自动化抓取并智能分析各行业招标信息，生成多维度结构化标书风险与付款方式分析报告。

This package looks like a template for a tender-scraping and analysis system but the actual crawling and push logic are missing. Before installing or running: 1) Don't place secrets (LLM API keys, SMTP passwords, webhook URLs) in config.yaml on shared machines — prefer environment variables or a secure secret store. 2) Inspect and, if needed, implement or review any scraping code to ensure it follows robots.txt and legal constraints; the current code does not perform scraping. 3) Review cron_setup.sh before running — it will modify your crontab and create persistent scheduled jobs. 4) If you plan to enable push notifications (Feishu/SMTP) verify webhook URLs and SMTP credentials and test in an isolated environment. 5) If you need the described scraping features, request or implement the missing network/crawl modules and re-audit them for unexpected endpoints or data exfiltration.

Type: OpenClaw Skill Name: tender-analysis-system Version: 1.0.0 The bundle implements an automated tender monitoring system that performs high-risk environment modifications, specifically establishing persistence by modifying the system's crontab (cron_setup.sh) and installing Python dependencies (run.sh). While these actions align with the stated goal of periodic automation, they are performed without explicit user confirmation within the scripts. Furthermore, config.yaml contains a hardcoded Chinese email address ([email protected]) as a default notification target, which could lead to unintended data disclosure if the user fails to update the configuration. The core logic in tender_analyzer.py is currently a skeleton that manages a database but lacks the actual scraping implementation described in the SKILL.md instructions.