BD OpenClaw 工作协议
1. 自我驱动 → 自己生成 todo-list,按顺序推进 2. 自主解决问题 → 遇到问题自己搞定,别卡住 3. 主动汇报 → 定期告诉进度,不等你问 4. 避免被动 → 不"问一点干一点"
1. 自我驱动 → 自己生成 todo-list,按顺序推进 2. 自主解决问题 → 遇到问题自己搞定,别卡住 3. 主动汇报 → 定期告诉进度,不等你问 4. 避免被动 → 不"问一点干一点"
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedurePersonal productivityAI and agentstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 43/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
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (OpenClaw 工作协议) differs from the folder (openclaw-work-protocol)
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 100Steps. 166 steps
- 100Execution cost. Instruction body is 1750 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 13 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)
- +3Description length 97: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- -237 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 30 headings
- +3Step-by-step instructions: 166 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.