lark-event

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

3|1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/HuXiangyu123/CUA-Lark-Agent --skill lark-event-huxiangyu123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-event
Source: https://github.com/HuXiangyu123/CUA-Lark-Agent/tree/main/lark-cli/skills/lark-event
Command: npx skills add https://github.com/HuXiangyu123/CUA-Lark-Agent --skill lark-event-huxiangyu123

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Subscribes to Feishu events over a persistent WebSocket connection and streams NDJSON to stdout for downstream processing, enabling real-time event-driven workflows without polling.

Core Features & Use Cases

  • Real-time event subscription via a long-lived WebSocket
  • NDJSON streaming to stdout, with optional compact formatting and routing
  • Output to files or in-memory pipelines using regex-based routing and flexible parameters

Quick Start

Start the lark-cli event +subscribe command to begin live event streaming and routing for your bot workflows.

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 without polling?

To subscribe to Feishu events in real time, this Skill uses a persistent WebSocket long connection to stream NDJSON directly to stdout, enabling event-driven workflows without polling. It supports messages, contacts, and calendar changes.

Can I filter specific Feishu event types for my bot pipeline?

Yes, you can filter specific Feishu event types using the --event-types option. This allows you to restrict the NDJSON stream to only relevant events for your deterministic bot workflows.

Does Feishu event subscription via WebSocket require any specific dependencies?

Yes, Feishu event subscription requires the lark-cli binary to run. It operates in bot-only mode and uses a WebSocket long connection to stream NDJSON output.

What is the best way to route Feishu NDJSON streams to files or pipelines?

The best way to route Feishu NDJSON streams is using the --route option with regex matching and --output-dir for file output. This allows flexible routing of real-time events to in-memory pipelines or deterministic file storage.

How do I get compact NDJSON output from Feishu WebSocket subscriptions?

You can get compact NDJSON output from Feishu WebSocket subscriptions by passing the --compact option. This reduces the formatting of the streamed events to fit your downstream processing needs.