lark-vc

vc (v1)

CRITICAL — Before starting, you MUST first use the Read tool to read ../lark-shared/SKILL.md, which contains authentication and permission handling

Core Concepts

• Video Meeting (Meeting): A Feishu video meeting instance, identified by meeting_id.
• Meeting Record: A record generated after a video meeting ends. Supports searching meeting rooms by filter conditions such as keywords, time period, participants, organizer, and meeting room.
• Meeting Note (Note): A structured document generated after a video meeting ends, including a note document (containing summaries, action items, and chapters) and a verbatim transcript document.
• Minutes: Recording output from Feishu video meetings or audio/video files uploaded by users. Supports transcription and meeting notes for video/audio, identified by minute_token.
• Note Document (MainDoc): The main document of the meeting note, containing AI-generated summaries and action items.
• Verbatim Transcript (VerbatimDoc): A sentence-by-sentence text record of the meeting, including speakers and timestamps.

Core Scenarios

1. Search meeting records

1. Only supports searching meetings that have ended. For future meetings that have not yet started, use the lark-calendar skill.
2. Only supports searching meeting records by filter conditions such as keywords, time period, participants, organizer, and meeting room. For unsupported filter conditions, prompt the user.
3. When search results contain multiple records, be sure to handle pagination data retrieval and do not miss any meeting records.

2. Organize meeting notes

1. When organizing note documents, by default just provide the links to the note document and verbatim transcript; there is no need to read the contents of the note document or verbatim transcript.
2. Only when the user explicitly needs to obtain the summary, action items, or chapter outputs from the note document should you read the document to obtain the specific content.

3. Links to note documents and verbatim transcripts

1. Note documents, verbatim transcript documents, and associated shared documents are returned by default using document Tokens.
2. When only basic information such as the document name and URL is needed, use lark-cli drive metas batch_query to query

# 学习命令使用方式
lark-cli schema drive.metas.batch_query

# 批量获取文档基本信息: 一次最多查询 10 个文档
lark-cli drive metas batch_query --data '{"request_docs": [{"doc_type": "docx", "doc_token": "<doc_token>"}], "with_url": true}'

1. When document content is needed, use lark-cli docs +fetch。

# 获取文档内容
lark-cli docs +fetch --doc <doc_token>

Resource Relationships

Meeting (视频会议)
├── Note (会议纪要)
│   ├── MainDoc (主纪要文档)
│   ├── VerbatimDoc (逐字稿)
│   └── SharedDoc (会中共享文档)
└── Minutes (妙记)
    ├── Transcript (文字记录)
    ├── Summary (总结)
    ├── Todos (待办)
    └── Chapters (章节)

Note：+search can only query historical meetings that have ended. To query future schedules, use lark-calendar。

Priority: When users search historical meetings, prioritize using vc +search rather than calendar events search. Calendar search targets schedules, while vc search targets ended meeting records and supports filtering by dimensions such as participants, organizer, and meeting room.

Routing Rules: If the user is asking about "meetings that have been held", "which meetings were held today", "what meetings have I attended recently", "ended meetings", or "historical meeting records", prioritize using vc +search. Only prioritize using lark-calendar。

Special Cases: When the user queries "what meetings are there today", use vc +search to query the meeting records of meetings held today, and at the same time use the lark-calendar skill to query meetings today that have not yet started, and after organizing them together, display them to the user.

Shortcuts (recommended to use first)

A Shortcut is a high-level wrapper for common operations (lark-cli vc +<verb> [flags]). For operations that have a Shortcut, use it first.

Shortcut	Description
+search	Search meeting records (requires at least one filter)
+notes	Query meeting notes (via meeting-ids, minute-tokens, or calendar-event-ids)

API Resources

lark-cli schema vc.<resource>.<method>   # 调用 API 前必须先查看参数结构
lark-cli vc <resource> <method> [flags] # 调用 API

Important: When using the native API, you must first run schema to view the --data / --params parameter structure; do not guess the field format.

meeting

• get — Get meeting details (topic, time, participants, note_id)

# 获取会议基础信息：不包含参会人列表
lark-cli vc meeting get --params '{"meeting_id": "<meeting_id>"}'


# 获取会议基础信息：包含参会人列表
lark-cli vc meeting get --params '{"meeting_id": "<meeting_id>", "with_participants": true}'

minutes (cross-domain, see lark-minutes）

• get — Get basic Minutes information (title, duration, cover); query notescontentPlease use +notes --minute-tokens <minute-token>

Permission table

Method	Required scope
+notes --meeting-ids	vc:meeting.meetingevent:read、vc:note:read
+notes --minute-tokens	vc:note:read、minutes:minutes:readonly、minutes:minutes.artifacts:read、minutes:minutes.transcript:export
+notes --calendar-event-ids	calendar:calendar:read、calendar:calendar.event:read、vc:meeting.meetingevent:read、vc:note:read
+search	vc:meeting.search:read
meeting.get	vc:meeting.meetingevent:read