WeCom CLI One-Click Installer

Problem

Installing the WeCom CLI is not just adding a command. It depends on a suitable Node.js runtime, a discoverable global executable, bot credentials, and interactive terminal initialization. Manual setups often fail because of incorrect Bot ID or Secret values, missing visible members, incomplete permissions, network delays, missing PATH entries, or automation that avoids a real TTY.

How the skill works

The skill turns installation into a guided sequence: it checks the Node.js requirement, leads the user to create an API-mode bot in the WeCom console, save credentials, assign visible members, and enable required permissions, then completes initialization in a real terminal. It also provides verification steps and troubleshooting hints for issues such as missing command, connection failures, old Node.js versions, registry timeouts, and stale local configuration. It acts as an installation guide and triage checklist rather than a replacement for WeCom permission administration.

Boundary: if a working configuration already exists, switch to usage documentation; if the bot still cannot connect, review bot status, visible members, permissions, and local configuration.