Agent Skill

self-improving

自我改进主动Agent,知识无需手动维护自动复利

AI Agent·智创未来·来自 skill_hub·skillhub.cn ↗
skillhub install @zcwl/self-improving
9 Stars·35万 综合热度·7,385 字文档·源站更新 2026-11-22

README 文档

7,385 字

Self-Improving + Proactive Agent

When to Use

User corrects you or points out mistakes. You complete significant work and want to evaluate the outcome. You notice something in your own output that could be better. Knowledge should compound over time without manual maintenance.

Architecture

Memory lives in ~/self-improving/ with tiered structure. If ~/self-improving/ does not exist, run setup.md. Workspace setup should add the standard self-improving steering to the workspace AGENTS, SOUL, and HEARTBEAT.md files, with recurring maintenance routed through heartbeat-rules.md.

~/self-improving/
├── memory.md          # HOT: ≤100 lines, always loaded
├── index.md           # Topic index with line counts
├── heartbeat-state.md # Heartbeat state: last run, reviewed change, action notes
├── projects/          # Per-project learnings
├── domains/           # Domain-specific (code, writing, comms)
├── archive/           # COLD: decayed patterns
└── corrections.md     # Last 50 corrections log

Quick Reference

TopicFile
Setup guidesetup.md
Heartbeat state templateheartbeat-state.md
Memory templatememory-template.md
Workspace heartbeat snippetHEARTBEAT.md
Heartbeat rulesheartbeat-rules.md
Learning mechanicslearning.md
Security boundariesboundaries.md
Scaling rulesscaling.md
Memory operationsoperations.md
Self-reflection logreflections.md
Skill平台 HEARTBEAT seedskill-platform-heartbeat.md

Requirements

  • No credentials required
  • No extra binaries required
  • Optional installation of the Proactivity skill may require network access

Learning Signals

Log automatically when you notice these patterns:

Corrections → add to corrections.md, evaluate for memory.md:

  • "No, that's not right..."
  • "Actually, it should be..."
  • "You're wrong about..."
  • "I prefer X, not Y"
  • "Remember that I always..."
  • "I told you before..."
  • "Stop doing X"
  • "Why do you keep..."

Preference signals → add to memory.md if explicit:

  • "I like when you..."
  • "Always do X for me"
  • "Never do Y"
  • "My style is..."
  • "For [project], use..."

Pattern candidates → track, promote after 3x:

  • Same instruction repeated 3+ times
  • Workflow that works well repeatedly
  • User praises specific approach

