lark-vc-agent

Joins Lark video meetings as a bot and reads real-time in-meeting events.

Updated May 22, 2026
One-click install
npx skills add https://github.com/CalWade/aigc-creator --skill lark-vc-agent-calwade
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-vc-agent
Source: https://github.com/CalWade/aigc-creator/tree/main/.agents/skills/lark-vc-agent
Command: npx skills add https://github.com/CalWade/aigc-creator --skill lark-vc-agent-calwade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It lets an AI agent act as a meeting participant on your behalf in Lark (Feishu) video conferences: joining an in-progress meeting by its 9-digit meeting number, observing live in-meeting activity (who joined or left, who is speaking, chat messages, screen shares), and leaving the meeting when asked—without you manually attending. ## Core Features & Use Cases - Bot meeting join/leave: Use +meeting-join with a 9-digit meeting number (and optional password) to place the bot into a live meeting, and +meeting-leave with the returned meeting.id to exit. Both are real, visible write operations. - Real-time event timeline: Use +meeting-events to read participant joins/leaves, chat, transcripts, and screen-share events from an ongoing meeting, with automatic pagination (--page-all) and incremental pulls via page_token. - Use Case: You are double-booked. Ask the agent to join meeting 123456789, poll the event stream every 20 seconds to track who is speaking and what is shared, then after the meeting ends pull the minutes and transcript via the companion lark-vc skill and post a summary to your team chat. ## Quick Start Ask the agent to join Lark meeting 123456789 on your behalf and report what is happening in the meeting right now.

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 Lark video meeting?▼

Run lark-cli vc +meeting-join with the 9-digit meeting number, adding --password if the meeting requires one. The command only works for meetings already in progress, and the bot becomes visible to all participants immediately after joining.

How do I read real-time events from an ongoing Lark meeting?▼

Use lark-cli vc +meeting-events with the long numeric meeting_id returned by +meeting-join, plus --page-all to fetch the full visible event stream. 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 historical meetings, participant snapshots, minutes, and transcripts. Route based on whether the meeting is still in progress.

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 if you only need a participant snapshot, use vc meeting get --with-participants, which does not require bot attendance.

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

No. Only +meeting-join accepts the 9-digit meeting number. Both +meeting-events and +meeting-leave require the long numeric meeting.id returned in the join response, so record it immediately after joining.

What permissions does the Lark meeting bot need?▼

Joining and leaving require the vc:meeting.bot.join:write scope, and reading events requires vc:meeting.meetingevent:read. All commands run under user identity only, so you must complete lark-cli auth login beforehand.