AC memory-pipeline
Install, repair, and validate a persistent memory workflow for OpenClaw-style agents using Markdown memory files plus recurring cron jobs. Use when setting up or fixing MEMORY.md / memory/ structures, adding inbox→raw→daily→weekly memory pipelines, creating or auditing memory-related cron jobs, defining how an agent should capture preferences, decisions, todos, project state, and long-term rules across sessions, or introducing structured memory folders such as memory/projects/ and memory/system/.
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 58/100
- 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. 11 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (memory-pipeline) differs from the folder (openclaw-memory-pipeline)
- 70Failures and branches. 6 branches
- 100Tools and files. No external tools needed
- 100Steps. 114 steps
- 100Execution cost. Instruction body is 2290 tokens
- 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 501: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 114 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.