lark-event Skill for Claude: Stream Real-Time Lark and Feishu Events

Lets Claude listen to live Lark or Feishu events, such as new chat messages, approvals and meetings, as a stream through lark-cli.

Installs: 472.4K; on skills.sh
Stars: 17.9K; on GitHub
Files: 7; besides SKILL.md
Updated: Oct 2026; last repo commit

lark-event teaches Claude to use lark-cli event consume <EventKey>, which prints each event as one line of JSON. Event types cover chat messages, reactions and chat changes, approvals, task updates, video meeting start, join and end, meeting notes and recordings, minutes, and whiteboard updates. It loads for bots, real-time message handling and long-running subscribers.

The command blocks until it is stopped, so SKILL.md shows how to bound a run with --max-events or --timeout, and how to filter events with a --jq expression. It uses a shared local bus daemon, which lark-cli event status inspects and lark-cli event stop stops. SKILL.md says to end a consume process with SIGTERM or by closing stdin, not kill -9, which can leak a server-side subscription. It needs lark-cli and a signed-in account.

Good for

Developers building Lark bots that react to messages in real time
Teams that want an agent to watch approvals, task updates or meeting events
Anyone running a long-lived event subscriber from a script

Install lark-event

Claude Code

Copy this prompt.

Install the lark-event skill in Claude Code. Run this command:

npx @larksuite/cli@latest install

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

This skill only gives Claude instructions for the lark-cli command line, so install the CLI first, then the skills, then sign in. The skills command adds the whole larksuite/cli set, which includes lark-shared, the skill this one reads first for sign-in and permissions.

From the project README. Source.

What's in the skill

When it loads

Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.

Sections in SKILL.md

Core commands
Common flags
Examples
Call flow
Subprocess contract
Ready marker
stdin EOF = graceful exit
Exit codes & reason
Never kill -9
One consume, one EventKey (multi-key = multi-shell)
Writing jq via schema
Topic index

Key facts

Author: Lark Suite (larksuite)
Repository: larksuite/cli, folder skills/lark-event
Installs on skills.sh: 472,378 as of 2026-11-02
GitHub stars: 17,911 for the whole larksuite/cli repo, 2026-11-02
License: MIT
Last repo commit: 2026-10-30
What is inside: 7 bundled reference pages besides SKILL.md, one per event area; no scripts
skills.sh audits: Gen Agent Trust Hub: pass, Socket: pass, Snyk: warn

What it includes

Lists every event type you can subscribe to
Can narrow to one area such as im, task or vc.
Network · event list
Shows an event's options and output fields
Claude reads it before it writes a filter.
Read · event schema
Streams events as lines of JSON until stopped
Supports --max-events, --timeout, --jq and --output-dir. Blocks until it ends, and an unbounded run also exits when stdin closes.
Try: “Watch new messages in this chat for ten minutes and list who wrote.”
Runs code · event consume
Shows the local background process
Has a --fail-on-orphan flag for a leftover daemon.
Read · event status
Stops the local bus daemon
Takes --all and --force.
Runs code · event stop
Seven guides: application, approval, IM, task, VC, minutes, whiteboard
Each lists the event types and their fields.
Read · Event area guides

From the official docs

Permissions

Medium risk

The skill starts a live listener that can feed real chat and meeting content into the conversation. Limit each run with a timeout and stop the background process when done.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It acts as you in Lark after you sign in
The repo README warns that the agent works under your user identity within the authorized scope. Grant only the scopes you need and read commands before you approve them. github.com
Chat messages can stream into the conversation
Message and meeting events carry real content. Subscribe only to the events you need and set a time limit. github.com
A consume run goes on until a limit or a stop
Bound each run with --timeout or --max-events. SKILL.md says to end a consume process with SIGTERM or by closing stdin, because kill -9 can leak a server-side subscription. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details

Turning on read-only	The skill has no read-only switch. Sign in with a narrow scope list, for example lark-cli auth login --domain <name>, so the agent cannot reach more than you intend.
Talks to	Lark/Feishu Open Platform API calls made by lark-cli. Your AI provider receives whatever Claude reads from Lark. A live connection to Lark for the events you subscribe to
Sign-in and keys	lark-cli stores credentials in the OS keychain, per the repo README.
Scopes	Claude runs lark-cli commands in your terminal After you sign in, commands run as your Lark or Feishu user within the permissions you granted Starts a long-running local process that listens for events Can write each event to files in an output folder you name

Questions

How do I install lark-event?

Use the install box at the top of this page. The box lists three steps: install the Lark CLI, add the Lark skills, then set up an app and sign in. The skill is only instructions, so Claude cannot use it until lark-cli is installed and you are signed in.

Do I need a Lark account to use lark-event?

Yes. You need a Lark or Feishu account, plus an app set up with lark-cli config init. The README then has you sign in with lark-cli auth login --recommend. There is no separate API key to paste.

What kinds of events can it listen to?

SKILL.md covers eight areas: application bot menus, approvals, chat (IM), tasks, video meetings, minutes, whiteboards and cards. Run lark-cli event list to see the current list.

Does it keep running after the chat ends?

It can. lark-cli event consume blocks until it is stopped, and it uses a shared local bus daemon. SKILL.md says an unbounded run also exits when stdin closes. Bound runs with --timeout or --max-events, and end a consume process with SIGTERM or by closing stdin, not kill -9.

Is lark-event safe?

Use it with care. Events can include the text of your chats, so a busy stream can pull private messages into the conversation. The repo README warns that after you authorize Lark permissions the agent acts under your user identity and that model mistakes or prompt injection can cause real changes.

Information

updated Nov 2, 2026

Repository: larksuite/cli
Folder: skills/lark-event

larksuite/cli skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 3

larksuite/cli README · github.com
lark-event SKILL.md · github.com
lark-skill-maker SKILL.md · github.com