BC lily-memory
Persistent memory plugin for OpenClaw agents. Hybrid SQLite FTS5 keyword + Ollama vector semantic search with auto-capture, auto-recall, stuck-detection, and memory consolidation.
As a process C 59/100 · Has gaps — weak spots: result and completion, when it triggers, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:64High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…FSj+bWLt…2sH/Kn8E…h6w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:168High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…wHD+vkj3…wBQ/hCAQ…tUp/3Qh6…OOw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:174High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…CpK+FtMRQVdIMN6/Df5j…tIC+7KYK…qaA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:227High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…RFW+TK4J…oUr/txX3…6Ns/A==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:251High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…JgI+2Q5U…e1E+Nyvgdz/aIyN…n58/GELp3+w==",
detector
Files scanned: 20. 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 59/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 782 tokens
- 100Running it twice. No mutating operations
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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 179: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.
External checks
ClawHub: suspicious
This memory skill mostly does what it says, but it can automatically alter OpenClaw session files on startup without a clear opt-in or prominent disclosure.
LLM: suspicious (high) · VirusTotal: benign · 28 May 2026