What problem does it solve? It lets an application bot actually join an ongoing Feishu/Lark video meeting, observe what is happening inside it in real time, send in-meeting text messages or reaction emojis, and leave when asked, without confusing these live actions with post-meeting queries. ## Core Features & Use Cases - Bot meeting join/leave: Join an in-progress meeting by 9-digit meeting number with --as bot, capture the returned long meeting.id, and leave only when the user explicitly asks. - Live event reading: Pull the in-meeting event stream (participant join/leave, chat, transcript, screen share) via +meeting-events with --page-all, keeping identity consistent with how the meeting_id was discovered. - In-meeting messaging: Send text or reaction emojis (including VC feedback keys like VC_NoSound) into an ongoing meeting. - Active meeting discovery: Use +meeting-list-active with user or bot identity to find the long meeting_id matching a 9-digit meeting number. - Use Case: A user says "let the bot sit in on meeting 123456789 and tell me who is speaking". The skill joins the meeting as the app bot, records meeting.id, polls +meeting-events, and reports the live timeline; post-meeting minutes are routed to the lark-vc skill instead. ## Quick Start Ask the assistant to join Lark meeting 123456789 as the app bot and report what is currently happening in the meeting.