WeChat Auto Reply

微信消息自动发送/半自动回复。主动发送时，按“搜索联系人→单聊直接 Enter 进入聊天；群聊先识别群聊分组再定位目标项→粘贴消息→发送”的逻辑执行。适用于 macOS + 微信桌面版环境，需本机完成权限和依赖配置。使用方式：wechat-auto-reply "联系人名称" 或 wechat-auto-repl...

This package appears to implement WeChat UI automation on macOS, which reasonably needs Accessibility permission, cliclick, screencapture, and Vision OCR. Before installing: - Do NOT grant Accessibility permission until you trust the scripts. UI automation can read and control your screen and keyboard. - The package references a wechat-dm.applescript file but that file is not included—installation as provided will fail. Ask the author or the tap for the missing AppleScript and inspect it before running. - The README suggests installing from a third-party Homebrew tap (bjdzliu/openclaw). Only add and install from taps you trust and inspect the formula contents. - Inspect the AppleScript and any Homebrew formula for network or credential usage. The included Python and shell files do not perform network calls or credential exfiltration, but the missing AppleScript could change that behavior. - Be prepared to calibrate hard-coded click coordinates and to install cliclick and pyobjc dependencies in a safe environment first. The repo also contains developer-local paths (e.g., /Users/chuck/.venvs/...), a sign of incomplete packaging. If you want to proceed, request the missing wechat-dm.applescript and the Homebrew formula source, review them, and test in a non-critical account or VM before granting Accessibility to the scripts.

Type: OpenClaw Skill Name: wechat-auto-reply-mac Version: 1.0.1 The skill automates WeChat on macOS using high-risk techniques including screen capture (`screencapture`), OCR (Vision Framework), and UI manipulation via `cliclick` and AppleScript. While these actions align with the stated 'auto-reply' purpose, the Python scripts (`state_machine_final.py` and `state_machine_test.py`) contain vulnerabilities where user-controlled strings (contact names/messages) are interpolated directly into AppleScript commands without sanitization, creating a risk of local injection. The inclusion of hardcoded developer-specific file paths (e.g., `/Users/chuck/`) and fixed screen coordinates suggests the code is unvetted and may behave unpredictably in different environments.