lark-event

Stream real-time Lark/Feishu events to AI agents via lark-cli event consume.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/x0chaoren0s/agent-platform --skill lark-event-x0chaoren0s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lark-event
Source: https://github.com/x0chaoren0s/agent-platform/tree/main/skills/lark-event
Command: npx skills add https://github.com/x0chaoren0s/agent-platform --skill lark-event-x0chaoren0s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Real-time event streams from Lark/Feishu enable AI agents to react to messages, reactions, and chat member changes without polling.

Core Features & Use Cases

  • Real-time event streaming from Lark/Feishu to AI agents via a consumable interface.
  • Supports blocking, bounded runs with a ready-marker contract for subprocess usage.
  • Use case: Activate a long-running subscriber to process im.message.receive_v1 events and trigger downstream tasks.

Quick Start

Use the lark-cli event consume im.message.receive_v1 --as bot

Frequently Asked Questions about lark-event

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

FAQPage Schema
How do I stream real-time Lark events to an AI agent?▼

Stream real-time Lark events to AI agents by running lark-cli event consume, which pushes live updates such as messages and reactions directly to your bot workflow without polling.

What types of Feishu events can I capture for a long-running bot workflow?▼

You can capture Lark events including IM messages (im.message.receive_v1), reactions, and chat member changes, with EventKeys ranging from message receipts to chat updates for continuous bot processing.

How do I subscribe to Lark message events via the command line?▼

Subscribe to Lark message events by executing lark-cli event consume im.message.receive_v1 --as bot, which initiates a blocking, bounded run to receive and process real-time event streams.

Can I limit the number of Lark events consumed or set a timeout?▼

You can bound your Lark event consumption using the --max-events and --timeout flags, enforcing a subprocess-ready contract with readiness semantics to safely control long-running stream durations.

Do I need to configure authentication before consuming Lark event streams?▼

Yes, consuming Lark event streams assumes you have already configured the authentication and safety rules described in the shared LARK skills before executing the lark-cli event consume command.