BD QClaw任务结果查询
通过 QClaw 查询 WorkBuddy 任务执行结果。当用户想要： - 查看任务是否完成 - 获取任务执行结果 - 查任务状态 - 询问"刚才那个任务怎么样了" - "结果出来了吗" - 想知道 WorkBuddy 执行了什么 触发词：任务结果、查结果、看结果、任务完成了吗、结果出来了吗、工作做完了吗、WorkBuddy结果、任务状态
As a process D 49/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.
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: 2. 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 49/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 (QClaw任务结果查询) differs from the folder (qclaw-result-checker)
- 100Tools and files. No external tools needed
- 100Steps. 7 steps
- 100Execution cost. Instruction body is 356 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
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 170: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: clean
The skill transparently checks local WorkBuddy task status and results, with a privacy caveat that broad result-related prompts could show prior queue data.
LLM: benign (high) · VirusTotal: benign · 28 May 2026