BC clawvault-memory
Durable-memory + self-improving workflow for the ClawVault plugin. REQUIRES the ClawVault plugin: install with 'openclaw plugins install clawhub:openclaw-plugin-clawvault' using the FULL name - the short clawhub:clawvault is an unrelated package by another author and does not provide the clawvault_* tools this skill calls. Activate whenever the user asks you to remember or recall, when a fact is worth keeping, OR when something fails, the user corrects you, or you find a better approach. Captures lessons, detects recurring patterns, promotes proven ones, and enforces write-before-respond, search-before-answer, and verify-before-save so memory holds checked facts, not guesses. Stores conversation-derived memories in a local SQLite database that persists across sessions.
Durable-memory + self-improving workflow for the ClawVault plugin.
As a process C 61/100 · Has gaps — weak spots: result and completion, 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 3, column 14: description: Durable-memory + self-improving workflow for the ClawVault plugin.… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (bash, read, web, node) that frontmatter does not declare
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3377 tokens
- 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 12 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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 779: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.