Lobster Compact
v1.0.0Summarize long conversations to preserve context. Automatically triggered when context window approaches limits, or manually with /compact.
⭐ 0· 29·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (conversation compaction) matches the runtime instructions: analyze exchanges, create a structured summary, and write summaries to memory files. Nothing requested (no extra env vars or binaries) is out of scope for that purpose.
Instruction Scope
Instructions explicitly require extracting file names, code snippets, errors, and other granular context and then saving them to MEMORY.md and memory/YYYY-MM-DD.md. That is consistent with a compaction skill but means the skill will persist potentially sensitive data (API keys, passwords, private code) unless the agent sanitizes or filters content first. The instructions do not include explicit redaction or sanitization steps.
Install Mechanism
No install step or code files — instruction-only. Lowest risk from installation because nothing is downloaded or written beyond the normal memory writes described in the instructions.
Credentials
No environment variables, credentials, or external config paths are requested. The allowed tools (read/write/edit/memory_search/memory_get) are aligned with the stated memory-writing behavior.
Persistence & Privilege
The skill instructs writing to persistent memory files (MEMORY.md and dated memory logs), which is expected for a compaction tool. always:false and no modifications to other skills are declared. Still, this persistence means summaries (including sensitive content) will be stored long-term — verify memory access controls and retention policies.
Assessment
This skill appears to do what it says: summarize conversations and save those summaries to your agent's memory. Before enabling it, decide if you want full conversation details (file names, code snippets, error traces) stored persistently. Ask or configure the agent to redact secrets (API keys, passwords, private keys) before saving, confirm where memory files are stored, who can access them, and how long they are retained. If you prefer tighter control, use /compact manually rather than allowing autonomous invocation, and periodically review or prune MEMORY.md and dated memory logs.Like a lobster shell, security has layers — review code before you run it.
latestvk9788j9cfx0zx3hyb35rd2p84s8467xc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.