lark-event

Subscribe to Feishu events via WebSocket and stream them as NDJSON.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of reliably capturing Feishu (Lark) events in real time so you can turn them into an event-driven workflow instead of polling or manual monitoring.

Core Features & Use Cases

  • Real-time WebSocket event subscription: Listens via long connection and streams events as NDJSON to stdout for downstream processing.
  • Agent-friendly routing and output shaping: Supports compact format, regex-based routing to different destinations, and optional pretty-printed JSON output.
  • Event-driven automation: Enables building pipelines for reacting to message events, contact changes, calendar updates, and other subscribed event types.

Quick Start

Use the lark-event skill to subscribe to message events and continuously print compact, quiet NDJSON for agent consumption.

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 over a WebSocket connection?

To subscribe to Feishu events in real time, use a WebSocket long connection with bot-only authentication via App ID and App Secret. It streams events as NDJSON to stdout for immediate pipeline processing.

Can I filter or route specific Feishu message events using regex?

Yes, you can filter and route Feishu message events using optional regex-based routing. This allows directing specific event types to different destinations for targeted real-time automation pipelines.

What is the best way to capture Feishu contact and calendar changes for automation?

The best way to capture Feishu contact and calendar changes is subscribing to event types over a WebSocket long connection. It outputs one-event-per-line NDJSON, enabling incremental consumption for event-driven automation.

Do I need a user token to consume Feishu events as NDJSON?

No, you do not need a user token to consume Feishu events as NDJSON. The subscription requires bot-only authentication using your application's App ID and App Secret to establish the connection.

How does NDJSON streaming format work for real-time IM message monitoring?

NDJSON streaming for real-time IM monitoring outputs one event per line to stdout. This compact, agent-friendly structure allows downstream pipelines to incrementally consume and process incoming message payloads.

Are there limitations when using WebSocket event subscriptions for Feishu automation?

WebSocket event subscriptions for Feishu automation require bot-only authentication and optional event-type registration. Limitations include needing sustained connections and proper payload handling for incremental event consumption.