BD memory-transfer
Transfer memory files between OpenClaw agents with support for topic-specific transfers and two modes: memory sharing (with role transformation) and memory cloning (verbatim copy). Use when: (1) Migrating memory from main agent to sub-agent, (2) Sharing specific topic memories between agents, (3) Copying user preferences to new agents, (4) Backing up agent memory before resets.
As a process D 46/100 · Unfinished process — 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: 4. 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 2, column 14: description: Transfer memory files between OpenClaw agents with support for top… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (memory-transfer) differs from the folder (memory-transfer-enhanced)
- 100Tools and files. No external tools needed
- 100Steps. 40 steps
- 100Execution cost. Instruction body is 1423 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 380: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.