lark-event

Stream Feishu/Lark events as NDJSON via a WebSocket long connection.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/binfen1/my-skills --skill lark-event-binfen1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-event
Source: https://github.com/binfen1/my-skills/tree/main/claude-code/lark-event
Command: npx skills add https://github.com/binfen1/my-skills --skill lark-event-binfen1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Real-time Feishu/Lark event subscriptions via a WebSocket long connection stream events as NDJSON to stdout, enabling immediate integration into pipelines and monitoring.

Core Features & Use Cases

  • Real-time event streaming via a long-lived WebSocket connection
  • Output NDJSON to stdout for straightforward downstream processing
  • Agent-friendly formatting with optional regex routing and selective file outputs
  • Supports a broad range of event types (messages, calendar, contacts) via lark-cli

Quick Start

Install lark-cli, configure authentication, and start subscribing to events with a single command.

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 Lark events in real-time via WebSocket?

You can subscribe to real-time Lark events via a WebSocket long connection to stream messages, calendar, and directory changes directly as NDJSON to stdout for immediate pipeline integration. This requires lark-cli and proper authentication.

What is the best way to stream Feishu bot events to an NDJSON pipeline?

Streaming Feishu bot events to an NDJSON pipeline is best handled through a WebSocket long connection that outputs agent-friendly NDJSON to stdout, with options for regex routing and selective file outputs to manage downstream processing.

Do I need lark-cli to receive real-time Feishu messages via WebSocket?

Yes, you need lark-cli installed and configured with proper authentication and permissions to receive events. It establishes the WebSocket long connection required to stream Lark events safely in a read-only consumption model.

Can I filter or route specific Feishu event types when streaming to stdout?

Yes, you can filter Feishu event streams using optional regex routing to direct specific events. This allows selective file outputs and compact formatting to ensure only relevant NDJSON events are processed downstream.

Are there limitations to processing Lark events via a WebSocket long connection?

Processing Lark events via WebSocket is designed for safe, read-only consumption. Limitations include the need for proper authentication permissions and dependency on lark-cli to maintain the long-lived connection for streaming NDJSON event data.