compact-guardian

Trigger a circuit-breaker after three consecutive memory-lancedb-pro compaction failures.

Updated Apr 3, 2026

Search Tags:#automation #memory #guardian #compression #workflows #failures #telegram

Ready to run

npx skills add https://github.com/Ghenghis/openclaw-claude-code-integration --skill compact-guardian-ghenghis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: compact-guardian
Source: https://github.com/Ghenghis/openclaw-claude-code-integration/tree/main/skills/compact-guardian
Command: npx skills add https://github.com/Ghenghis/openclaw-claude-code-integration --skill compact-guardian-ghenghis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

压缩熔断守护。当 memory-lancedb-pro 自动压缩（auto compaction）连续失败 3 次时，熔断机制触发，停止当前 session 的自动压缩并通过 Telegram 通知用户手动 /compact 处理。在记忆压缩失败后，激活此 skill 进行熔断检查。

Core Features & Use Cases

自动监控 memory-lancedb-pro 的自动压缩流程并在连续失败时触发熔断
通过 Telegram 通知用户并阻断相关会话的后续自动压缩，等待手动修复
提供 fail、guardian、success、reset 子命令用于逐步记录失败、检查熔断、重置计数并清理会话

Quick Start

在 memory-lancedb-pro 自动压缩连续失败时，运行 compact-guardian 来触发熔断并通过 Telegram 通知用户以便手动处理。

Frequently Asked Questions about compact-guardian

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I stop memory auto compaction when it fails repeatedly?▼

You can stop memory auto compaction failures by triggering a circuit-breaker that halts automatic compression for the affected session after three consecutive failures. The mechanism then notifies you via Telegram to intervene manually.

What is a circuit-breaker for memory compaction workflows?▼

A memory compaction circuit-breaker is a safeguard that monitors automatic compression processes and trips after three consecutive failures. It stops further automated attempts in the affected gateway session and alerts the user through Telegram.

How do I reset the failure counter after manually fixing memory compression?▼

To reset the failure counter after manually fixing memory compression, you run the success command on the affected session. This clears the failure tracking, deactivates the circuit-breaker, and resumes normal automated workflows.

Do I need Telegram to receive notifications for compression failures?▼

Yes, Telegram is required to receive notifications when the circuit-breaker triggers. The system sends an alert to notify you that automatic compression has been halted and a manual /compact intervention is required.

Can I track per-session compression failures across gateway sessions?▼

Yes, the guardian mechanism tracks per-session compression failures independently across gateway sessions. It exposes fail, guardian, success, and reset commands to increment, check, clear, and manage the failure counters for each specific session.

Why does automatic memory compression stop after three failures?▼

Automatic memory compression stops after three failures because the circuit-breaker mechanism is designed to prevent continuous error loops. By halting the process and requiring a manual /compact command, it ensures the underlying issue is resolved before automation resumes.