Content
86%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 genuinely lean, command-driven skill body that respects the context window and gives copy-paste-ready commands for nearly every step. The gaps are narrow but real: the terminal `gh issue create` step lacks concrete flags, and the workflows define no failure paths (dedup hit, auth failure mid-flow, submission error).
Suggestions
Give `gh issue create` its full form (e.g., `gh issue create --repo CherryHQ/cherry-studio --title "…" --body-file <tmp> --template ...`) so the final, irreversible step is as specified as the search step.
Define the dedup-hit branch (existing open issue found — append a 👍/subscribe and link it to the user instead of filing a duplicate), since the 查重 step currently has no defined outcome.
Add one line for failure recovery: what to do when `gh issue create` errors (fall back to 本地模式 and mark 待提交).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line is operational instruction — commands, paths, a compact archive template, and terse guardrails ("提交前必须用户确认", "脱敏日志中 token/key") with zero concept explanation. Nothing explains what GitHub or an issue tracker is; every token earns its place, matching the lean anchor-5 example. | 5 / 5 |
Actionability | Concrete, runnable commands throughout ("gh auth status 2>&1", "gh search issues \"[关键词]\" --repo CherryHQ/cherry-studio --state open --limit 5", template paths, copy-ready markdown archive block). Falls short of 5 because "gh issue create" is given bare with no --title/--body/--template/--repo flags, and the 预览 (preview) step has no specified format, leaving the most important step the least specified. | 4 / 5 |
Workflow Clarity | Both GitHub-mode flows are clearly arrow-sequenced (收集→查重→读模板→预览→确认→提交→告知链接) with an explicit user-confirmation checkpoint, and the batch flow includes per-item dedup, preview, confirm and status update ("逐个查重预览确认→更新状态为「已提交 #号」"), so batch validation is present rather than missing. Not 5 because there is no error-recovery handling (e.g., what to do when gh auth fails mid-batch or create errors) and the dedup-hit path (existing issue found) is undefined. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines, single-purpose, needs no external reference files (verified: no references/, scripts/, or assets/ bundle exists), and is cleanly organized into 触发边界 / 检测 GitHub 登录 / GitHub 模式 / 本地模式 / 注意 sections. Per the simple-skill guideline this is the well-organized-sections case that scores 5. | 5 / 5 |
Total | 18 / 20 Passed |