Content
86%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-engineered CLI skill body: executable commands with flag-level detail, explicit routing tables for intent and prerequisites, safeguards on destructive/irreversible operations, and a clean one-level-deep reference structure where all linked files exist. Remaining polish is minor: deduplicate the applink and --apply-to warnings and consolidate error-handling guidance inline.
Suggestions
Deduplicate the 日程分享链接 vs applink warning — it appears nearly verbatim in both '核心概念' and the '意图路由' table; stating it once in a routing row would save tokens.
The recurring '--apply-to' rule is repeated in the Shortcuts table, '前置条件路由', and '意图路由'; consolidate into the recurring reference link and mention the requirement once.
Add a one-line pointer to the error/permission handling location (e.g. '命令失败时先读 ../lark-shared/SKILL.md 的错误处理') near the top so the error-recovery loop is discoverable without leaving the body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and operational — shortcut table, routing tables, flag-level CLI examples — with almost no explanation of concepts Claude already knows. Minor over-explanation exists: the share-link-vs-applink warning is repeated verbatim in '核心概念' and '意图路由', and the recurring '--apply-to' rule appears three times. This is 'efficient with minor instances that could be trimmed', not the 5 anchor's 'every token earns its place'. | 4 / 5 |
Actionability | Concrete, copy-paste-ready `lark-cli calendar` commands with flags, defaults, and realistic examples throughout (e.g. '+freebusy ... --type common_free --min-duration 30m', '+search-event --query "周会" --start 2026-04-20 ...'), plus discovery commands ('lark-cli calendar <resource> -h'). Specific examples cover the common cases, matching the 5 anchor. | 5 / 5 |
Workflow Clarity | Multi-step flows are clearly sequenced via the '前置条件路由' table, '意图路由' table, and new-vs-edit signals in '任务类型分流', with explicit checkpoints for risky operations (recurring scope confirmation '先确认「仅此次/全部/此次及后续」', '+transfer' 的 '不可逆，需 --yes', '+room-find' 禁止无明确时间调用). It falls short of the 5 anchor only in lacking inline error-recovery loops, which are delegated to ../lark-shared/SKILL.md. | 4 / 5 |
Progressive Disclosure | The body is a true overview: a shortcut table linking each command to its reference file, routing tables that say '先读 X', and 14 real reference files (all cited paths — schedule-meeting, recurring, suggestion, room-find, update, etc. — exist in ./references/). References are one level deep and clearly signaled, matching the 5 anchor exactly. | 5 / 5 |
Total | 18 / 20 Passed |