FC agent-memory-system
OpenClaw Agent 长期记忆系统 - 温度模型 + 自动归档 + 知识提炼。让 AI Agent 拥有持久记忆，自动管理冷热数据，从经验中提炼可复用技能。
Not recommendedcritical or high security findings · low grade F
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 1 more place: ClawHub
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
Dangerous commands
If you install
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
For the author
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 14
-
high Dangerous commands
cmd-persistenceinstall.sh:53Persistence mechanism (cron / launchd / scheduled task / autorun registry)) | crontab - 2>/dev/null || log_warn "无法修改 crontab"
-
high Dangerous commands
cmd-persistenceinstall.sh:215Persistence mechanism (cron / launchd / scheduled task / autorun registry)) | crontab -
-
high Dangerous commands
cmd-persistencescripts/install.sh:54Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null | grep -v "memory-gc.sh" || true; echo "0 0 * * 0 $SCRIPT_DIR/memory-gc.sh") | crontab -
-
high Dangerous commands
cmd-persistencescripts/install.sh:62Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null | grep -v "nightly-reflection.sh" || true; echo "45 23 * * * $SCRIPT_DIR/nightly-reflection.sh") | crontab -
Medium and low: 10
-
low Dangerous commands
cmd-cron-mentioninstall.sh:52Mentions editing / listing crontabcrontab -l 2>/dev/null | grep -v "agent-memory-system" || true
-
low Dangerous commands
cmd-cron-mentioninstall.sh:205Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "agent-memory-system"; then
-
low Dangerous commands
cmd-cron-mentioninstall.sh:210Mentions editing / listing crontabcrontab -l 2>/dev/null || true
-
low Dangerous commands
cmd-cron-mentioninstall.sh:257Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "agent-memory-system"; then
-
low Dangerous commands
cmd-cron-mentionREADME.md:39Mentions editing / listing crontabcrontab -e
-
low Dangerous commands
cmd-cron-mentionscripts/install.sh:50Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "memory-gc.sh"; then
-
low Dangerous commands
cmd-cron-mentionscripts/install.sh:54Mentions editing / listing crontab(crontab -l 2>/dev/null | grep -v "memory-gc.sh" || true; echo "0 0 * * 0 $SCRIPT_DIR/memory-gc.sh") | crontab -
-
low Dangerous commands
cmd-cron-mentionscripts/install.sh:58Mentions editing / listing crontabif crontab -l 2>/dev/null | grep -q "nightly-reflection.sh"; then
-
low Dangerous commands
cmd-cron-mentionscripts/install.sh:62Mentions editing / listing crontab(crontab -l 2>/dev/null | grep -v "nightly-reflection.sh" || true; echo "45 23 * * * $SCRIPT_DIR/nightly-reflection.sh") | crontab -
-
low Dangerous commands
cmd-cron-mentionSKILL.md:116Mentions editing / listing crontabcrontab -e
Files scanned: 12. 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") - note
frontmatter-keyunknown frontmatter key "keywords"
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 34 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 979 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)
- +3Description length 82: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -31 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 28 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.
External checks
ClawHub: suspicious
This memory skill is mostly purpose-aligned, but it needs Review because it can install recurring scheduled jobs and perform under-scoped local file changes.
LLM: suspicious (high) · VirusTotal: · 29 May 2026