openclaw-workspace

What problem does it solve?

OpenClaw agents rely on a set of markdown workspace files to define their identity, behavior, memory, and operational rules, but unmanaged workspaces quickly suffer from bloat, redundant content, stale entries, and missing security gates — wasting tokens on every turn, creating contradictory behavior, and risking private memory leaks in group chats.

Core Features & Use Cases

• Workspace Auditing: Scan all workspace files for character count bloat, redundant content across files, stale entries (old SSH hosts, deprecated rules), and missing security gates for private memory files.
• New Workspace Setup: Guide you through creating a fully functional, secure OpenClaw workspace from scratch with the correct file order, boot sequence configuration, and minimal viable file set.
• Memory Distillation: Process daily session logs into a lean, curated MEMORY.md file, promoting recurring lessons and iron-law rules while archiving old logs to free up token budget.
• Use Case: If your agent is sharing private user context in group chats, this skill will help you identify the missing MEMORY.md gating in your AGENTS.md boot sequence and clean up redundant rules across your workspace files to reduce token waste.

Quick Start

Use the openclaw-workspace skill to audit my OpenClaw workspace files for token bloat, redundancy, and security gaps, then propose targeted edits to reduce my per-turn token usage.