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 operational skill body: an intent-routing table with real, resolvable reference files, executable commands throughout, and decision/guardrail sections with explicit validation gates and error-recovery loops for destructive operations. The main improvement areas are the fully inlined collaborator-permissions section and a repeatedly referenced creative-design/creative-design.md file that is missing from the bundle.
Suggestions
Move the detailed collaborator/permission rules (typed-ID requirements, feature_not_available / copy_download_by / external_invite edge cases) into a dedicated references/lark-apps-member.md and keep only the dry-run/--yes confirmation pattern inline.
Add the missing creative-design/creative-design.md to the bundle (it is referenced as the full development-and-publish flow for html/creative apps in five places), or repoint those links to an existing reference.
Replace the vague '对应 access-scope reference' cell with proper 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.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, routing-first prose that assumes Claude's competence and explains nothing Claude already knows, but the fully inlined ~25-line collaborator/permissions section (e.g. 'copy_download_by 也只在 +member-settings-get 的响应中读取…', 'feature_not_available（OpenAPI code 3340005）') and rules repeated across sections (app_id resolution, release handling) could be trimmed or moved out. This is anchor 4 ('efficient; minor instances… that could be trimmed'), not 5, because of that inline bulk. | 4 / 5 |
Actionability | Commands are complete and copy-paste ready with exact flags and placeholders: 'lark-cli apps +member-add --app-id <app_id> --member-type openid --member-id ou_xxx --perm view --dry-run --as user', 'lark-cli apps +get --app-id <meta_token> -q '.data.app.app_id'', 'lark-cli auth login --domain apps'. Not 4: there are no missing key details in the common cases. | 5 / 5 |
Workflow Clarity | Multi-step flows are explicitly sequenced with validation checkpoints: the '选择开发路径' decision table is ordered before intent routing, app_id resolution has ordered steps 1–3, destructive ops gate on '--dry-run' → user confirmation → '--yes', releases poll 'finished/failed' with PENDING-approval handling, and git failures loop through credential refresh → retry → stop and report. Destructive/batch operations all carry validation, so the ≤3 cap does not apply; feedback loops match the top anchor. | 5 / 5 |
Progressive Disclosure | The intent-routing table maps 25+ intents to one-level-deep reference files and all 30 references/lark-apps-*.md links resolve, giving good structure. Kept at 4 rather than 5 because 'creative-design/creative-design.md' is referenced repeatedly but absent from the bundle, the access-scope row says '对应 access-scope reference' instead of a real link, and the member/collaborator rules are entirely inline with no reference file. | 4 / 5 |
Total | 18 / 20 Passed |