Tencent Meeting CLI

Problem

The Tencent Meeting skill targets workflows that need to place meeting operations in a terminal or Agent pipeline. The hard part is not simply starting a meeting; it is routing the right command when handling meeting lifecycle changes, recordings, transcripts, invitees, in-call controls, and tool error feedback without leaking privacy or skipping confirmations.

How It Works

• Setup and auth: It centers on the tmeet CLI. If the command is missing, it expects the CLI package to be installed. OAuth login is a blocking flow and must run in the foreground so credentials are written correctly.
• Query routing: Use list commands for pure time-range filters. Use search when the request contains keywords such as topic, meeting code, creator, or notes. Recording, replay, and transcript queries require the detailed routing rules for meeting-level and recording-level entry points, permissions, and artifact location.
• Parameters and output: Time values use ISO 8601. Pagination uses --page-token and --page-size. --compact trims response fields, while --format controls JSON layout.
• Safety and confirmation: Destructive or user-facing write actions such as canceling a meeting, updating details, changing invitees, calling or removing participants, logging out, or submitting recording permission requests must be shown to the user first and executed only after explicit confirmation. User-facing output should use meeting_code, not meeting_id, and tokens must not be printed.

Note: The skill depends on network access, an npm environment, and a valid login session. Contact search is limited to resolving invitees or call targets, not general person lookup.