lark-meeting

Unified entry for Lark Video Conference business, supporting operations such as querying meeting records, real-time meeting interaction, managing Minutes, reading intelligent minutes, etc. This skill is responsible for domain relationships, task routing and cross-command orchestration.

No need to pre-read

lark-shared

or pre-run

auth status --verify

; only read this Skill when encountering unauthenticated, token/identity or scope errors, then retry after fixing. Requests for authentication, identity or scope management directly use this Skill.

Identity Initialization and Continuity

Use

source_identity

as the state of cross-command workflows:

Source identity already exists in context: Strictly follow it. When the user requests to switch, first explain the identity continuity and permission impact, do not switch silently.
No source identity, user explicitly specifies identity: Use the
```
--as
```
specified by the user.
No source identity and user does not specify: Use
```
--as bot
```
when the operation semantics explicitly require an application robot, otherwise explicitly use
```
--as user
```
.

After determining

source_identity

, check whether the target command supports this identity:

Supported: Explicitly pass it in and continue execution.
Not supported: Explain the restrictions and stop; do not replace the identity to make the command succeed.
Only restart a workflow with the new identity after the user explicitly agrees to switch identity.

Domain Model and Concepts

text

[Meeting Sources]

Calendar Schedule (event_id) ──Scheduled or Associated──┐
Instant Meeting (no event_id)────────────────┴──► Meeting (meeting_id)

Calendar Schedule ──meeting_note────────────► Doc (user-created minutes, independent of AI intelligent minutes)

[Meeting Artifacts]

Meeting (meeting_id)
├── AI Summary ──► Note (intelligent minutes) (note_id)
│               ├── Intelligent Minutes Document ───────────► Doc (note_doc_token)
│               ├── Verbatim Transcript
│               │   ├── normal  ──────────► Doc (verbatim_doc_token)
│               │   └── unified ──────────► note +transcript (non-independent Doc)
│               └── Shared Document ──────────────► Doc (shared_doc_tokens)
│
└── Recording ──► Minutes (minute_token)
                 ├── AI Products: Summary / Todo / Chapter / Keyword
                 ├── Transcript (text record)
                 └── Original Audio & Video

Local Audio & Video ─────────────────────────────► Minutes (minute_token)

Object	Primary Identifier	Concept and Relationship
Calendar Schedule	`event_id`	A schedule on the calendar, including time, participants, conference rooms and RSVP, which can be scheduled or associated with VC meetings; it is not a complete meeting record. The `meeting_note` on the schedule is a Doc manually bound by the user, which has nothing to do with AI intelligent minutes.
Meeting	`meeting_id`	An actual video conference that can come from Calendar or be an instant meeting without a schedule. Meeting topic, time, participant snapshot and in-meeting events belong to meeting data; Note and Minutes are possible post-meeting artifacts associated with it.
Note (Intelligent Minutes)	`note_id`	A collection of logical artifacts formed after enabling AI summary. `note_display_type` determines different ways to obtain text records in the verbatim transcript.
Minutes	`minute_token`	Generated by meeting recording or local audio & video upload, including summary, to-do items, chapters, keywords, text records and original audio & video; it can be associated with VC meetings or exist independently.
Doc	Doc token	Content carrier, not a meeting identifier. `note_doc_token` , `shared_doc_tokens` and some `verbatim_doc_token` point to Doc; Doc token cannot be used as `note_id` or `meeting_id` .

Core Identifiers

```
meeting_id
```
: Meeting ID. A long numeric string, not a 9-digit meeting number.
```
meeting_no
```
: Meeting number. 9-digit pure number; CLI parameter name is
```
--meeting-number
```
.
```
minute_token
```
: Minutes Token. A lowercase alphanumeric string, usually obtained from the Minutes URL
```
/minutes/<minute_token>
```
.

All the above identifiers are passed as strings as they are and cannot be substituted for each other.

Domain Invariants

Note and Minutes come from two independent links of AI summary and recording respectively. A meeting may have both types of artifacts, only one type, or none at all; it is impossible to infer that a
```
minute_token
```
must exist based on
```
note_id
```
, and vice versa.
Minutes can be directly generated from local audio & video, so it is not necessarily associated with
```
meeting_id
```
or Calendar
```
event_id
```
.
Calendar
```
meeting_note
```
, Note
```
note_id
```
, Minutes
```
minute_token
```
and various Doc tokens identify different objects and cannot be interchanged, substituted into commands of other domains or inferred from one another.

Quick Actions

Query Ongoing Meeting Content

bash

# Meetings the current user is in
lark-cli vc +meeting-list-active --as user

# Target user's meetings visible to the application robot
lark-cli vc +meeting-list-active --as bot --user-id <open_id>

# Use the source identity after confirming the unique meeting_id
lark-cli vc +meeting-events --as <source_identity> --meeting-id <meeting_id> --page-all --format pretty

When there are multiple meetings, you need to select the meeting to query first; when there is only one meeting, directly query the meeting events of that meeting.

