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 concise, well-structured, highly actionable skill body with clear sequenced workflows and validation checkpoints including user confirmation and dedup before submit. The main improvement areas are specifying the gh issue create invocation fully and adding an explicit error-recovery/duplicate-handling feedback loop.
Suggestions
Specify the gh issue create invocation concretely (e.g., gh issue create --repo CherryHQ/cherry-studio --title "..." --body-file <filled-template>) so the submission step is copy-paste ready.
Add an explicit feedback loop for the dedup result (e.g., if an open duplicate is found, link to it and skip creation) and for create failures (retry / fall back to local mode), which would lift workflow_clarity to 5.
Clarify how the .github/ISSUE_TEMPLATE YAML template is filled from the collected fields before preview, so the template-to-submission path is unambiguous.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and token-efficient throughout: dense arrow-notation workflows, concrete one-line commands, and a compact markdown template, with no padding or explanation of concepts Claude already knows; every line earns its place. | 5 / 5 |
Actionability | Provides concrete executable commands (gh auth status, gh search issues with full flags, gh issue create), specific template/file paths, URLs, and a copy-paste local-mode template; minor gap is that gh issue create is given without --title/--body flags and the template-filling step is described as a process rather than shown as executable code. | 4 / 5 |
Workflow Clarity | Clear sequenced workflows (collect → dedup → read template → preview → confirm → create → report link) with validation checkpoints (auth-detect branching, dedup, preview, mandatory user confirmation before submit) and per-item confirmation in the batch flow; held below 5 because there is no explicit error-recovery feedback loop for create failures or duplicate handling. | 4 / 5 |
Progressive Disclosure | A self-contained single-file skill under 50 lines with no bundle files and well-organized sections (触发边界, 检测 GitHub 登录, GitHub 模式, 本地模式, 注意), satisfying the simple-skill exception for progressive disclosure. | 5 / 5 |
Total | 18 / 20 Passed |