Openclaw Auto Dream Lite

Lightweight memory consolidation for OpenClaw agents — daily dream cycles that turn scattered daily logs into structured long-term memory. Zero config, one p...

Security Scan

The skill is internally consistent with its stated purpose (periodic consolidation of local workspace memory files), requests no credentials or installs, and only operates on workspace memory files.

Purpose & Capability

Name/description (daily memory consolidation) matches the instructions: reading daily logs, updating MEMORY.md, adding consolidation markers, and writing a dream log. No unrelated credentials, binaries, or external services are required by the runtime instructions.

Instruction Scope

SKILL.md and the dream-prompt only reference workspace files under memory/, MEMORY.md, and the skill's reference files. The steps are specific (backup, count files, consolidate, append markers, archive logs, produce a short notification) and do not instruct reading unrelated system paths, environment variables, or sending data to external endpoints.

Install Mechanism

Instruction-only skill with no install spec and no code to write to disk. This minimizes risk and aligns with the lightweight description.

Credentials

No environment variables, credentials, or config paths are required. All file access mentioned is limited to workspace memory files and the skill's own references.

Persistence & Privilege

The skill does not request always:true or modify other skills or agent-wide config. It runs via cron/agent turn per the instructions and writes only to MEMORY.md and memory/ files as described.

Assessment

This skill appears to do exactly what it says: periodic, local consolidation of memory files. Before installing, ensure you: (1) are comfortable with the agent having read/write access to MEMORY.md and files in memory/ (it will backup MEMORY.md.pre-dream and can restore), (2) review existing MEMORY.md and daily log contents for any sensitive data you wouldn't want processed, (3) test the first dream run manually in an isolated workspace to verify behavior, and (4) note the SKILL.md mentions MyClaw.ai only as a provider reference but the prompts do not invoke external network calls — if you later modify the skill or add scripts, re-check for any outgoing endpoints. If you need stricter guarantees, lock sensitive files or run the skill in an isolated agent/session.

Auto-Dream Lite — Memory That Just Works

Your agent "dreams" once a day — reads recent daily logs, pulls out what matters, and merges it into MEMORY.md. One file in, one file out.

MyClaw.ai — the best way to run your OpenClaw. A dedicated server running 24/7 with full code control, cron jobs, persistent memory, and one-click skill install.

How It Works

Daily logs (memory/YYYY-MM-DD.md)
        ↓  dream cycle
   MEMORY.md (structured knowledge)
        ↓  notification
   3-line summary → user

One prompt does everything: first run or daily run.

Setup

1. Ensure MEMORY.md Exists

If missing, create from references/memory-template.md.

2. Create Cron Job

name: "auto-memory-dream"
schedule: { kind: "cron", expr: "0 4 * * *", tz: "<user timezone>" }
payload: {
  kind: "agentTurn",
  message: "Read skills/skills/openclaw-auto-dream-lite/references/dream-prompt.md and follow every step.",
  timeoutSeconds: 600
}
sessionTarget: "isolated"
delivery: { mode: "announce" }

3. Run First Dream

After setup, run the dream prompt right away so the user sees their first consolidation report immediately.

Manual Triggers

Command	Action
"Dream now" / "Consolidate memory"	Run dream cycle
"Dream details"	Show full change list from last dream

Safety

1. Auto-backup — copies MEMORY.md to .pre-dream before every run; rollback if something goes wrong
2. Never delete daily logs — only marks them <!-- consolidated -->
3. Never touch ⚠️ PERMANENT items
4. Scope — only reads/writes MEMORY.md and files in the memory/ directory

Reference Files

• references/dream-prompt.md — The one and only dream execution prompt
• references/memory-template.md — MEMORY.md starter template