Content
85%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, actionable skill body: concrete commands, an explicit dry-run/confirm validation loop for destructive edits, and a clean one-level reference split. The only weakness is verbosity in the meta-notices (experimental disclaimer and command-availability caveat).
Suggestions
Trim the command-availability warning to one line — drop the service-discovery/static-endpoint/backend-tool-registration implementation details and keep only the actionable rule: verify with `dws <cmd> --help` or `--dry-run` before calling.
Shorten the experimental-preview notice; the mono-vs-multi and dispatch-verifier details can be cut to a single line or moved to a reference, since they are not needed to execute the markdown operations.
Keep the lean intent-table + hard-constraints + cross-product-routing structure as-is — it is the strongest part of the body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The operational core (intent table, hard constraints, cross-product routing) is lean, but the experimental-preview notice and the command-availability warning ("服务发现已下线...静态端点目录和后端工具注册...") carry implementation details that could be tightened — matching the score-2 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the score-3 'every token earns its place'. | 2 / 3 |
Actionability | The intent table gives copy-paste-ready commands with real flags (e.g. `dws markdown patch --node <fileId> --pattern '<RE2>' --content "<新文本>" --regex --dry-run`), matching the 'fully executable code/commands; specific examples; copy-paste ready' anchor rather than the score-2 'incomplete; pseudocode'. | 3 / 3 |
Workflow Clarity | Destructive overwrite/patch operations have an explicit dry-run → user-confirm → --yes checkpoint ("先用命令级 --dry-run 查看差异，获得用户明确确认后再加 --yes"), plus safety behavior (0-hit no-write, empty-result abort), matching the 'clear sequence with explicit validation steps; feedback loops' anchor; validation is present so the destructive-op cap at 2 does not apply. | 3 / 3 |
Progressive Disclosure | The body is an overview (intent table + hard constraints + routing) that signals one clearly-marked one-level-deep reference, "命令参考：[markdown.md](references/markdown.md)" (verified to exist), with detailed flag tables split into that file — matching the 'clear overview with well-signaled one-level-deep references; content appropriately split' anchor. | 3 / 3 |
Total | 11 / 12 Passed |