lark-vc-agent

Join, monitor, message, and leave in-progress Lark video meetings as an app bot.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? It lets an application bot actually join an ongoing Lark (Feishu) video meeting, read the in-meeting event stream visible to its identity, send in-meeting text messages or reaction emojis, and leave the meeting when asked, so users can delegate live meeting attendance and observation to an agent. ## Core Features & Use Cases - Bot meeting join/leave: Join an in-progress meeting by 9-digit meeting number with optional password, and leave by the long numeric meeting_id returned at join time. - In-meeting event reading: Discover active meetings via +meeting-list-active and pull participant, transcript, chat, screen-share, and document-context events with +meeting-events, with pagination and identity-continuation rules. - In-meeting messaging: Send text or reaction emojis (including VC feedback keys like VC_NoSound) into an ongoing meeting under the correct user or bot identity. - Use Case: A user says "let the bot sit in on meeting 123456789 and tell me who is speaking"; the agent joins with the bot identity, records meeting.id, polls +meeting-events with --page-all, and reports the live speaker and chat activity. ## Quick Start Ask the agent to have the app bot join meeting number 123456789 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 Lark bot join an ongoing video meeting?

Run lark-cli vc +meeting-join --as bot --meeting-number with the 9-digit meeting number, adding --password if the meeting requires one. Record the returned meeting.id immediately, since later event reads and leaving the meeting depend on it.

How to read live events from an in-progress Lark meeting?

Use lark-cli vc +meeting-events with the long numeric meeting_id and the same identity that discovered or joined the meeting. Pass --page-all by default and keep the page_token for incremental pulls; never reuse stale results for current-state questions.

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

lark-vc-agent handles real-time bot participation: joining, leaving, reading live events, and sending in-meeting messages. lark-vc handles post-meeting work like searching ended meetings, participant snapshots, minutes, transcripts, and recordings.

Why does meeting join fail with HTTP 403 no permission?

Error 121003 usually means join preconditions are unmet rather than a missing scope: wrong meeting number, missing password, meeting not started, waiting room approval pending, or the meeting blocking this identity. Verify these settings before retrying.

Can I use a 9-digit meeting number to leave or read events?

No. The 9-digit meeting number only works for +meeting-join. Event reads, message sending, and leaving require the long numeric meeting_id from the join response or from +meeting-list-active matched by meeting_no.

Which identity should I use for Lark meeting event queries?

Continue with whichever identity produced the meeting_id: --as user for meetings found as the current user, --as bot for bot-joined or bot-discovered meetings. Mixing identities causes empty results or permission errors.