lark-event

Stream Lark/Feishu events as NDJSON for immediate processing.

Updated May 11, 2026
One-click install
npx skills add https://github.com/heximao/agents --skill lark-event-heximao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-event
Source: https://github.com/heximao/agents/tree/main/skill-archive/lark/lark-event
Command: npx skills add https://github.com/heximao/agents --skill lark-event-heximao

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill allows real-time event listening and subscribing for Lark/Feishu, enabling efficient and timely processing of messages, reactions, and other events.

Core Features & Use Cases

  • Real-time Event Listening: Receive stream events as NDJSON for immediate processing.
  • Event Types: Covers IM messages, VC meeting ended notifications, minutes generated, and more.
  • Use Case: Ideal for building Lark bots or integrating Lark with external systems for real-time data processing.

Quick Start

Start consuming Lark events for 'im.message.receive_v1' using the lark-cli event consume im.message.receive_v1 --as bot command.

Frequently Asked Questions about lark-event

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

FAQPage Schema
How do I listen to real-time Feishu events for immediate processing?

To listen to real-time Feishu events for immediate processing, you can stream specific event types like IM messages as NDJSON. This allows you to consume events and apply filters for timely integration.

Can I build a Lark bot that runs scripts in response to IM messages?

Yes, you can build a Lark bot that runs scripts in response to IM messages. By consuming the 'im.message.receive_v1' event type as a bot, you can trigger automated scripts for real-time message processing.

Do I need the lark-cli binary to consume Lark API events?

Yes, you need the lark-cli binary to consume Lark API events. Accessing the real-time event stream and executing commands like event consumption requires this dependency along with Lark API access.

What is the best way to filter Lark events for specific VC meeting notifications?

The best way to filter Lark events for specific VC meeting notifications is by consuming targeted event types. You can stream events such as VC meeting ended notifications and apply filters to process only the required data.

Are there limitations when subscribing to Feishu real-time event streams?

Limitations when subscribing to Feishu real-time event streams include the strict dependency on the lark-cli binary and Lark API access. Subscriptions are constrained to supported event types like IM messages and VC meeting notifications.