Self-Improving + Proactive Agent

Store agent corrections and preferences in local memory files.

103|14|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/szsip239/teamclaw --skill self-improving-proactive-agent-szsip239
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Self-Improving + Proactive Agent
Source: https://github.com/szsip239/teamclaw/tree/main/data/skills/self-improving
Command: npx skills add https://github.com/szsip239/teamclaw --skill self-improving-proactive-agent-szsip239

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agents lack persistent, structured memory to learn from corrections and maintain long-term quality of work. This skill provides a local, versioned memory and heartbeat-driven workflow to compound execution over tasks.

Core Features & Use Cases

  • Memory management: HOT memory for confirmed rules, WARM namespaces for domains and projects, and COLD archives for decayed patterns.
  • Corrections & learning: logs corrections, promotes patterns to confirmed preferences, and tracks evolution over time across contexts.
  • Proactive execution: preloads relevant memory before non-trivial work, suggests follow-up actions, and maintains heartbeat-driven maintenance to safeguard learning.
  • Use cases: after user feedback, across recurring tasks, or when reducing repeating mistakes in agent workflows.

Quick Start

Load ~/self-improving/memory.md before starting non-trivial work.

Frequently Asked Questions about Self-Improving + Proactive Agent

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

FAQPage Schema
How do I make an agent learn from corrections and remember preferences across tasks?

To make an agent learn from corrections, you need a persistent memory system that logs user feedback and promotes recurring patterns into confirmed rules. This skill maintains a local memory of preferences and lessons across global, domain, and project namespaces to improve execution quality over time.

How does local agent memory work for recurring workflows?

Local agent memory works by storing state in a local directory using markdown files for hot, warm, and cold tiers. It preloads relevant rules before non-trivial work and uses a heartbeat-driven maintenance workflow to safeguard learning and compound execution quality across repetitive tasks.

Can I manage agent memory separately for different projects and domains?

Yes, you can manage agent memory separately using namespaced structures. This skill organizes memory into global, domain, and project namespaces, allowing the agent to apply specific rules and lessons contextually during non-trivial tasks without cross-contaminating preferences.

What is the best way to stop an agent from repeating the same mistakes?

The best way to stop repeating mistakes is to log them explicitly in a corrections file. This skill tracks these corrections, identifies recurring patterns, and promotes them to confirmed preferences in its memory system, actively preventing the same errors in future workflows.

Do I need network access to maintain persistent memory for my agent?

No, you do not need network access to maintain persistent memory. This skill operates entirely offline, storing state and managing heartbeat-driven maintenance locally on your machine to ensure data privacy and uninterrupted execution.

How do I archive decayed patterns and rules in agent memory?

To archive decayed patterns, the memory system automatically moves outdated rules into a cold archive tier. This skill manages the lifecycle of learned preferences, moving confirmed rules from hot memory to cold archives when they are no longer actively needed.