CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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, Drive doc comment notices, 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.

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 an excellent CLI-skill reference: dense, tool-specific tables and executable examples with zero filler; a clear three-step call flow; and a subprocess contract (ready marker, stdin EOF semantics, exit codes, JSON error envelopes) that doubles as validation and error-recovery guidance. Domain specifics are correctly deferred to eight real, one-level-deep reference files indexed with per-file coverage summaries.

DimensionReasoningScore

Conciseness

Every section carries lark-cli-specific knowledge Claude cannot already know (custom flags, the subprocess contract, pre-decoded payload behavior), delivered via dense tables and terse prose — e.g. the exit-code table and "any jq runtime error skips the event with a one-line WARN; the loop does not abort". No concept explanations or padding; matches the 5 anchor ('every token earns its place') rather than 4, which requires instances of over-explanation.

5 / 5

Actionability

All examples are copy-paste executable ("lark-cli event consume im.message.receive_v1 --max-events 1 --timeout 30s --as bot", the multi-process background pattern with `wait`), the ready marker is given verbatim ("[event] ready event_key=<key>"), and failure handling names exact fields to branch on ("Parse `error.type` / `error.subtype` to branch... do not regex-match message text"). Fully executable per the 5 anchor with no pseudocode or missing steps.

5 / 5

Workflow Clarity

A numbered call flow (list → schema → consume) plus a rigorous subprocess contract with explicit validation checkpoints: block on the stderr ready marker ("Do not fall back to `sleep`"), an exit-code/reason table, structured error envelopes whose `error.hint` gives "the recovery action", and completion semantics ("treat `reason: limit/timeout/signal` (all exit 0) as 'business completion'"). Self-correcting failures (unknown key/domain/param fail with the valid values listed inline) provide the error-recovery feedback loops of the 5 anchor; the 4 anchor's 'minor validation gaps' do not apply, and no destructive/batch cap is triggered.

5 / 5

Progressive Disclosure

SKILL.md is a true overview: commands, flags, the subprocess contract, and cross-cutting jq/schema guidance stay inline, while per-domain detail is split into 8 one-level-deep reference files — all verified to exist and be substantive (38–170 lines each) — surfaced through a topic-index table that describes each file's coverage. This matches the 5 anchor (clear overview with well-signaled one-level-deep references); the cross-skill pointers (../lark-shared, ../lark-im) are see-also navigation to sibling skills, not nested content within this bundle.

5 / 5

Total

20

/

20

Passed

Description

100%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 exemplary: it names the exact command and output format, enumerates the covered event domains, provides an explicit 'Use for' clause full of natural trigger phrases with synonyms (Lark/Feishu, listen/subscribe/consume, webhook/push), and occupies a clearly distinct niche. Both 'what' and 'when' are answered explicitly and concretely, with no vague or padded language.

DimensionReasoningScore

Specificity

Concrete actions throughout: "real-time event listening / subscribing / consuming", "stream events as NDJSON via `lark-cli event consume <EventKey>`", with enumerated coverage (IM messages/reactions/chat changes, Approval status changes, VC meeting started/joined/ended, etc.) and flag-level details. Matches the 5 anchor (multiple specific concrete actions, comprehensive coverage); the 4 anchor's 'minor gaps in coverage' do not apply.

5 / 5

Completeness

Explicitly answers both questions: 'what' — "stream events as NDJSON via `lark-cli event consume <EventKey>`" with the event-domain list — and 'when' — "Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers". This is the 5-anchor pattern (explicit what AND when with concrete trigger phrases); the explicit 'Use for' clause also avoids the missing-trigger cap at 3.

5 / 5

Trigger Term Quality

Natural trigger phrases a user would actually say: "Lark/Feishu" (both product names), "listening / subscribing / consuming" (three verb synonyms), "Lark bots", "real-time message processing", "long-running subscribers", "streaming webhook/push handlers". Synonym coverage is comprehensive per the 5 anchor; not 4, since no common variation (Lark vs Feishu, webhook vs push, listen vs subscribe vs consume) is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche — Lark/Feishu real-time event consumption — with distinct triggers (subscribe, consume, stream, subscriber, NDJSON, webhook) that would not naturally fire for message-sending or generic file/document skills. Minimal conflict risk per the 5 anchor; a 4 would require noticeable overlap with a closely related skill, and the scoping verb triple ('listening / subscribing / consuming') disambiguates from adjacent Lark skills.

5 / 5

Total

20

/

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.

Validation — 12 / 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

Path

skills/lark-event/SKILL.md

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.