Content
88%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 strong, highly actionable routing skill: concrete commands and flags throughout, explicit confirmation gates and bounded retry policies for destructive and batch operations, and a comprehensive verified reference bundle. Weaknesses are minor — some duplicated routing bullets that could be deduplicated, two empty raw-API descriptions, and a two-level workflow reference chain that slightly complicates navigation.
Suggestions
Deduplicate the near-verbatim permission-governance routing bullets (lines 27 and 30) and consolidate the copy-routing guidance (blockquote at line 19, bullet at line 24, and the +copy shortcut/API rows) into a single authoritative statement.
Fill in the empty descriptions for permission.members auth and transfer_owner, or point them at a reference file like the other raw API entries do.
Surface the workflow phase sub-files (e.g. lark-drive-workflow-knowledge-organize-discovery.md) directly from the workflow registry entry in SKILL.md so navigation to phase details stays within one hop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a dense, rule-based routing document with almost no padding or explanation of known concepts, but the permission-governance routing bullet appears twice nearly verbatim (lines 27 and 30) and copy routing is stated three separate times, so minor trimming is possible. This fits the 'efficient; minor instances that could be trimmed' anchor rather than level 3, since the redundancy is localized rather than whole unnecessary sections. | 4 / 5 |
Actionability | Guidance is fully executable: exact commands with flags ('lark-cli drive +import --type bitable', "drive +inspect --url '<url>'"), a shortcut table where every entry links to a per-command reference, and concrete flag mappings for natural-language queries (--created-by-me, --mine). The only blemish is the empty descriptions on permission.members auth/transfer_owner, which is too small to drop below the top anchor. | 5 / 5 |
Workflow Clarity | Destructive and batch operations have explicit validation checkpoints: a three-condition confirmation gate for high-risk writes with a read-only discovery-then-stop rule, serial import with a bounded retry policy (max 3 retries, then stop and report conflicts), and an error-code table with remediations. This satisfies the feedback-loop requirement, so the destructive/batch cap does not apply and the content matches the top anchor. | 5 / 5 |
Progressive Disclosure | The body is a well-organized overview and all 47 intra-bundle reference links verified to exist, each clearly signaled from the routing bullets and shortcut table. However, the workflow registry path (workflow.md → workflow file → phase sub-files such as knowledge-organize-discovery.md) is a two-level reference chain, and cross-skill links (../lark-shared, ../lark-wiki) are not one-level-deep within this bundle, so it falls between the 'minor organization gaps' level 4 and the top anchor. | 4 / 5 |
Total | 18 / 20 Passed |