BF memory-compression-system
Integrated memory management and extreme context compression for OpenClaw. Combines memory management, compression, search, and automation in one unified skill.
Integrated memory management and extreme context compression for OpenClaw.
As a process F 46/100 · Will not run — References files that are not bundled: scripts/repair.sh, scripts/rebuild-index.sh, scripts/diagnose.sh
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
-
low Dangerous commands
cmd-cron-mentionscripts/status.sh:156Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "memory-compression-system"; then
Files scanned: 11. 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: scripts/repair.sh - warning
missing-refreference to a missing file: scripts/rebuild-index.sh - warning
missing-refreference to a missing file: scripts/diagnose.sh - warning
missing-refreference to a missing file: examples/troubleshooting.md
Process rating: all ten parameters 46/100
- 0Tools and files. 4 referenced file(s) missing: scripts/repair.sh, scripts/rebuild-index.sh, scripts/diagnose.sh
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 113 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2720 tokens
- 100Progress reporting. Reports progress
- low 16 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)
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 160: enough signal without eating the budget
- +4Structure: 60 headings
- +3Step-by-step instructions: 113 items
- +3Output format is stated explicitly
- +4Has examples (19 code blocks)
- +3All 7 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.