CF docx-writer
标准学术文档生成 — 通过 bayoo-docx（原生脚注支持）和模板 template.docx 生成符合学术排印规范的 Word 文档，含脚注、三线表、图片、LaTeX 公式（可输出 Word 原生可编辑公式 OMML 或 XeLaTeX 渲染图）等。当用户要生成/排版 Word（.docx）文档、学位论文、实验报告、新闻稿、推送稿、讲稿，或需要在 docx 里插入数学公式/LaTeX 公式/原生可编辑公式时使用
标准学术文档生成 — 通过 bayoo-docx（原生脚注支持）和模板 template.docx 生成符合学术排印规范的 Word 文档，含脚注、三线表、图片、LaTeX 公式（可输出 Word 原生可编辑公式 OMML 或 XeLaTeX 渲染图）等。当用户要生成/排版…
As a process F 33/100 · No process to follow — References files that are not bundled: templates/*.yaml
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: 12. 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: templates/*.yaml
Process rating: all ten parameters 33/100
- 0Tools and files. 1 referenced file(s) missing: templates/*.yaml
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 70Execution cost. Instruction body is 4601 tokens
- 100Steps. 76 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 15 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -212 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 210: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 76 items
- +4Has examples (10 code blocks)
- +3All 4 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.