CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lark-doc

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;`/page/<token>` 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。

Quality

82%

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

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

An exemplary router-style SKILL.md: maximally token-efficient, unambiguous scenario routing to real per-task reference files, and explicit boundary and fallback rules. The only deductions are second-level reference nesting in the bundle and executable command detail living in references rather than the body.

DimensionReasoningScore

Conciseness

The body is a dense, imperative router with zero concept explanation and no padding — every line is a behavioral directive (routing, fallback rules, guardrails), fully assuming Claude's competence. Leaner than the anchor-5 example is hard to achieve for a multi-scenario skill.

5 / 5

Actionability

Gives exact shortcut names (+fetch, +update, +media-insert, +history-revert), concrete commands (lark-cli drive files copy, whiteboard +update, --as user, auth status --verify), and one reference per scenario. Not a 5 because copy-paste command syntax for the core operations is delegated to the reference files rather than shown in the body.

4 / 5

Workflow Clarity

Clear sequencing (先判断场景 → read that scenario's reference once → execute), ordered file-resolution fallback rules, an explicit auth error → read lark-shared → fix → retry feedback loop, and a whiteboard guardrail (必须复用现有 token,禁止新建空白画板). Minor validation gaps remain in the body for edit and history-revert flows, which are left to the references.

4 / 5

Progressive Disclosure

A lean overview routing each scenario to exactly one clearly labeled reference file, all 12 of which exist in the bundle, plus an explicit instruction to read references per-phase rather than upfront. Not a 5 because the bundle has second-level nesting (lark-doc-update.md → lark-doc-xml.md → lark-doc-xml-extended-blocks.md), so some detail sits two-to-three hops from SKILL.md.

4 / 5

Total

17

/

20

Passed

Description

78%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 strong description: concrete capability list, an explicit use-when clause with URL/token trigger patterns, and unusually good boundary routing against sibling skills. The main weakness is trigger/when coverage that does not extend to the creation route or all capability areas, and a few missing natural synonyms.

DimensionReasoningScore

Specificity

Names the domain (飞书云文档 Docx/Wiki) and several concrete actions (读取、创建、编辑文档,插入或下载图片附件,操作思维笔记), but capability areas present in the body — history versions, whiteboards, Docx covers, draft parsing — are not mentioned, which is more than a trivial gap.

4 / 5

Completeness

Both what and when are present, and the when-clause (用户提供文档 URL/token…时使用) is explicit with concrete trigger patterns. It is not a 5 because the when-clause only covers the URL/token route and gives no trigger for the create-from-scratch capability the description itself lists.

4 / 5

Trigger Term Quality

Good natural keyword coverage including 飞书云文档, Docx, Wiki, 文档 URL/token, the concrete URL path patterns /docx/ and /wiki/, 思维笔记, and 评论. A few natural synonyms are missing, e.g. 知识库 (the common Chinese name for Wiki) and plain 云文档.

4 / 5

Distinctiveness Conflict Risk

Active disambiguation against sibling skills: 独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch;表格或 Base 内部数据操作不在本 skill;/page/<token> 是妙搭应用,非飞书云文档 — a clear niche with minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

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

relative_links

Relative link issues: 4 suspicious

Warning

Total

13

/

16

Passed

Repository

larksuite/cli

Path

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