BC Memory Management / Management System
A practical memory management system for OpenClaw: importance scoring, time-decay cleanup, write triggers, hybrid retrieval, and daily maintenance workflow.
As a process C 55/100 · Has gaps — weak spots: result and completion, consistency, execution cost
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
body-longSKILL.md body ≈ 11123 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "changelog"
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (Memory Management / Management System) differs from the folder (memory-management-lite)
- 40Execution cost. Instruction body is 11123 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Steps. 337 steps, 6 vague phrases
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 11 branches
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 68 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 156: enough signal without eating the budget
- +4Structure: 73 headings
- +3Step-by-step instructions: 337 items
- +4Has examples (39 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.
External checks
ClawHub: suspicious
This memory skill is mostly coherent, but it can persist user information, delete old memory logs, and copy OpenClaw config/API-key-related files during maintenance.
LLM: suspicious (high) · VirusTotal: · 29 May 2026