Content
85%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 dense, highly actionable router: concrete commands, confirmation gates for destructive operations, and real feedback loops. The main defect is progressive disclosure — the creative-design route, one of the three app_type paths, is a dangling reference, and the access-scope pointer is vague — with minor conciseness losses from repetition and overlong guardrail sentences.
Suggestions
Add the missing creative-design/creative-design.md to the bundle (or repoint the six references to an existing file such as references/lark-apps-local-dev.md) — the primary HTML/创意模式 development route currently dead-ends.
Replace the vague access-scope row ('对应 access-scope reference') with explicit links to references/lark-apps-access-scope-get.md and references/lark-apps-access-scope-set.md, matching the style of every other routing row.
Consolidate the six repetitions of the creative-design link and tighten the longest guardrail sentences (发布态护栏, 禁止预授权判定底线) into shorter condition→action rules to cut token cost without losing the gates.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Almost entirely non-obvious domain rules (error subtypes, ID-type enums, scope names, approval states) with no teaching of known concepts, but the creative-design link is repeated six times and several guardrail sentences (发布态护栏, 预授权底线) are long run-ons that restate conditions and could be trimmed. | 4 / 5 |
Actionability | Copy-paste-ready commands with placeholders throughout (e.g. 'lark-cli apps +member-add --app-id <app_id> --member-type openid --member-id ou_xxx --perm view --dry-run --as user', '+metric-list --metric requests --since <range>'), and the intent table maps every intent to an exact subcommand plus its reference file — even edge cases like meta_token resolution get a concrete command. | 5 / 5 |
Workflow Clarity | Clear sequencing (dev-path decision table → intent routing → app_id resolution → release guardrails) with explicit validation gates (dry-run before member writes, --yes gating, db-execute dry-run), a genuine error-recovery feedback loop (git failure → +git-credential-init → retry → stop and report), release polling with terminal-state precedence, and a non-preauthorization checklist for destructive operations. | 5 / 5 |
Progressive Disclosure | The 27 reference files are all one level deep, clearly signaled, and resolve — but the primary HTML/creative route points to 'creative-design/creative-design.md' which does not exist in the bundle (referenced 6 times as the complete dev/publish flow), and the access-scope row says only '对应 access-scope reference' with no link, so navigation fails on a main path. | 3 / 5 |
Total | 17 / 20 Passed |