lark-event

Capture real-time Lark platform events via WebSocket long connection with NDJSON output.

14|4|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/SpaceZephyr/allSkills --skill lark-event-spacezephyr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-event
Source: https://github.com/SpaceZephyr/allSkills/tree/main/lark-event
Command: npx skills add https://github.com/SpaceZephyr/allSkills --skill lark-event-spacezephyr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Users building Lark event-driven automation workflows need a reliable, low-effort way to capture real-time platform events (such as incoming messages, contact updates, and calendar changes) without building and maintaining custom WebSocket connection logic, which this Skill eliminates by providing a pre-configured, production-ready event listener.

Core Features & Use Cases

  • Pre-configured WebSocket Event Subscription: Connects to Lark's event push service via long connection out of the box, supporting 24+ common event types in catch-all mode or custom event type filtering.
  • Flexible Output & Routing: Supports compact agent-friendly NDJSON format, regex-based event routing to separate directories, and individual file output for archival or downstream processing.
  • Use Case: Build automation pipelines such as auto-replying to user messages, logging calendar event changes to Lark documents, or syncing contact updates to internal HR systems without writing custom WebSocket handling code.

Quick Start

Use the lark-event skill to subscribe to all incoming Lark message events in compact agent-friendly format and pipe the output to a script that auto-replies to user messages.

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 real-time Lark events via WebSocket without manual polling?▼

To subscribe to real-time Lark events via WebSocket without manual polling, you use a pre-configured event listener that establishes a long connection. This automatically captures messages, contact changes, and calendar updates, eliminating custom WebSocket implementation.

What is the best way to capture Lark platform events for an automated reply workflow?▼

The best way to capture Lark platform events for automated reply workflows is using a catch-all event subscription via WebSocket. It outputs NDJSON formatted data, which can be directly piped to downstream scripts for seamless automated message processing and replies.

Can I filter specific Lark event types and route them to separate directories?▼

Yes, you can filter specific Lark event types and route them to separate directories using regex-based event routing. This allows individual file output for targeted downstream processing or archival within your automation pipelines.

Does the Lark event subscription support NDJSON output for automation pipelines?▼

Yes, the Lark event subscription supports NDJSON output for automation pipelines. It provides a compact, agent-friendly data formatting that ensures seamless integration with downstream scripts and cross-system event synchronization tasks.

Do I need custom WebSocket connection logic to sync Lark contact updates to HR systems?▼

No, you do not need custom WebSocket connection logic to sync Lark contact updates to HR systems. A pre-configured event listener handles the long connection automatically, providing real-time event data ready for cross-system synchronization.