openclaw-reflect

Detect recurring tool-outcome failures and generate memory-augmentation proposals.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/velamints2/clawbot-lab --skill openclaw-reflect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-reflect
Source: https://github.com/velamints2/clawbot-lab/tree/main/skills/openclaw-reflect
Command: npx skills add https://github.com/velamints2/clawbot-lab --skill openclaw-reflect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill enables autonomous observation of tool outcomes across sessions, detects recurring failure patterns, and proposes memory-driven improvements that guide safer agent behavior over time.

Core Features & Use Cases

  • Observes outcomes and classifies recurring patterns across multiple sessions.
  • Proposes tiered memory updates (MEMORY.md, CLAUDE.md, SOUL.md) with evaluator-backed validation.
  • Provides rollback support via pre-change snapshots and optional ledger integration.
  • Auto-applies low-risk changes while queuing higher-risk proposals for operator review.

Quick Start

End a session to trigger the full pipeline automatically.

Frequently Asked Questions about openclaw-reflect

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

FAQPage Schema
How do I stop recurring tool-outcome failures from repeating across agent sessions?

To stop recurring tool-outcome failures, you need cross-session failure pattern detection that identifies repeated issues and proposes memory-driven improvements to guide safer agent behavior over time. This skill observes outcomes and classifies recurring patterns automatically.

How does evaluator-backed self-improvement for autonomous agents work?

Evaluator-backed self-improvement works by validating proposed memory updates against an evaluator before applying them. It auto-applies low-risk changes to memory files while queuing higher-risk proposals for operator review, ensuring safe agent behavior modification.

What's the best way to apply memory updates to agent configuration files safely?

The best way to safely apply memory updates is using tiered validation that applies low-risk changes to MEMORY.md and CLAUDE.md automatically, while routing high-risk proposals to SOUL.md for operator approval. Pre-change snapshots provide rollback support.

Does this agent self-improvement approach require operator gating for every change?

Operator gating is optional and only required for high-risk changes queued to SOUL.md. Low-risk memory augmentations are auto-applied to MEMORY.md and CLAUDE.md without operator intervention, balancing autonomy with safety.

Can I roll back memory augmentation changes if they degrade agent performance?

Yes, you can roll back memory augmentation changes using pre-change snapshots stored in the .reflect directory. The rollback support feature captures state before applying updates, allowing you to restore previous configurations if performance degrades.

When do I need cross-session recurrence checks for agent memory management?

Cross-session recurrence checks are needed when agents experience repeated tool-outcome failures across multiple sessions. This pattern detection identifies recurring issues that require memory-driven improvements to prevent future failures and increase reliability.