wecomcli-meeting

Use `wecom-cli meeting create` with a JSON payload containing subject, begin_time, end_time, and attendees as userid object arrays. The skill resolves names to userids, checks attendee free/busy status, and confirms the created meeting's subject, time, and participants.

Use `meeting search` with a keywords array when you know the meeting topic or attendee name, and `meeting list` with a time range for browsing. Ambiguous queries like "what meetings do I have" trigger searches of both meetings and calendar schedules, merged into one result.

No. Creating, updating, and canceling recurring (repeating) meetings is not supported by the API. When a recurring meeting is detected via a non-empty repeat_rule, the skill tells you to manage it manually in the WeCom client instead of attempting workarounds.

Use `meeting original get` for the verbatim transcript with timestamps and speakers, or `meeting get` for AI-generated notes and todos. Plain summary requests return the ready-made notes; custom summarization requests are generated from the full transcript.

Attendees must be object arrays like [{"userid": "woxxx"}], not plain names or string arrays, and names must be resolved through the contact skill. The meeting_id is a long string with an mt prefix; the 9-digit meeting_code cannot be used as meeting_id.

Meetings are capped at 100 attendees and 24 hours duration, recurring meetings cannot be created or modified, RSVP responses to invitations are unsupported, and `meeting get` accepts at most 10 meeting IDs per call, requiring batched requests.