feishu-cli-meetings

Feishu Meetings and Minutes

This Skill has only one workflow references/workflows/vc/workflow.md, locate the section in it according to the table below and then execute. In this workflow, references/、scripts/、templates/、examples/ resolve the relative path according to workflow.md the directory where it is located; when executing scripts use the resolved actual path, do not rely on the current shell directory.

Routing

Intent	Command	Workflow section
Search historical meetings by topic/time/participant, convert meeting number to meeting_id, get note_id and minute_token at once	vc search、vc detail、vc recording	Command: Search and locate meetings
Meeting notes, notes document, verbatim transcript (ordinary notes read the verbatim document, unified notes export a unified verbatim transcript)	vc notes、vc note detail/transcript、doc export	Decision rules, command: Notes and verbatim transcript
Minutes search, AI summary/todos/chapters/keywords, Minutes verbatim transcript, download audio/video, request Minutes permissions	minutes search/get/download/apply-permission	Command: Minutes
In-progress meetings, in-meeting events	vc meeting list-active、vc bot meeting-events	Command: In-progress meetings and in-meeting events
Meeting bot join/leave	vc bot meeting-join/meeting-leave	Command: Meeting bot join/leave
Direct access to notes and Minutes from calendar events	calendar agenda → vc notes --calendar-event-ids	Typical workflow B

Execution rules

1. Identity:vc search/detail/recording/notes、vc note detail、vc meeting list-active and minutes commands default to User, can --as bot|auto(Bot requires the app to enable the scope, and usually has no permission to read the user's meetings and Minutes);vc note transcript only supports User; meeting-join/leave only supports Bot (passing --user-access-token reports error exit 2);meeting-events the --as must be consistent with the meeting_id source. The identity used to obtain the ID must be carried over to subsequent commands; when a command does not support it, explain the limitation, do not switch identity without authorization.
2. Identifiers cannot be mixed: a 9-digit number is a meeting number, and can only be given to vc detail <会议号>、vc search --query and meeting-join --meeting-number； meeting-events / meeting-leave requires a long numeric meeting_id。
3. When reading a verbatim transcript, first check the notes type:normal use doc export <verbatim_doc>，unified use vc note transcript <note_id>, when there is only Minutes use minutes get <minute_token> --transcript(write to file).
4. vc notes --with-artifacts/--download-transcript All three paths take effect:--meeting-ids / --calendar-event-ids first resolve through recording minute_token, when the meeting has no recording write hint and explain in stderr; when only the summary, todos, etc. are needed use minutes get --summary --todo ..., do not pull the entire artifact.
5. vc notes if any entry fails (including a requested artifact or verbatim transcript) end with exit code 1, already-fetched data is still output as usual;minutes get when an artifact fails, output artifacts_error and exit non-zero;vc recording、minutes download partial failure is still 0, only total failure is non-zero—check each item; ok / error。
6. minutes apply-permission will notify the Minutes owner, and the bot joining/leaving is visible to participants: obtain the user's consent before execution; to verify parameters use --dry-run。
7. After the meeting ends do not use meeting-eventsagain, instead read vc detail / vc notes post-meeting artifacts; for in-meeting events first vc meeting list-active get meeting_id。

Pre-check before User path business commands, for example searching meetings and reading Minutes verbatim transcripts (auth check only checks the User Token; the Bot path requires confirming the application side has enabled the scope, and it cannot be used as a substitute):

feishu-cli auth check --scope "vc:meeting.search:read vc:note:read minutes:minutes:readonly minutes:minutes.artifacts:read"

When delete or overwrite commands return exit code 10, confirm the target and impact with the user, then append the global --yes to rerun; do not add it yourself. For identity or scope errors (such as 99991663/99991668/99991672/99991679), read ../feishu-cli-platform/references/workflows/auth/references/identity.md; to judge success or failure, write scripts, or handle confirmation gates, read ../feishu-cli-platform/references/workflows/auth/references/agent-contract.md。