BF openclaw-continuity-pack
用于给 OpenClaw 安装可复用的 continuity 模板与统一安装入口,支持 workspace-only、continuity-only 和 full continuity 三条路线;可选对匹配源码树应用 runtime patch,实现前台同一对话、后台自动续接、静默 continuity 准备的工作流。
As a process F 43/100 · Will not run — References files that are not bundled: assets/patch/thread-continuity.patch
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 skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-agent-memory-dumpassets/workspace/HEARTBEAT.mdAgent memory / workspace files bundled with the skill (3) — likely a workspace dump with personal data or tokensassets/workspace/HEARTBEAT.md, assets/workspace/memory/README.md, assets/workspace/SOUL.md
Files scanned: 33. 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") - warning
missing-refreference to a missing file: assets/patch/thread-continuity.patch
Process rating: all ten parameters 43/100
- 0Tools and files. 1 referenced file(s) missing: assets/patch/thread-continuity.patch
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 100Steps. 74 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1283 tokens
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- +2Single-language instructions
- +3Description length 160: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 74 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (13 of 13)
- +3All 4 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.