searxng-auto-proxy searxng自适应代理检测

SearXNG 自适应代理检测技能，自动检测 Clash 代理可用性，智能切换 17 个搜索引擎，支持性能监控和自动优化。

This package implements an adaptive proxy monitor for SearXNG and generally fits its description, but there are several red flags you should address before installing: (1) The bundle appears incomplete or inconsistent — documentation references many modules, CLI commands, and tests that are not present in the file list. Expect the provided adapter.py to be only part of the claimed system. (2) Default file paths are under /root/.openclaw and logs/caches will be written there; avoid running it as root or on a production host until you review/adjust paths. (3) SKILL.md and code disagree about config locations and environment variables (e.g., SEARXNG_SECRET_KEY, CLASH_API). Verify which variables the running code actually reads and do not paste secrets into examples until confirmed. (4) The start script backgrounds the process — run interactively first to observe behavior. (5) The adapter performs outbound HTTP requests (probing search engines) and will call your local Clash API; run in an isolated environment (container or VM) if you want to test safely. (6) If you lack the missing modules/CLI, expect runtime errors; inspect adapter.py fully for any network callbacks or hidden endpoints before use. If you want, I can: (a) diff the full adapter.py to show exactly which env vars/paths it uses, (b) search the code for any network endpoints beyond the documented ones, or (c) suggest minimal config changes to run it safely in a container.

Type: OpenClaw Skill Name: searxng-auto-proxy Version: 3.0.0 The skill bundle provides a legitimate utility for managing SearXNG search engine proxies through a Clash API. The core logic in `adapter.py` implements a multi-layered approach to detect engine availability and optimize proxy node selection based on latency. While the documentation (SKILL.md) mentions features like a Web Panel and ML prediction that are not present in the provided source code, the included files show no signs of data exfiltration, malicious execution, or prompt injection. The use of hardcoded paths in `/root/.openclaw/` and the interaction with the Clash API are consistent with the tool's stated purpose of automating network configurations for a search aggregator.