lark-vc-agent

Joins and leaves live Feishu video meetings as a bot and reads real-time in-meeting events.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/sliec/shared-files --skill lark-vc-agent-sliec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-vc-agent
Source: https://github.com/sliec/shared-files/tree/main/skills/lark-vc-agent
Command: npx skills add https://github.com/sliec/shared-files --skill lark-vc-agent-sliec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lark-cli, and includes references (resource) components.

What problem does it solve? It lets an AI agent act as a meeting participant on your behalf: joining an in-progress Feishu (Lark) video meeting by its 9-digit meeting number, observing live in-meeting activity such as who joined, who left, who is speaking, chat messages, and screen shares, and leaving the meeting when the task is done. ## Core Features & Use Cases - Bot Meeting Join/Leave: Join an ongoing meeting with +meeting-join using a 9-digit meeting number (and optional password), then leave with +meeting-leave using the returned meeting ID. - Real-Time Event Timeline: Read live meeting events with +meeting-events, including participant joins/leaves, transcripts, chat, and screen sharing, with automatic pagination and incremental page_token continuation. - Use Case: Ask the agent to sit in on a standup meeting, monitor who speaks and what is shared during the call, then leave and hand off to lark-vc or lark-minutes to pull the meeting notes and send a summary to a group chat via lark-im. ## Quick Start Ask the agent to join Feishu meeting 123456789 on your behalf, watch the live event stream, and leave when finished.

Frequently Asked Questions about lark-vc-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make a bot join a Feishu video meeting?

Run lark-cli vc +meeting-join with the 9-digit meeting number, adding --password if the meeting requires one. The meeting must be in progress, and the returned meeting.id must be saved for later event queries and leaving.

How do I read live events from an ongoing Feishu meeting?

Use lark-cli vc +meeting-events with the long numeric meeting ID, plus --page-all and --format pretty. The bot must currently be in the meeting, or have been in it within 5 minutes after it ended.

What is the difference between lark-vc and lark-vc-agent?

lark-vc-agent handles in-meeting actions: joining, reading live events, and leaving. lark-vc handles post-meeting queries such as searching past meetings, participant snapshots, notes, transcripts, and recordings.

Why does +meeting-events return error 10005 bot is not in meeting?

Error 10005 means the bot never actually joined that meeting, so no event stream is visible. Join first with +meeting-join, or use vc meeting get --with-participants for a participant snapshot that does not require bot attendance.

Can I use the 9-digit meeting number for +meeting-leave or +meeting-events?

No. Both commands require the long numeric meeting ID returned by +meeting-join, not the 9-digit meeting number. Passing the meeting number causes errors such as 20002 meeting not exist.

What permissions does the Feishu meeting bot need?

Joining and leaving require the vc:meeting.bot.join:write scope, and reading events requires vc:meeting.meetingevent:read. The feature is in beta, so permission errors may mean you need to join the early-access group instead of requesting scopes.