Memory Manager

OpenClaw-native memory maintenance, snapshots, indexing health checks, and review workflows. Use when you need to protect context before risky work, troubles...

Security Scan

The skill's purpose and instructions are plausible for managing OpenClaw memory, but the SKILL.md repeatedly references PowerShell scripts that are not bundled, leaving actual behavior ambiguous and making it unsafe to run without inspecting those scripts first.

Purpose & Capability

The name/description match the actions described (snapshots, health checks, archiving). The skill does not request unrelated credentials or installs, which is proportionate. However, it claims a resource layout of several scripts (check.ps1, snapshot.ps1, doctor.ps1, review.ps1, search.ps1, archive.ps1) while providing no script files in the bundle — this mismatch should be explained by the author (they may expect these to live in the user's workspace).

Instruction Scope

Runtime instructions direct the agent (and user) to run pwsh -File scripts/*.ps1 that will read and modify workspace memory files (MEMORY.md and memory/YYYY-MM-DD.md). That is reasonable for a memory manager, but because the actual scripts are not included, there is no way to audit what those scripts do — they could overwrite or exfiltrate data contrary to the 'core rules'. The SKILL.md states safe rules (do not overwrite MEMORY.md), but those rules cannot be enforced without seeing the scripts. The instructions also expect 'openclaw memory search' to be available; the skill does not declare this dependency explicitly beyond examples.

Install Mechanism

No install spec and no code files are provided, so nothing will be written to disk by an installer. This minimizes supply-chain risk. The only runtime dependency implied is PowerShell (pwsh), which is called in examples and noted as intentionally PowerShell-first for portability.

Credentials

The skill requests no environment variables, credentials, or config paths. That is appropriate for a local memory maintenance workflow and reduces risk of secret exfiltration from the skill bundle itself.

Persistence & Privilege

always is false and model invocation is allowed by default (normal). The skill does not request elevated or persistent platform privileges. The primary risk comes from executing external scripts in the workspace, not from the skill having persistent privileges.

What to consider before installing

This SKILL.md describes safe rules and PowerShell scripts for managing your OpenClaw memory, but the actual scripts referenced are not bundled — you should NOT run these commands until you either (a) inspect the scripts that live in your workspace (scripts/check.ps1, snapshot.ps1, doctor.ps1, review.ps1, search.ps1, archive.ps1) or (b) ask the skill author to provide the script sources for review. Ensure pwsh (PowerShell) is available if you plan to run them, make a manual backup of MEMORY.md and your memory/ folder first, and run scripts in a sandbox or with dry-run flags if provided. If you cannot inspect the scripts, treat running them as risky because they could modify or exfiltrate memory files despite the stated rules.

Memory Manager v2

Maintain OpenClaw memory without replacing it.

This skill is for the existing OpenClaw memory model:

• MEMORY.md for curated long-term memory
• memory/YYYY-MM-DD.md for daily notes
• OpenClaw memory_search / memory_get for retrieval

Do not migrate the workspace into a different memory architecture. Do not move canonical daily memory files by default. Do not present keyword grep as semantic search.

Use this skill for

• Pre-compaction or pre-risk memory snapshots
• Memory-search troubleshooting and recovery
• Embedding/index health checks
• Reviewing recent daily notes for durable takeaways
• Safe archival of old daily notes
• Quick memory hygiene/status checks

Resource layout

• scripts/check.ps1 — quick health/status summary
• scripts/snapshot.ps1 — create a safe snapshot from current memory files
• scripts/review.ps1 — generate a review draft from recent daily notes
• scripts/search.ps1 — wrapper around openclaw memory search with keyword fallback
• scripts/doctor.ps1 — diagnose provider/index readiness and attempt repair
• scripts/archive.ps1 — archive older daily notes safely
• references/workflow.md — operating rules and recommended workflows

Core rules

1. Preserve MEMORY.md.
2. Preserve memory/YYYY-MM-DD.md as the canonical daily log format.
3. Never overwrite existing memory files when a safe append or sidecar file is enough.
4. Prefer OpenClaw-native memory commands over homegrown substitutes.
5. Label fallback modes honestly.

Recommended workflows

1) Quick memory health check

Run:

pwsh -File scripts/check.ps1

Use when you want:

• today file existence
• recent daily note count
• snapshot count
• index/provider health summary

2) Troubleshoot memory search

Run:

pwsh -File scripts/doctor.ps1

Use when:

• memory_search is unavailable
• embeddings are failing
• index appears empty
• SQLite lock or provider issues are suspected

To attempt automatic recovery:

pwsh -File scripts/doctor.ps1 -Repair

3) Create snapshot before risky work

Run:

pwsh -File scripts/snapshot.ps1

Use before:

• large refactors
• config changes
• memory cleanup
• provider/index changes
• long sessions likely to compact

4) Review recent memory into durable learnings

Run:

pwsh -File scripts/review.ps1 -Days 7

Use when:

• promoting facts or preferences into MEMORY.md
• summarizing recent activity
• finding repeated themes or decisions

5) Search memory

Run:

pwsh -File scripts/search.ps1 -Query "jobpulse redesign"

Behavior:

• first tries openclaw memory search
• falls back to keyword search only if semantic search fails
• reports which mode was used

6) Archive older daily notes

Run:

pwsh -File scripts/archive.ps1 -KeepDays 30

Use when old daily notes should move out of the main memory/ folder without disturbing recent working memory.

Portability note

These scripts are PowerShell-first because many OpenClaw workspaces run on Windows. They avoid machine-specific paths where possible and accept -Workspace overrides for portability.

Read next

For workflow guidance and safety boundaries, read references/workflow.md.