CtrlK
BlogDocsLog inGet started
Tessl Logo

lark-event

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.

72

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-structured, with executable commands, explicit validation checkpoints, and a clean topic-index pointing to real per-domain reference files. It is dense in places, which slightly limits conciseness but does not undermine clarity.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence — no preamble explaining what events or NDJSON are — with dense but earned prose in the subprocess-contract and jq sections; a few passages could be tightened further.

4 / 5

Actionability

Fully executable: copy-paste bash examples, exact `lark-cli` commands, a precise stderr ready-marker line, and a complete exit-code/reason table covering the common run cases.

5 / 5

Workflow Clarity

A clear 3-step call flow (list → schema → consume) with explicit validation signals (unknown domain fails with the valid set; block on the ready marker, never sleep; parse the error envelope, not message text) and an exit-code table that forms an error-recovery feedback loop.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview with a well-signaled one-level-deep topic index pointing to seven real reference files in ./references/ (verified present), each summarized with its coverage scope for easy navigation.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinct, explicitly answering both what the skill does and when to use it with concrete trigger phrases and a named tool. The only minor gap is a few trigger terms being somewhat technical rather than naturally conversational.

Suggestions

Consider leading with one plain-language use case before the tool/command detail so a user scanning descriptions latches onto the intent faster.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — stream events as NDJSON via `lark-cli event consume <EventKey>`, subscribe/consume, bounded runs, stderr ready-marker — and enumerates covered event domains, giving comprehensive coverage.

5 / 5

Completeness

Explicitly states both what it does (stream events as NDJSON via the named command across listed domains) and when to use it ('Use for Lark bots, real-time message processing...'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural phrases users would say ('Lark bots', 'real-time message processing', 'long-running subscribers', 'streaming webhook/push handlers'), though some terms lean technical rather than colloquial.

4 / 5

Distinctiveness Conflict Risk

A clear niche — Lark/Feishu real-time event streaming via lark-cli with subprocess semantics — with specific trigger terms and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

12

/

16

Passed

Repository
larksuite/cli
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.