CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lark-meeting

飞书视频会议:查询会议记录与会议产物(纪要/逐字稿/妙记)、妙记搜索/上传/下载/编辑、机器人参与会议;查询进行中的会议、实时会议内容(发言/聊天/共享文档)问答(会上/会里)、发送会中聊天/表情;基于 meeting_id、meeting_no、event_id、note_id、minute_token、vc-node-id 或妙记 URL 查询相关信息。预约会议、忙闲和会议室管理走 lark-calendar。

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

90%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.

A dense, well-orchestrated skill body: executable commands with exact flags, an unambiguous identity-state workflow, and a genuinely progressive loading design that keeps the overview lean. The main gaps are validation checkpoints delegated to scene files and the absence of the referenced scenes/ files (and cross-skill lark-drive references) from the bundle, which weakens the otherwise excellent navigation layer.

Suggestions

Ship the six scenes/*.md handbooks (and the two ../lark-drive reference targets) with the bundle, or inline a minimal fallback flow for each scene in SKILL.md, since the body routes most non-quick-action tasks to them.

Surface one or two explicit verification checkpoints for write operations in the body itself (e.g. confirm meeting_id and participant list before `vc +meeting-end` or `drive +member-add`) rather than relying solely on the scene handbooks.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: no explanation of what Feishu, meetings, or calendars are; the domain-model diagram and table carry only non-obvious internal relationships (note_display_type branches, meeting_note vs AI 纪要, verbatim normal/unified). Every section adds CLI-specific or routing knowledge Claude could not infer, matching 'every token earns its place'.

5 / 5

Actionability

快速行动 gives copy-paste-ready commands with exact flags ("lark-cli vc +meeting-list-active --as bot --user-id <open_id>", "lark-cli vc +meeting-events --as <source_identity> --meeting-id <meeting_id> --page-all --format pretty"), and the command table maps all 26 commands to a concrete lookup path (a specific references/*.md file or an exact `lark-cli ... --help` invocation). The identity procedure is fully concrete decision logic, not vague direction.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced: numbered identity-selection with explicit stop conditions ("不支持:说明限制并停止"), a 3-step conditional 渐进加载规则, a multi-meeting disambiguation rule, and an auth-error feedback loop ("遇到未认证…读取该 Skill,修复后重试"). Falls short of 5 because explicit validation checkpoints for write operations (end meeting, permission changes, minutes edits) are delegated to scene-handbook files rather than shown, leaving the in-body checkpoints mostly for read and routing flows.

4 / 5

Progressive Disclosure

Exemplary one-level-deep design: quick action inline, six clearly-signaled scene handbooks, a per-command reference table, and an explicit progressive-loading rule section; all 22 references/*.md files referenced in the command table exist in the bundle and contain substantive content (verified). Held at 4 rather than 5 because the six scenes/*.md handbooks — the primary flow layer the body routes most tasks to — plus two ../lark-drive references are not present in the bundle, so the prescribed navigation path dead-ends for non-quick-action tasks (the --help fallback in loading rule 3 partially mitigates this).

4 / 5

Total

18

/

20

Passed

Description

75%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.

A highly specific, well-scoped description that names concrete capabilities across the whole Feishu video-meeting domain and cleanly separates itself from lark-calendar. Its main weakness is the absence of an explicit 'Use when' trigger clause, which caps completeness, and a few missing natural synonyms (转写/录制/回放).

Suggestions

Add an explicit trigger clause, e.g. "当用户提到飞书会议、会议纪要、逐字稿、妙记或正在开会时使用" — this would lift completeness from 3.

Include common user-side synonyms for Minutes/transcript artifacts such as "转写"、"文字记录"、"录制"、"回放" to strengthen trigger-term coverage.

Optionally extend the routing sentence to other adjacent skills (e.g. 纪要文档正文编辑、云空间文件) the way it already does for lark-calendar.

DimensionReasoningScore

Specificity

The description lists many concrete actions — "查询会议记录与会议产物(纪要/逐字稿/妙记)", "妙记搜索/上传/下载/编辑", "机器人参与会议", "查询进行中的会议", "发送会中聊天/表情" — covering query, edit, live interaction, and bot attendance comprehensively. It exceeds the 'minor gaps' level of a 4 because coverage spans the entire domain, not just several actions.

5 / 5

Completeness

The 'what' is explicit and rich (查询/搜索/上传/下载/编辑/发送 across meetings, Minutes, and notes), but the 'when' is only weakly implied: "基于 meeting_id、meeting_no、event_id、note_id、minute_token、vc-node-id 或妙记 URL 查询相关信息" describes inputs, not invocation triggers, and "预约会议、忙闲和会议室管理走 lark-calendar" routes away without stating when to use this skill. Per the guideline, a missing 'Use when...' clause or equivalent explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural-keyword coverage: "会议记录", "纪要/逐字稿/妙记", "进行中的会议", "会中聊天/表情", plus the explicit synonym pair "(会上/会里)" and concrete forms like 妙记 URL. Not 5 because common user variations such as "转写", "录制", and "回放" are absent; not 3 because coverage goes well beyond 'some relevant keywords' with synonyms and identifier-level triggers.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (飞书视频会议 and its artifacts) with distinct triggers and explicitly de-conflicts the nearest neighbor: "预约会议、忙闲和会议室管理走 lark-calendar". The concrete identifier list (meeting_id, minute_token, vc-node-id, 妙记 URL) makes wrong-skill triggering minimal — better than the 'minor overlap risk with closely related skills' of a 4.

5 / 5

Total

17

/

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: 6 missing, 3 suspicious

Warning

Total

12

/

16

Passed

Repository

larksuite/cli

Path

skills/lark-meeting/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.