BF presend-deliverable-inspector
对 PPT、Word、PDF、Excel、邮件、汇报稿和多附件包做发送前最终审核（pre-send review / send-readiness check / final QA），专门判断整套材料现在能不能发。区别于 Office 文件制作、编辑、转换，单纯 PPT 版式检查，通用 document review / report review 和单点 fact check：本 Skill 先读取当前指令、必要对话前文、收件人、目标动作、截止时间和材料阶段，再给出‘可以发送 / 快改后发送 / 暂缓发送 / 重做后再发’判定；重点发现跨页与跨附件数字冲突、指标口径、来源与证据强度、结论越界、隐藏页/备注/批注/旧版本、隐私承诺和决策缺口。仅在用户明确要求‘能不能发’‘发前检查’‘最终审核’‘出街体检’‘帮我检查这个PPT’‘明天发老板/客户’‘final QA’，或在‘PPT review’‘document review’‘report review’请求中带有发送、提交、汇报或发布意图时触发；不要因仅出现 PPT、Word、PDF 或 Excel 而触发。输出必须改、可以保留、未核验项及 30 分钟修复路线。不得自动发送、编造来源、覆盖原文件或替用户作出承诺。
对 PPT、Word、PDF、Excel、邮件、汇报稿和多附件包做发送前最终审核（pre-send review / send-readiness check / final QA），专门判断整套材料现在能不能发。区别于 Office 文件制作、编辑、转换，单纯 PPT 版式检查，通用 document…
As a process F 35/100 · Will not run — References files that are not bundled: scripts/inspect_deliverable.py, scripts/render_inspection_report.py, references/release-readiness-gate.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: scripts/inspect_deliverable.py - warning
missing-refreference to a missing file: scripts/render_inspection_report.py - warning
missing-refreference to a missing file: references/release-readiness-gate.md - warning
missing-refreference to a missing file: scripts/assess_release_readiness.py - warning
missing-refreference to a missing file: scripts/run_regression_suite.py
Process rating: all ten parameters 35/100
- 0Tools and files. 5 referenced file(s) missing: scripts/inspect_deliverable.py, scripts/render_inspection_report.py, references/release-readiness-gate.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. 40 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1260 tokens
- 100Running it twice. No mutating operations
- low 14 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
- +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
- +1No license
- +2Single-language instructions
- +3Description length 542: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.