WeCom Unified

Problem Addressed

Enterprise WeChat (WeCom) is a dominant workplace collaboration platform, yet many of its operations rely on web or mobile interfaces, lacking native command-line integration. This hinders automation, batch processing, and programmatic control for developers. Manually performing repetitive tasks such as bulk contact searches, document management, or meeting scheduling is time-consuming and error-prone.

Core Capabilities and Workflow

The WeCom Unified suite provides a comprehensive CLI toolset via wecom-cli, encapsulating core WeCom functionalities into programmable commands.

• Business Domain Routing: The skill intelligently routes user intents to specific business domains like contact, doc, calendar, etc., based on the overview table. Each domain has a dedicated reference file detailing parameter specifications.
• Strict Pre-checks: Before any command, wecom-cli --version must be run to verify the CLI version (≥ 1.1.0), and wecom-cli auth show --status to check credential configuration. If unauthorized, wecom-cli auth must be executed for QR code authorization.
• Identity and ID Constraints: Operator identity is obtained via wecom-cli identity whoami. All outputs strictly prohibit exposing internal IDs like userid or chat_id, mandating readable names (e.g., names, titles) and referencing reference files for conversion.
• Domain Collaboration: For instance, creating a meeting may require querying busy-free slots in the calendar domain first, and document searches can be handled through the doc-manage domain, illustrating data flow across domains.

Applicable Boundaries and Notes

The skill is not omnipotent and has clear boundaries:
- Feature Limitations: It currently does not support creating recurring calendar/meeting events, drafting or recalling emails, or moving/deleting files, among other operations.
- Pre-requisites: wecom-cli must be installed with a compliant version, and credential configuration is a mandatory step.
- Output Specifications: Due to ID constraints, when an API returns only an ID, the system attempts to convert it to a readable name via reference files. If conversion fails, natural language descriptions are used to refer to objects without exposing machine identifiers.
- Disambiguation Mechanism: For ambiguous commands like "schedule a meeting," disambiguation is triggered during creation to determine if it's a calendar event or online meeting, while queries merge results from both domains.