CtrlK
BlogDocsLog inGet started
Tessl Logo

lark-whiteboard

飞书画板:查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。 当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责:飞书云文档内容编辑(lark-doc)、文档内嵌电子表格/Base(lark-sheets / lark-base)。

67

Quality

83%

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

78%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 a well-structured, token-efficient routing layer with explicit safety gates for destructive overwrites and clean progressive disclosure into the three reference files. It could be tightened by isolating the pinned CLI version and inlining one representative end-to-end example.

Suggestions

Move the pinned version "@larksuite/whiteboard-cli@^0.2.13" into a single version-pinning note or a dedicated prerequisites section so it is not repeated and does not clutter the decision flow.

Inline one short end-to-end example (e.g., export-then-update) directly in the body so a reader can act without opening a reference for the most common case.

DimensionReasoningScore

Conciseness

The body is lean — dense decision tables, shortcut links, and scope boundaries with no padding or explanation of concepts Claude already knows — but the pinned version "@larksuite/whiteboard-cli@^0.2.13" is time-sensitive information not placed in a deprecated section, a minor conciseness penalty per the guideline.

4 / 5

Actionability

Concrete executable commands are inlined ("+export --output-type preview", "+update --input_format mermaid / plantuml / svg") and route to reference files holding full copy-paste bash examples, but the body itself contains no complete runnable code block, leaving a minor gap.

4 / 5

Workflow Clarity

A clear read-only-vs-write routing flow with inline destructive-operation confirmation gates ("先确认会整板重建", "有损确认") is present, but the full step sequences and the 止损 feedback loop live in the workflow reference rather than the body, so most checkpoints rather than all are inline.

4 / 5

Progressive Disclosure

The body is a clean overview pointing to three real one-level-deep bundle files (export, update, workflow) via well-signaled tables and a Shortcuts section; content is appropriately split and easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

87%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 strong: third-person voice, explicit what/when, and clear boundary guidance against sibling skills. The only room for improvement is naming SVG and source-code export and adding synonyms like 白板 for broader trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ("查询和编辑飞书云文档中的画板", "导出画板为预览图片", "导出原始节点结构", "使用多种格式更新画板内容"), but SVG and Mermaid/PlantUML source-code export are not named, leaving minor gaps in coverage rather than comprehensive enumeration.

4 / 5

Completeness

Explicitly answers both what (query/edit/export/update capabilities) and when ("当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill") with concrete trigger phrases, plus an explicit out-of-scope boundary.

5 / 5

Trigger Term Quality

Natural trigger phrases a user would say are present ("查看画板内容", "导出画板图片", "编辑画板"), but synonyms such as 白板 and concrete format/extension terms (SVG, Mermaid, .svg) are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Carves a clear Feishu whiteboard niche with distinct triggers and an explicit "不负责" boundary against lark-doc, lark-sheets, and lark-base, minimizing the chance of triggering the wrong sibling skill.

5 / 5

Total

18

/

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: 1 missing, 5 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.