Conv Compactor
v1.0.1多级对话压缩系统。监控上下文长度，在达到阈值时自动或手动触发压缩，将对话历史浓缩为结构化摘要，保留关键信息。
⭐ 0· 69·0 current·0 all-time
by@sinnzen
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (conversation compaction) align with what the skill asks/does: it's instruction-only, requires no binaries/creds, and provides compression prompts and triggers appropriate for the purpose.
Instruction Scope
Overall scoped to compressing in-conversation content. Notable points: it instructs preserving full code snippets and redacting secrets, forbids calling tools ('不要调用工具') yet also suggests optionally writing compressed summaries into the memory-hierarchy; that implies the skill acts on the conversation buffer only and does not explicitly request reading files or external tools. The redaction rules rely on correct agent behavior — if the agent has tool access or file-reading capabilities, unintentional secret leakage could occur unless redaction is correctly applied.
Install Mechanism
No install spec and no code files — instruction-only. This is lowest-risk for on-disk or network installs.
Credentials
Requires no environment variables, credentials, or config paths. The only external interaction mentioned is an optional write to memory-hierarchy, but no credentials/config paths are requested to perform that.
Persistence & Privilege
always:false and no system-wide changes requested. However the SKILL.md encourages automatic invocation when token usage is high and mentions optionally writing compressed summaries into long-term memory; this gives the agent discretion to persist summaries (potential privacy implications) though the skill does not request elevated privileges or config access.
Assessment
This skill appears to do what it says: compress conversation history into structured summaries and asks the agent to redact sensitive items. Before installing, consider: (1) Where will compressed summaries be stored? If you use a memory or long-term store, verify that store's access controls and retention policy. (2) Test the redaction on non-sensitive data first — the prompt instructs redaction but relies on the agent to correctly remove secrets. (3) If you don't want autonomous compression, disable autonomous invocation or add a user-confirm step (the SKILL.md suggests automatic triggering at >80% tokens). (4) If your workflows include reading local files or tools, confirm the agent does not contradict '不要调用工具' by reading files without your consent. If those concerns are acceptable or mitigated, the skill is internally coherent and appropriate to install.Like a lobster shell, security has layers — review code before you run it.
latestvk97683nkdcbyy6yfekzgarv4ad8412ga
License
MIT-0
Free to use, modify, and redistribute. No attribution required.