Content
78%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 thorough, highly actionable CLI skill with strong progressive disclosure and explicit safety/validation gates for destructive and send operations. The main weakness is conciseness: the confirmation-before-send and draft-default rules are restated several times across sections, inflating the token budget without adding new information.
Suggestions
State the '默认存草稿 / --confirm-send 发送前需用户确认' rule once in the security section and reference it from the workflow and shortcut table instead of restating the full rule in each location.
Trim core-concept definitions that restate the obvious (e.g. what a folder or label is) to just the Lark-specific identifiers and behaviors (message_id, thread_id, built-in folder/label IDs).
Deduplicate the shortcut table's repeated 'save as draft (default). Use --confirm-send to send immediately after user confirmation' phrasing by noting the default once and keeping only per-shortcut differences.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and information-dense, but the send-confirmation rule and '默认存草稿 / --confirm-send' phrasing are repeated across the security rules, typical-workflow, command-selection, and shortcut-table sections, and a few core-concept definitions (folder/label) state the obvious — could be tightened. | 3 / 5 |
Actionability | Fully executable, copy-paste-ready CLI commands throughout (e.g. `lark-cli mail +send --to alice@example.com --subject '周报' --body '…'`) plus a concrete schema→flag mapping table and worked GET/POST examples covering the common native-API cases. | 5 / 5 |
Workflow Clarity | Clear sequenced processes (11-step typical workflow, 3-step native-API procedure) with explicit validation/feedback loops for destructive and batch ops (confirmation previews with affected counts, send_status delivery verification, the triage→preview→confirm→trash example); the main workflow list reads more as a feature tour than an inline-checkpointed process, a minor gap. | 4 / 5 |
Progressive Disclosure | Clear overview structure with well-signaled one-level-deep references — a shortcuts table and 常用操作速查 link each operation to its references/*.md file, bulk detail is delegated to 28 reference files and assets/templates/, and sampled referenced paths are real. | 5 / 5 |
Total | 17 / 20 Passed |