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.
The body is an exemplary lean operational skill: terse, command-driven, well-sectioned, with explicit user-confirmation and dedup checkpoints guarding the batch/destructive submission flows. The only meaningful improvements are completing the gh issue create invocation (flags/template usage) and stating how to fetch the upstream issue templates, plus handling the duplicate-found case.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~35-line body is maximally lean: every line is operational (commands, paths, a fill-in template, URLs) with zero explanation of concepts Claude already knows and no padding. Arrow-compressed steps like「收集信息(...) → 查重 ... → 预览给用户 → 确认后 gh issue create」assume Claude's competence, matching anchor 5 exactly. | 5 / 5 |
Actionability | Mostly copy-paste ready: 「gh auth status 2>&1」, 「gh search issues "[关键词]" --repo CherryHQ/cherry-studio --state open --limit 5」, template paths, storage file paths, and a concrete markdown archive template. Minor gaps keep it below anchor 5: 「gh issue create」 lacks its argument form (--title/--body or --template), and reading 「.github/ISSUE_TEMPLATE/0_bug_report.yml」 does not specify how to obtain the file from the upstream repo (no clone/URL assumed). | 4 / 5 |
Workflow Clarity | Both GitHub-mode and batch flows have clear arrow-sequenced steps with real checkpoints: dedup search (查重), user preview (预览给用户), mandatory confirmation (提交前必须用户确认 / 确认后), and post-submit status updates. The batch-operation cap at 3 does not apply since validation and confirmation are present, but it stays at 4 because error recovery is not addressed (e.g., what to do when 查重 finds an existing issue, or when gh issue create fails). | 4 / 5 |
Progressive Disclosure | This is a simple single-purpose skill under 50 lines with no bundle files (no references/, scripts/, or assets/ directories exist) and no need for external references; per the rubric's simple-skill guideline it scores 5 on well-organized sections alone. The body is cleanly sectioned (触发边界 / 检测登录 / GitHub 模式 / 本地模式 / 注意) and every path referenced is an external destination (repo, forum, form URL), not a missing bundle file. | 5 / 5 |
Total | 18 / 20 Passed |