BD report-builder
📥 openclaw skill install dabin0927/executive-briefing —— 给老板汇报不用写 PPT，一页纸让他 3 分钟拍板。 自动把几十页方案压缩成决策摘要：结论直接给、数据会说话、行动能落地。 BLUF 一页纸 + So What 叙事 + 脚本化工具链（init/bump/validate/density）。 适合：向 CEO/董事会/投资人汇报、决策备忘录、管理简报。 不适合：技术文档、数据分析图表、PPT 排版。 (EN) One-page executive briefing factory — BLUF + scripts + templates.
📥 openclaw skill install dabin0927/executive-briefing —— 给老板汇报不用写 PPT，一页纸让他 3 分钟拍板。 自动把几十页方案压缩成决策摘要：结论直接给、数据会说话、行动能落地。 BLUF 一页纸 + So What 叙事 +…
As a process D 41/100 · Unfinished process — 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: 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") - note
frontmatter-keyunknown frontmatter key "triggers"
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 (report-builder) differs from the folder (executive-briefing)
- 60Tools and files. Uses tools (python, node) that frontmatter does not declare
- 100Steps. 15 steps
- 100Execution cost. Instruction body is 1856 tokens
- 100Running it twice. No mutating operations
- low 13 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
- -229 emoji in the instructions: noise for the model
- -31 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 305: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.