CtrlK
BlogDocsLog inGet started
Tessl Logo

lark-note

飞书会议纪要(Note)直查:已知 note_id 时查询纪要详情、展示类型、关联文档 token,并读取 unified 原始逐字记录。当用户已持有 note_id,或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取。

77

Quality

100%

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%

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

A well-structured, information-dense skill body that routes the agent through concrete commands and clear decision tables while offloading detail to genuinely present reference files. It is concise, actionable, and easy to navigate.

DimensionReasoningScore

Conciseness

Lean routing tables and field definitions with no padding; the 核心概念 section defines Feishu-specific internals Claude would not already know, which is appropriate rather than verbose.

3 / 3

Actionability

Concrete, copy-ready lark-cli commands throughout (note +detail --note-id, vc +detail --meeting-ids, docs +fetch) plus a worked bash example, fully executable rather than descriptive.

3 / 3

Workflow Clarity

The command-routing and note_display_type tables sequence multi-step lookups with explicit decision branches; operations are read-only, so the destructive/batch validation cap does not apply.

3 / 3

Progressive Disclosure

Two real one-level-deep references (lark-note-detail.md, lark-note-transcript.md, both present) are surfaced via a Shortcuts table that states when to read each, with the body kept as an overview.

3 / 3

Total

12

/

12

Passed

Description

100%

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 precise, third-person description that pairs concrete capabilities with an explicit use-trigger and sharp exclusions. It is concise yet complete and unlikely to be invoked for the wrong skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('查询纪要详情、展示类型、关联文档 token,并读取 unified 原始逐字记录') rather than vague domain labels, matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly states what it does and includes an explicit '当...时使用' trigger clause plus exclusions, cleanly answering both what and when.

3 / 3

Trigger Term Quality

Covers natural domain terms (飞书会议纪要, 纪要详情, 逐字记录) alongside the routing triggers (note_id, vc-node-id) that a user/agent would actually invoke this skill with.

3 / 3

Distinctiveness Conflict Risk

The '不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取' clause carves out a clear niche and rules out overlap with sibling skills.

3 / 3

Total

12

/

12

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: 10 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.