AC task-progress-report
在运行长任务时，同步开启"任务进展汇报"功能，定时输出当前任务进展情况。当用户提到"汇报进展"、"定时报告"、"任务进度"、"长时间运行"、"监控任务状态"或需要了解长时间任务的执行情况时，使用此技能。特别适用于模型蒸馏、数据训练、批量处理、爬虫任务等需要长时间运行的场景。
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ReferenceData and analyticsInfrastructuretype 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: 3. 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")
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 38 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 601 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 137: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (7 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.
External checks
ClawHub: clean
This skill appears to be a task progress reporter that writes local markdown status reports and does not show hidden, destructive, credential, or exfiltration behavior.
LLM: benign (high) · VirusTotal: · 29 May 2026