BF summarize
在 Codex 中总结、精简或交接当前任务，提取目标、状态、决策、验证、风险和下一步，并基于本次证据给出操作、优化与行为建议。用户说“总结”“总结一下”“总结进度”“复盘”“总结精简”“压缩上下文”“交接”“handoff”“compact”“总结 checkpoint”“总结 交接 分层”“总结 诊断 历史”或“summarize”时使用。默认只读；仅在用户明确说“总结 保存”时写入当前工作区。
在 Codex 中总结、精简或交接当前任务，提取目标、状态、决策、验证、风险和下一步，并基于本次证据给出操作、优化与行为建议。用户说“总结”“总结一下”“总结进度”“复盘”“总结精简”“压缩上下文”“交接”“handoff”“compact”“总结 checkpoint”“总结 交接 分层”“总结 诊断…
As a process F 31/100 · Will not run — References files that are not bundled: references/recommendations.md, references/history-diagnostics.md, references/layered-handoff.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/recommendations.md - warning
missing-refreference to a missing file: references/history-diagnostics.md - warning
missing-refreference to a missing file: references/layered-handoff.md - warning
missing-refreference to a missing file: references/operations.md - warning
missing-refreference to a missing file: scripts/save_handoff.py - warning
missing-refreference to a missing file: scripts/inspect_handoff.py
Process rating: all ten parameters 31/100
- 0Tools and files. 6 referenced file(s) missing: references/recommendations.md, references/history-diagnostics.md, references/layered-handoff.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
- 40Consistency. Frontmatter name (summarize) differs from the folder (session-summarize)
- 100Steps. 44 steps
- 100Execution cost. Instruction body is 982 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
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 200: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 44 items
- +4Has examples (2 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.