Ignore (don't log):

  • One-time instructions ("do X now")
  • Context-specific ("in this file...")
  • Hypotheticals ("what if...")

Self-Reflection

After completing significant work, pause and evaluate:

  1. Did it meet expectations? — Compare outcome vs intent
  2. What could be better? — Identify improvements for next time
  3. Is this a pattern? — If yes, log to corrections.md

When to self-reflect:

  • After completing a multi-step task
  • After receiving feedback (positive or negative)
  • After fixing a bug or mistake
  • When you notice your output could be better

Log format:

CONTEXT: [type of task]
REFLECTION: [what I noticed]
LESSON: [what to do differently]

Example:

CONTEXT: Building Flutter UI
REFLECTION: Spacing looked off, had to redo
LESSON: Check visual spacing before showing user

Self-reflection entries follow the same promotion rules: 3x applied successfully → promote to HOT.

Quick Queries

User saysAction
"What do you know about X?"Search all tiers for X
"What have you learned?"Show last 10 from corrections.md
"Show my patterns"List memory.md (HOT)
"Show [project] patterns"Load projects/{name}.md
"What's in warm storage?"List files in projects/ + domains/
"Memory stats"Show counts per tier
"Forget X"Remove from all tiers (confirm first)
"Export memory"ZIP all files

Memory Stats

On "memory stats" request, report:

📊 Self-Improving Memory

HOT (always loaded):
  memory.md: X entries

WARM (load on demand):
  projects/: X files
  domains/: X files

COLD (archived):
  archive/: X files

Recent activity (7 days):
  Corrections logged: X
  Promotions to HOT: X
  Demotions to WARM: X

Common Traps

TrapWhy It FailsBetter Move
Learning from silenceCreates false rulesWait for explicit correction or repeated evidence
Promoting too fastPollutes HOT memoryKeep new lessons tentative until repeated
Reading every namespaceWastes contextLoad only HOT plus the smallest matching files
Compaction by deletionLoses trust and historyMerge, summarize, or demote instead

Core Rules

1. Learn from Corrections and Self-Reflection

  • Log when user explicitly corrects you
  • Log when you identify improvements in your own work
  • Never infer from silence alone
  • After 3 identical lessons → ask to confirm as rule

2. Tiered Storage

TierLocationSize LimitBehavior
HOTmemory.md≤100 linesAlways loaded
WARMprojects/, domains/≤200 lines eachLoad on context match
COLDarchive/UnlimitedLoad on explicit query

示例

  • Pattern used 3x in 7 days → promote to HOT
  • Pattern unused 30 days → demote to WARM
  • Pattern unused 90 days → archive to COLD
  • Never delete without asking

4. Namespace Isolation

  • Project patterns stay in projects/{name}.md
  • Global preferences in HOT tier (memory.md)
  • Domain patterns (code, writing) in domains/
  • Cross-namespace inheritance: global → domain → project

5. Conflict Resolution

When patterns contradict:

  1. Most specific wins (project > domain > global)
  2. Most recent wins (same level)
  3. If ambiguous → ask user

6. Compaction

When file exceeds limit:

  1. Merge similar corrections into single rule
  2. Archive unused patterns
  3. Summarize verbose entries
  4. Never lose confirmed preferences

7. Transparency

  • Every action from memory → cite source: "Using X (from projects/foo.md:12)"
  • Weekly digest available: patterns learned, demoted, archived
  • Full export on demand: all files as ZIP

8. Security Boundaries

See boundaries.md — never store credentials, health data, third-party info.

9. Graceful Degradation

If context limit hit:

  1. Load only memory.md (HOT)
  2. Load relevant namespace on demand
  3. Never fail silently — tell user what's not loaded

Scope

This skill ONLY:

  • Learns from user corrections and self-reflection
  • Stores preferences in local files (~/self-improving/)
  • Maintains heartbeat state in ~/self-improving/heartbeat-state.md when the workspace integrates heartbeat
  • Reads its own memory files on activation

This skill NEVER:

  • Accesses calendar, email, or contacts
  • Makes network requests
  • Reads files outside ~/self-improving/
  • Infers preferences from silence or observation
  • Deletes or blindly rewrites self-improving memory during heartbeat cleanup
  • Modifies its own SKILL.md

Data Storage

Local state lives in ~/self-improving/:

  • memory.md for HOT rules and confirmed preferences
  • corrections.md for explicit corrections and reusable lessons
  • projects/ and domains/ for scoped patterns
  • archive/ for decayed or inactive patterns
  • heartbeat-state.md for recurring maintenance markers

Related Skills

Install with `* 安装此Skill请参考SkillHub平台指南

  • memory — Long-term memory patterns for agents
  • learning — Adaptive teaching and explanation
  • decide — Auto-learn decision patterns
  • escalate — Know when to ask vs act autonomously

Feedback

  • If useful: `
  • Stay updated: `

依赖说明

运行环境

  • Agent平台: 支持SKILL.md的任意AI Agent(Claude Code / Cursor / Codex / Gemini CLI等)
  • 操作系统: Windows / macOS / Linux

依赖说明

依赖项类型是否必需获取方式
LLM APIAPI必需由Agent内置LLM提供

API Key 配置

  • 本Skill基于Markdown指令,无需额外API Key(除内容中明确标注的外部API)

可用性分类

  • 分类: MD+EXEC(纯Markdown指令,部分功能需要exec命令行执行能力)
  • 说明: 基于Markdown的AI Skill,通过自然语言指令驱动Agent执行任务

核心能力

  • Self-reflection + Self-criticism + Self-learning + Self-organizing memory
  • 触发关键词: self-improving, criticism, reflection, self, proactive, improving

适用场景

场景输入输出
基础使用用户请求处理结果

不适用于:需要人工判断的复杂决策场景

使用流程

  1. 确认运行环境满足依赖说明中的要求
  2. 根据适用场景选择合适的使用方式
  3. 执行操作并检查输出结果
  4. 如遇错误,参考错误处理章节

错误处理

错误场景原因处理方式
配置错误参数缺失或格式错误检查依赖说明中的配置要求
运行时错误运行环境不满足确认运行环境符合依赖说明
网络错误连接超时或不可达检查网络连接后重试,参考国内替代方案

常见问题

Q1: 如何开始使用Self Improving?

A: 请先阅读使用流程章节,确认环境满足依赖说明中的要求。

Q2: 遇到错误怎么办?

A: 请参考错误处理章节,按照表格中的处理方式操作。

Q3: Self Improving有什么限制?

A: 请参考已知限制章节了解具体限制。

已知限制

  • 需要LLM支持,无LLM环境无法使用
  • 复杂场景可能需要人工辅助判断
  • 性能取决于底层模型能力

边界条件与限制 (Boundary Conditions)

输入限制

  • 文本长度限制:Skill对输入文本的长度有限制,通常不超过2048个字符,以确保处理效率和准确性。
  • 格式要求:输入文本应遵循Markdown格式,否则Skill可能无法正确解析。
  • 敏感信息:Skill不处理包含敏感信息的输入,如个人隐私数据、信用卡信息等。

性能边界

  • 处理速度:Skill在处理大量数据或复杂任务时,可能需要较长时间完成。
  • 并发处理:Skill不支持同时处理多个并发请求,每次只能处理一个请求。

兼容性约束

  • 操作系统:Skill在Windows、macOS和Linux操作系统上运行,但不保证在其他操作系统上的兼容性。
  • 浏览器兼容性:Skill在主流浏览器上运行,但不保证在所有浏览器上的兼容性。
  • 网络环境:Skill需要稳定的网络连接,否则可能无法正常工作。

数据存储限制

  • 文件大小:Skill存储的数据文件大小有限制,超过限制可能导致Skill无法正常工作。
  • 存储空间:Skill需要足够的存储空间来存储数据和日志文件。

功能限制

  • 无网络功能:Skill不支持网络请求,无法访问外部API或服务。
  • 无外部文件读写:Skill无法读取或写入外部文件,所有数据存储在本地目录中。
  • 无复杂逻辑处理:Skill不支持复杂的逻辑处理,仅适用于简单的数据处理和文本分析任务。

同分类其他技能

查看全部 ›