BC session-memory-flush
在 OpenClaw session 即将因 idle/reset 释放前，扫描 `openclaw sessions --json` 可见会话，读取 transcript，提炼高价值上下文并写入 workspace memory 文件，降低新 session 的失忆感。用于 main、native subagent、cron、dreaming 等会话的 idle 前摘要回收；当需要安装、验证、调试、交付这个 skill，或需要解释它与 builtin memory / per-agent SQLite index / workspace 共享范围的关系时使用。
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Exfiltration
net-redirectable-api-keywatcher.py:514Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
low Dangerous commands
cmd-cron-mentioninstall.sh:210Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v "$CRON_MARKER" > "$TMP_CRON" || true
-
low Dangerous commands
cmd-cron-mentionuninstall.sh:17Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v "$CRON_MARKER" > "$TMP_CRON" || true
Files scanned: 7. 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. 40 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 936 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 284: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.