Question 1

What does the lark-meeting skill actually do?

Accepted Answer

It is the unified entry point for Feishu video-meeting data: past meeting records, live meeting content, Minutes (妙记), and AI smart notes (智能纪要). One command tree — `lark-cli vc`, `lark-cli minutes`, `lark-cli note` — covers search, detail, transcript download, live interaction, and bot attendance. Scheduling, busy-time, and room management do not live here; those go to lark-calendar.

Question 2

What's the difference between meeting_id, meeting_no, note_id, and minute_token?

Accepted Answer

Four different objects that never substitute for each other. meeting_id is the long digit ID of one actual meeting. meeting_no is the 9-digit number users read aloud — the CLI calls the parameter --meeting-number. note_id points to an AI smart-note collection. minute_token points to a Minutes recording (taken from a URL like /minutes/obcxxx). Mismatching them across domains is the most common failure mode.

Question 3

What's the difference between Note and Minutes?

Accepted Answer

Two independent pipelines. Note (智能纪要) comes from AI summarization when a meeting has AI summary enabled. Minutes (妙记) comes from recording — either a recorded meeting or a local audio/video file uploaded afterward. A meeting may have both, only one, or neither, and you cannot infer one from the other. This is the file's central domain invariant.

Question 4

Can Minutes exist without a meeting?

Accepted Answer

Yes. Minutes can be generated directly from a local audio/video file via upload, so a minute_token is not guaranteed to map back to any meeting_id or calendar event_id. The skill's domain model is explicit: Minutes are independent of the meeting they might be linked to.

Question 5

When do I use --as user vs --as bot?

Accepted Answer

User identity covers what the logged-in user can see and do — meetings they attend, their own notes. Bot identity (--as bot) requires a target --user-id and only returns meetings where the target user is in the meeting *and* the bot is also in it. The skill's rule: once you pull an ID with one identity, keep using that identity for the rest of the chain. Switching silently is forbidden.

Question 6

Why did the bot return an empty meeting list?

Accepted Answer

Empty from bot identity does not mean the user is in no meeting — it means no meeting exists where the target user and the bot are together. The bot must actually be in the meeting to see it. The skill also forbids inferring 'user is idle' from that empty list, and warns against re-running auth checks when the real cause is permissions on the bot app.

Question 7

How do I get a transcript out?

Accepted Answer

Two routes. From Minutes: `lark-cli minutes +detail --minute-tokens obcxxx --transcript` writes a transcript file, by default to ./minutes/{minute_token}/transcript.txt — combine with --output-dir to redirect. From a unified smart note: `note +transcript`, but it only works with user identity; a bot that receives note_display_type=unified must not silently switch identity to fetch it.

Question 8

What happens if I call minutes +detail without flags?

Accepted Answer

You get base info only — the title — and none of the AI artifacts. The --summary, --todo, --chapter, --keyword, and --transcript flags are opt-in and must be passed explicitly. Request everything at once with the full flag list; batch up to 50 minute tokens comma-separated.

Question 9

How is lark-meeting different from lark-vc-agent?

Accepted Answer

[lark-vc-agent](/skills/automation/lark-vc-agent/) is a tiny compatibility shim that routes straight into lark-meeting; lark-meeting carries the actual domain model, hard rules, and scene manuals. If you installed the family, you already have lark-meeting under the hood. Install lark-meeting directly for the full routing and the six workflow manuals.

Question 10

Does it require reading lark-shared first?

Accepted Answer

No — one of the few lark-cli skills that does not mandate the pre-read. It says to touch lark-shared/SKILL.md only when you hit an auth, token, identity, or scope error. The skill ships a progressive-loading rule instead: run quick actions first, read one scene manual only when the task matches, and consult command references only when parameters are missing.

Question 11

Is the 126.9K install number real?

Accepted Answer

Yes — skills.sh on 2026-09-26 shows 126,900 all-time installs on the open.feishu.cn counter with a weekly series of 0, 0, 0, 4,845, 27,641, 27,011, 25,324, 25,744, plus 35.2K on the larksuite/cli counter (0, 0, 0, 1,413, 6,988, 7,460, 6,671, 6,602). Three zero weeks, then a launch spike to a steady ~27K/week — a newborn skill that hit the board around 2026-08-20.

Meeting on Top AI Skills

Lark-Meeting Skill FAQ: Meeting IDs, Notes, and Minutes

Frequently Asked Questions

Why a Lark-Meeting FAQ Exists