AI Agent Hub
Back to skills
Self-Improving + Proactive Agent icon

Self-Improving + Proactive Agent

AI Agent Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Install @user_5e5107f8/self-improving-pro-pro using the official guide at https://skillhub.cn/install/skillhub.md.

About this skill

Problem

Long agent conversations have a memory gap: the agent repeats mistakes, loses stated preferences, or overfits one-off instructions. Manual prompt maintenance does not scale. This skill turns explicit user corrections, confirmed preferences, and self-reflection into local memory files, so useful patterns compound over time instead of disappearing when context resets.

How It Works

  • Learning signals: captures explicit corrections (“No, that's not right...”), direct preferences (“Always do X for me”), and repeated useful patterns; ignores one-time instructions, context-specific details, and hypotheticals.
  • Tiered storage: memory.md is HOT and always loaded, capped around 100 lines; projects/ and domains/ are WARM and loaded on context match; archive/ is COLD and loaded only on explicit query.
  • Promotion and decay: a pattern used 3 times in 7 days can move to HOT; unused for 30 days drops to WARM; unused for 90 days moves to COLD, with deletion only after confirmation.
  • Conflict resolution: more specific namespaces win, project > domain > global; same-level conflicts use recency; ambiguous cases ask the user.
  • Transparency: memory-driven behavior should cite the source, for example “Using X (from projects/foo.md:12)”.

Boundaries

It reads only files under ~/self-improving/, makes no network requests, and does not access calendar, email, contacts, or modify its own SKILL.md. It should not store credentials, health data, or third-party information. When context is tight, it should load HOT first and explicitly state what remains unloaded rather than failing silently.

Use Cases

  • After multi-step code reviews, store repeated user formatting corrections in project-scoped memory to avoid repeating them.
  • In ongoing writing collaboration, save explicit title and terminology preferences to HOT memory and load them by context.
  • After a bug fix, log self-reflection improvements to corrections.md and promote them only after three validated uses.
  • Isolate project and domain patterns in a cross-project workspace so global preferences do not pollute project output.

Best For

  • Engineers maintaining multi-project AI workflows who need project-scoped code and documentation preferences.
  • Technical writers collaborating with agents who need stable recall of title, terminology, and formatting preferences.
  • Platform owners debugging agent behavior who want to audit memory sourcing, promotion, and decay rules.
  • Ops engineers managing local agent state who need it confined to self-improving files and offline.