lark-vc-agent

Join and interact with live Feishu video meetings as an app bot via lark-cli.

3|2|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/zlsbksdxl/codex-lark --skill lark-vc-agent-zlsbksdxl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-vc-agent
Source: https://github.com/zlsbksdxl/codex-lark/tree/main/plugins/feishu2codex/skills/lark-vc-agent
Command: npx skills add https://github.com/zlsbksdxl/codex-lark --skill lark-vc-agent-zlsbksdxl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It lets an AI agent act inside an ongoing Feishu/Lark video meeting: joining as an app bot, reading real-time in-meeting events (joins, chat, transcripts, screen shares), sending in-meeting text or reactions, and leaving the meeting, all through lark-cli commands. ## Core Features & Use Cases - Bot meeting participation: Join an in-progress meeting by 9-digit meeting number with +meeting-join, and leave with +meeting-leave when the user explicitly asks. - Live event awareness: Discover active meetings with +meeting-list-active and stream participant, chat, transcript, and share events with +meeting-events, with pagination and identity-continuation rules. - In-meeting messaging: Send text messages or reaction emoji (including VC feedback keys like VC_NoSound) with +meeting-message-send. - Use Case: A user asks "let the bot sit in on meeting 123456789 and tell me who is speaking". The agent joins the meeting, records the returned meeting.id, polls +meeting-events --page-all, and reports the live timeline. ## Quick Start Ask the agent to join the ongoing Feishu meeting with your 9-digit meeting number 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 Feishu video meeting?

Run `lark-cli vc +meeting-join --as bot --meeting-number <9-digit number>` with the app identity. The meeting must be in progress, and you must record the returned `meeting.id` for later event reads or leaving the meeting.

How to read live events from an ongoing Lark meeting?

Use `lark-cli vc +meeting-events --meeting-id <id> --page-all --format pretty` with the same identity that discovered the meeting. The meeting_id must be the long numeric ID, not the 9-digit meeting number.

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

lark-vc-agent handles in-meeting actions: joining, reading live events, sending messages, and leaving. lark-vc handles post-meeting queries such as historical meeting search, participant snapshots, minutes, transcripts, and recordings.

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

Error 10005 means the app bot never actually joined that meeting, or the meeting ended beyond the 5-minute grace window. Either join the meeting first with +meeting-join, or use the user identity if the meeting_id came from user-side discovery.

Can I send reactions or feedback emoji inside a Feishu meeting?

Yes, use `+meeting-message-send --msg-type reaction --emoji-type <key>`. Keys are case-sensitive and must come from the documented list, which includes standard Feishu reactions plus VC feedback keys like VC_NoSound and VC_CanNotSee.

Does a 9-digit meeting number work as meeting_id?

No. Commands like +meeting-events, +meeting-message-send, and +meeting-leave require the long numeric meeting_id. Match the 9-digit number against `meeting_no` in +meeting-list-active results to obtain the correct meeting_id.