The application identity only returns meetings where "the target user is attending and the application robot is also in the same meeting"; an empty result does not mean the target user is not in a meeting. Use "user identity" or "application identity" when explaining results to users, do not expose internal abbreviations like

user

bot

Scenario Manuals

When the task target matches a scenario, read the corresponding scenario manual and execute the task according to the process.

Query Meeting and Artifacts: Locate historical meetings by topic, time, participants or
```
meeting_id
```
/
```
meeting_no
```
/
```
event_id
```
; query participants, recordings and intelligent minutes or Minutes associated with the meeting; summarize or review based on meeting records.
Query Minutes and Artifacts: Have Minutes URL /
```
minute_token
```
, or search Minutes by title, owner, participants; read summary, to-do items, chapters, keywords, verbatim transcript, download original audio & video, or query associated intelligent minutes.
Generate and Modify Minutes, Manage Minutes Permissions: Generate Minutes, verbatim transcript, summary, to-do items or chapters from local audio & video; modify Minutes title, summary, to-do items, keywords or speakers; apply for Minutes permissions, or view and assign Minutes collaborator permissions.
Query Intelligent Minutes and Associated Artifacts: Have
```
note_id
```
, intelligent minutes Docx URL/token, or need to query minutes content, verbatim transcript, Minutes and shared documents and other associated artifacts.
Application Robot Attendance and In-Meeting Interaction: Complete orchestration of application robot's active meeting discovery, real attendance, event pulling, text/emoji interaction and explicit authorized departure.
In-Meeting Events and In-Meeting Interaction: When no new join/leave operations are triggered, use user identity or application identity already in the meeting to query active meetings, view speeches/chat/shared content, or send text and emojis.

Command Reference

Command	Purpose	Reference Method
`vc +search`	Search historical meetings	lark-vc-search
`vc +detail`	Query meeting information and associated Note, Minutes identifiers	lark-vc-detail
`vc meeting get`	Query basic meeting information and participant snapshot	`lark-cli vc meeting get --help`
`vc +recording`	Locate recordings and Minutes from meetings	lark-vc-recording
`vc +meeting-list-active`	Discover currently visible ongoing meetings	lark-vc-meeting-list-active
`vc +meeting-events`	Read in-meeting events and shared content	lark-vc-meeting-events
`vc +meeting-message-send`	Send in-meeting text messages or emojis	lark-vc-meeting-message-send
`vc +meeting-join`	Let application robot join the meeting	lark-vc-agent-meeting-join
`vc +meeting-leave`	Let application robot leave the meeting	lark-vc-agent-meeting-leave
`minutes +search`	Search Minutes	lark-minutes-search
`minutes minutes get`	Query basic Minutes information	`lark-cli minutes minutes get --help`
`minutes +detail`	Read Minutes information and specified artifacts	lark-minutes-detail
`minutes +download`	Download original audio & video of Minutes	lark-minutes-download
`minutes +upload`	Generate Minutes from cloud storage audio & video	lark-minutes-upload
`minutes +update`	Modify Minutes title	lark-minutes-update
`minutes +speaker-replace`	Replace speakers in Minutes verbatim transcript	lark-minutes-speaker-replace
`minutes +summary`	Replace Minutes AI summary	lark-minutes-summary
`minutes +todo`	Add/delete/modify Minutes AI to-do items	lark-minutes-todo
`minutes +apply-permission`	Apply for Minutes view or edit permission	lark-minutes-apply-permission
`drive +member-list`	View Minutes collaborators and their permissions	lark-drive-member-list
`drive +member-add`	Assign Minutes view or edit permission to specified members	lark-drive-member-add
`minutes +word-replace`	Batch replace keywords in Minutes verbatim transcript	`lark-cli minutes +word-replace --help`
`note +detail`	Query intelligent minutes and associated document identifiers	lark-note-detail
`note +transcript`	Obtain unified intelligent minutes verbatim transcript	lark-note-transcript

Progressive Loading Rules

Load progressively in the order of "Quick Actions → Scenario Manuals → Command Reference":

When the user's target meets the entry conditions of "Quick Actions", directly execute the corresponding CLI; do not pre-read scenario manuals, command references,
```
--help
```
or schema.
If it does not meet the quick action conditions, or lacks key identifiers, needs disambiguation, or involves write operations, read one main scenario manual matching the target; when the main scenario explicitly transfers to a downstream scenario, only continue to read the referenced scenario or chapter, and execute the CLI according to the process in it.
Only when specific parameters, return fields, special constraints or exception handling methods are missing: For commands with reference manuals, read the corresponding file; for commands without reference manuals, run the exact
```
lark-cli ... --help
```
listed in the table. When the scenario or reference has given an exact command, do not call
```
--help
```
again; only call it when parameters are missing, commands are unrecognized, or documents conflict with running results.

lark-meeting

NPX Install

Tags

SKILL.md Content (Chinese)

lark-meeting

Identity Initialization and Continuity

Domain Model and Concepts

Core Identifiers

Domain Invariants

Quick Actions

Query Ongoing Meeting Content

Scenario Manuals

Command Reference

Progressive Loading Rules