lucid-dreamer@0.8.0
CAUTION· static onlyPublisher claims: "Nightly AI memory reasoning system. Lucid runs every night while you sleep - it reads your daily notes and memory files, detects stale facts, unresolved todos, recurring problems, forgotten decisions, and can optionally perform aggressive cleanup and contradiction detection. Includes optional session debrief for quick end-of-day memory capture. Zero dependencies, no database, no embeddings. Just a scheduled job and markdown files. Use when you want your AI agent to automatically maintain and improve its long-term memory over time. Triggers on "memory dreamer", "nightly memory review", "lucid", "auto memory", "memory cleanup", "memory hygiene"." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-07 and scored it 71/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Instructs the agent to modify its persistent memory or instruction files; Instructs the agent to modify its persistent memory or instruction files; Instructs the agent to modify its persistent memory or instruction files. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
- MEMORY.md doesn't mention it — no update neededFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.b. Git commit: `cd "${CLAWD_DIR}" && git add MEMORY.md memory/sections && git commit -m "dreamer: cleanup"`Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.3. Run `cd "${CLAWD_DIR}" && git add MEMORY.md memory/index.md memory/sections && git commit -m "dreamer: auto-apply"`Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.lines.append("_Projects in MEMORY.md not mentioned in any daily note for 30+ days._\n")Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.1. Edit the relevant `memory/sections/*.md` file(s) directly when sectioned memory exists; otherwise edit `MEMORY.md`Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- **Update MEMORY.md:** Add note that `scripts/backup-remote.sh` was rewritten 2026-03-15 to use native `openclaw backup create`. Old split-workspace + separate-config approach replaced.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim robbyczgw-cla: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.