Content
65%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.
The body is well-structured with excellent progressive disclosure and mostly actionable guidance, but it carries redundant table content and lacks explicit validation/retry loops for batch and destructive IM operations.
Suggestions
Add explicit validate->fix->retry feedback loops for destructive/batch operations (messages.delete, messages.patch, reactions create/delete, folder expansion) to lift workflow_clarity above the batch/destructive cap of 3.
Trim redundancy between the Shortcuts table, API Resources section, and 权限表 by keeping SKILL.md to discovery-level summaries and deferring scope/flag detail to the reference files.
Include one or two complete copy-paste command examples (e.g. a send-message and a list-messages invocation with real flags) to move actionability from tabular flags toward fully executable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but the large Shortcuts table, API Resources section, and 权限表 partly duplicate details that also live in the references, and dense explanatory blocks (Identity/Token Mapping, Sender Name Resolution) could be trimmed; fits the 'mostly efficient but could be tightened' anchor rather than the lean 4. | 3 / 5 |
Actionability | Gives concrete commands and flags ("lark-cli im +<verb> [flags]", "lark-cli schema im.<resource>.<method>", specific scopes, batch limits) with minor gaps; not a 5 because most guidance is tabular flags rather than complete copy-paste examples covering common cases. | 4 / 5 |
Workflow Clarity | Sequencing exists (schema-before-call checkpoint, card-create MUST-read gate), but destructive/batch operations (messages.delete, patch, reactions, folder expansion) lack explicit validate->fix->retry feedback loops, so the batch/destructive cap of 3 applies. | 3 / 5 |
Progressive Disclosure | Clear overview with well-signaled one-level-deep references; all 28 referenced bundle files exist, bulk detail is pushed to references/, and the only deeper nesting (card/components) sits behind the card-create entry point for justified reasons. | 5 / 5 |
Total | 15 / 20 Passed |