BD longtask_system
|
As a process D 44/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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Dangerous commands
cmd-background-processskill-card.md:21Starts a background / autostarted processMitigation: Use trusted task files, monitor daemon logs and inbox state, and keep a clear stop procedure for the screen or setsid process. <br>
-
low Dangerous commands
cmd-background-processSKILL.md:78Starts a background / autostarted process# 方案2: setsid(Linux 环境)
-
low Dangerous commands
cmd-background-processSKILL.md:79Starts a background / autostarted processsetsid bash daemon.sh my_task > longtask_log/daemon.log 2>&1 &
-
low Dangerous commands
cmd-background-processSKILL.md:85Starts a background / autostarted process (quoted — discussed, not commanded)**注意**:OpenClaw 等 Agent 框架在 session 结束时会清理子进程,必须使用 `screen` 或 `setsid` 确保 daemon 不被杀掉。
quoted -
low Dangerous commands
cmd-background-processSKILL.md:258Starts a background / autostarted process- 修复 daemon 在 OpenClaw 环境下被 session 杀掉的问题(使用 screen/setsid)
Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Implicit map keys need to be followed by map values at line 10, column 1: 重要:为了确保长程任务执行的效果,每一个子任务会强制通过/new重置对话后执行!如果你是单agent模式,可以在notify_agent.sh脚本中的消息构建… ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-shortdescription under 40 chars: too little signal for triggering - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 44/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (longtask_system) differs from the folder (longtask-system)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 36 steps
- 100Execution cost. Instruction body is 1288 tokens
- 100Running it twice. No mutating operations
- low 10 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 1: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 24 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 46.
External checks
ClawHub: suspicious
This is a coherent long-task automation skill, but it deserves Review because it can run persistent agent orchestration while resetting agent context and rendering untrusted task text into HTML without escaping.
LLM: suspicious (high) · VirusTotal: · 29 May 2026