BC origin-office
原生文档（docx/pptx）→ 可验证的对象——转换即语义事务。零依赖解析 docx 的章/条/段落/表格（合并单元格展开、勾选框保留）与 pptx 的幻灯片/形状/表格（占位符类型、gridSpan 合并），每处结构一个对象建成本象包，SHA-256 结构指纹入库，verify 可验证「包与源文件一致」（篡改即检出）。行业火力全在 PDF 扫描件（OCR 有物理误差），原生电子文档的无损结构化没人认真做——本象做「把字变成可验证状态的对象」。当需要把 docx/pptx 转成 AI 可锚定、可验证的结构，或做文档版本追踪/条款级引用时使用。
原生文档（docx/pptx）→ 可验证的对象——转换即语义事务。零依赖解析 docx 的章/条/段落/表格（合并单元格展开、勾选框保留）与 pptx 的幻灯片/形状/表格（占位符类型、gridSpan 合并），每处结构一个对象建成本象包，SHA-256 结构指纹入库，verify…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 0
✓ No critical or high findings
Files scanned: 3. 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 "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary"
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 5 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 451 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
- +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
- +2Single-language instructions
- +3Description length 275: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.