Content
63%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 a lean, actionable template with real commands and a solid starter scaffold for a simple skill. Its weaknesses are structural: a duplicated resources section pointing at bundle files that are missing, a dangling reference to non-existent IF-THEN rules, and no explicit run-and-fix verification step.
Suggestions
Remove the duplicated '📦 可用资源' section and the dangling 'IF-THEN 规则' note, or replace them with concrete load conditions (e.g. '遇到 mock 需求时加载 references/mock-patterns.md').
Ship the three referenced files (mock-patterns.md, test-qa.md, test-strategies.md) or delete the links that point at them.
Add an explicit verification step after the template, e.g. '编写后运行 npx vitest run src/components/<component>，修复失败用例后再继续'， and flesh out the vi.mock example so it is copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient (terse commands, a compact template, one-line category descriptions), but the '📦 可用资源' section is duplicated verbatim and the trailing note '根据 SKILL.md 中的 IF-THEN 规则判断是否需要加载' references rules that do not exist in the document — unnecessary padding that keeps it below the level-4 anchor. | 3 / 5 |
Actionability | It provides concrete, runnable commands ('pnpm --filter @blueking/chat-x test', 'npx vitest run src/components/your-component') and a near-complete executable template, matching 'mostly executable guidance with minor gaps'. The gaps — the empty vi.mock stub ('/* ... */') and placeholder component names needing substitution — keep it from the copy-paste-ready level-5 anchor. | 4 / 5 |
Workflow Clarity | As a simple single-purpose skill the action is unambiguous: co-located file naming convention, a starting template, and explicit run commands. It sits between the simple-skill level-5 exception and level 3 because there is no explicit verify/fix checkpoint after writing (e.g., 'run the tests and fix failures before finishing'), though the run commands are given. | 4 / 5 |
Progressive Disclosure | References are listed one level deep with clear paths, but the three referenced files (references/mock-patterns.md, test-qa.md, test-strategies.md) do not exist in the bundle, and the resource section is duplicated verbatim — matching 'some structure but could be better organized' rather than the well-organized level-4 anchor. | 3 / 5 |
Total | 14 / 20 Passed |