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 well-engineered procedural skill: concrete commands and MCP call blocks throughout, a clearly sequenced workflow with genuine error-recovery paths, and scripts correctly factored out of the SKILL.md body. The only improvements are minor: deduplicate the branch-naming rules and script-path table, and consider moving the naming/title conventions into a reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Almost every line carries project-specific operational detail Claude cannot infer (bk-ci repo, jOOQ generation, .cursor/.idea sync, Cursor detection), so it earns its tokens. Minor trimming opportunities exist: "末段必须是 issue 号" is stated twice in Step 3, and the closing 脚本说明 table repeats script paths already given in Step 4 commands. | 4 / 5 |
Actionability | Guidance is fully executable: copy-paste bash/PowerShell blocks (git branch --show-current, git fetch origin master, both script invocations with -Base origin/master, cursor --new-window), complete CallMcpTool argument blocks for issue_read and issue_write, and the exact AskQuestion prompt with its four options. Placeholders (分支名, issue号) are appropriately parameterized. | 5 / 5 |
Workflow Clarity | The process is clearly sequenced (environment/branch/MCP prechecks, then Steps 1–5) with explicit validation checkpoints and error-recovery loops: skip when not Cursor or not on master, MCP-unavailable fallback to manual branch names, refusal to reuse an existing branch with rename/cleanup guidance, double confirmation before creating an upstream issue, and jOOQ-failure handling. The terminal state ("本次对话到此结束，不要再对任何文件做修改") is unambiguous. | 5 / 5 |
Progressive Disclosure | The heavy executable logic is properly externalized into two real bundle scripts (scripts/git-worktree.ps1, scripts/git-worktree.sh) referenced one level deep with a closing table describing their add/list/remove operations. The ~60 lines of branch-naming and issue-title convention kept inline in the body are a minor organization gap — they could live in a reference file. | 4 / 5 |
Total | 18 / 20 Passed |