lark-event

Subscribe to Feishu events via WebSocket and emit NDJSON to stdout.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Subscribes to Feishu events in real time using a WebSocket long connection, streaming NDJSON to stdout so you can build event-driven pipelines with low latency.

Core Features & Use Cases

  • Real-time event subscriptions via WebSocket long connection
  • NDJSON output to stdout for downstream processing
  • Regex routing and file output options to persist and organize events
  • Bot-only authentication and safety rules guided by lark-cli configuration

Quick Start

Start streaming events with lark-cli event +subscribe.

Frequently Asked Questions about lark-event

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

FAQPage Schema
How do I subscribe to Feishu events in real time using a WebSocket connection?

It streams Feishu event subscriptions via a WebSocket long connection, outputting NDJSON to stdout to build low-latency, event-driven pipelines for bot-driven workflows like message handling and contact updates.

How do I route and persist specific Feishu event streams to files?

You can route and persist Feishu event streams by applying regex routing rules to the NDJSON output, organizing and saving specific event types into files for downstream processing pipelines.

Do I need lark-cli and App credentials to receive Feishu event subscriptions?

Yes, operating real-time Feishu event subscriptions requires the lark-cli tool along with proper App credentials and permissions configured in the Feishu Open Platform to ensure secure bot authentication.

What downstream processing formats are supported for Feishu event data?

Feishu event data is emitted as NDJSON to stdout, allowing downstream event-driven pipelines to consume the structured stream for tasks like message handling, contact updates, and calendar changes.

Can I use this approach for bot-driven workflows like message handling and calendar changes?

Yes, this approach targets bot-driven workflows such as message handling, contact updates, and calendar changes by enabling robust event-driven pipelines and routing through the WebSocket stream.