lark-event
Installation
Summary
Stream Lark/Feishu events as NDJSON with bounded runs and subprocess-safe exit contracts.
- Consume real-time events (IM messages, reactions, chat changes, VC meetings, Minutes) via
lark-cli event consume <EventKey>, with optional jq filtering and--max-events/--timeoutbounds - Emits a stderr ready marker before stdout, supports stdin EOF for graceful shutdown, and reports exit reason (limit/timeout/signal/error) for reliable orchestration
- One EventKey per process; use
lark-cli event listandlark-cli event schemato discover keys and inspect output schemas before consuming - Requires
lark-clibinary and Lark authentication configured via lark-shared skill; avoidkill -9on processes with PreConsume hooks to prevent server-side subscription leaks
SKILL.md
Lark Events
Prerequisite: Read
../lark-shared/SKILL.mdfirst for authentication,--as user/botswitching,Permission deniedhandling, and safety rules.
Core commands
| Command | Purpose |
|---|---|
lark-cli event list [--json] |
List all subscribable EventKeys |
lark-cli event schema <EventKey> [--json] |
Show an EventKey's params and output schema |
lark-cli event consume <EventKey> [flags] |
Blocking consume; events → stdout NDJSON |
lark-cli event status [--json] [--fail-on-orphan] |
Inspect the local bus daemon status |
lark-cli event stop [--all] [--force] |
Stop the bus daemon |
Common flags
Explore more of GLSRM
