BD convert2docx
把 Markdown / 纯文本 / HTML / RTF / LaTeX / reStructuredText / Org-mode 转成 .docx，并套用用户自己指定的 reference.docx 样式模板。支持单文件、批量、拖拽操作。当用户说"把 XX 转成 Word"、"批量转 docx"、"用我自己的样式模板转换文档"时使用本技能。
把 Markdown / 纯文本 / HTML / RTF / LaTeX / reStructuredText / Org-mode 转成 .docx，并套用用户自己指定的 reference.docx 样式模板。支持单文件、批量、拖拽操作。当用户说"把 XX 转成 Word"、"批量转…
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Dangerous commands
cmd-execpolicy-bypassscripts/convert2docx.bat:41Runs PowerShell with execution policy bypassedpowershell.exe -NoProfile -ExecutionPolicy Bypass -File "%PS_SCRIPT%"
Files scanned: 7. 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") - note
frontmatter-keyunknown frontmatter key "title" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 41/100
- 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
- 40Consistency. Frontmatter name (convert2docx) differs from the folder (docx-convert)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 28 steps
- 100Execution cost. Instruction body is 787 tokens
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
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
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 174: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.