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 dense, highly actionable instruction body: exact paths, copy-paste CLI commands, a validated 8-step generation workflow with explicit verification and anti-fabrication checkpoints, and a properly factored template/script bundle. The only weaknesses are moderate repetition of the category-completeness rule and reference-style format conventions kept inline rather than split into a separate file.
Suggestions
Consolidate the repeated 'don't force basic/abnormal/boundary completeness' guidance (生成步骤 4, 用例类型 section, Markdown 约定) into a single stated rule to save tokens.
Move the frontmatter field conventions (the Markdown 约定 bullet list) or the types/evidence rules into a references/ file, keeping SKILL.md as an overview that links to assets/case-template.md and the new reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section carries operational rules and assumes competence — no generic testing concepts, library intros, or padding (e.g. "不能把现有 bug 写成正确预期"、"不臆造接口、HTTP 方法、错误码"). Not 5 because the 'don't force basic/abnormal/boundary completeness' rule recurs in three places (生成步骤 4, 用例类型 section, Markdown 约定) and some long compound bullets in the types/evidence section could be tightened. | 4 / 5 |
Actionability | Fully executable guidance throughout: exact path pattern `.agents/test/<业务域>/<子业务>/<可选细分>/<ID>-<业务目标>.md`, copy-paste commands (`node .../scripts/catalog.mjs validate|list|serve` with concrete flag examples), concrete endpoint and port (`http://127.0.0.1:4317/`, `GET /api/cases`), the exact file to edit for parser changes (`scripts/case-format.cjs` + `catalog.mjs sync-reader`), and a real, complete template at assets/case-template.md. | 5 / 5 |
Workflow Clarity | "根据业务生成用例" is a numbered 1–8 sequence with explicit validation checkpoints and feedback loops: 局部校验并在阅读器检查 (step 8), 交付前运行 validate, recording 阻塞条件 instead of faking passes, and a verify-fix path for tool changes (use a temporary case directory, don't leave demo data, re-run validate). Error-recovery guidance is explicit (待确认项, 阻塞条件及待补证据). | 5 / 5 |
Progressive Disclosure | Good structure with real one-level-deep bundle references that all exist: [用例模板](assets/case-template.md) carries the per-case scaffolding, and scripts/catalog.mjs / scripts/case-format.cjs are documented by function. Not 5 because ~40 lines of frontmatter field conventions and types/evidence rules remain inlined in SKILL.md where a references/ file would fit the rubric's ideal split; not 3 because the references that exist are clearly signaled and the body is well-sectioned. | 4 / 5 |
Total | 18 / 20 Passed |