BF wenqu-review
审查中文内容的事实依据、逻辑连贯性、术语规范、翻译腔、AI 写作痕迹与整体结构，适用于 文章、报告、教程、项目介绍和说明材料。当用户要求“审查”“检查一下”“看看有没有问题” “整体看看”，或使用 "review an article", "review this draft", "proofread" 等英文表达时 使用；可独立运行，也可作为其他写作技能的内联审查阶段。
审查中文内容的事实依据、逻辑连贯性、术语规范、翻译腔、AI 写作痕迹与整体结构，适用于 文章、报告、教程、项目介绍和说明材料。当用户要求“审查”“检查一下”“看看有没有问题” “整体看看”，或使用 "review an article", "review this draft", "proofread"…
As a process F 35/100 · Will not run — References files that are not bundled: references/change-impact.md, references/rN-*.md, references/planning/questionnaire.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/change-impact.md - warning
missing-refreference to a missing file: references/rN-*.md - warning
missing-refreference to a missing file: references/planning/questionnaire.md - warning
missing-refreference to a missing file: references/preferences.md - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 35/100
- 0Tools and files. 4 referenced file(s) missing: references/change-impact.md, references/rN-*.md, references/planning/questionnaire.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 693 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 187: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 13 items
- +4Reference files are cited in the instructions (9 of 9)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.