agentleFS
YiShu5YiShu5/claude-skills/skills/self-improving-agent/SKILL.md

self-improving-agent

Skill131 starsChanged 55 days agoMITView on GitHub

Low-noise self-improvement skill. Captures learnings, errors, and corrections into a local `.learnings/` cache layer. Never auto-promotes to long-term memory files (SOUL.md, MEMORY.md, AGENTS.md, TOOLS.md). Promotion requires explicit user approval after repeated validation.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tavily-search, proactive-agent and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • caicongyangSkill

    tavily-search

    Tavily 搜索工具,提供 AI 优化的搜索结果。每月免费 1000 次查询。

    Also in 5 projects that use this

  • halthelobsterSkill

    proactive-agent

    Transform AI agents from task-followers into proactive partners that anticipate needs and continuously improve. Now with WAL Protocol, Working Buffer for context survival, Compaction Recovery, and battle-tested security patterns. Part of the Hal Stack 🦞

    Also in 3 projects that use this

  • LaoK2017Skill

    skill-vetter

    Security review and audit tool for AI agent skills. Use when asked to "vet a skill", "check skill security", "audit a skill", or when reviewing skills before installation to detect malicious code, unauthorized access, and suspicious patterns.

    Also in 3 projects that use this

  • MicrosoftSkill

    web-search

    Also in 4 projects that use this

  • VercelSkill

    find-skills

    Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

    Also in 7 projects that use this

  • OpenAISkill

    brainstorming

    You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write to cache first: All observations go to .learnings/.

    line 34
  2. Distinctive:

    MEMORY.md is for stable truths: Only long-term preferences, decisions, and goals belong there.

    line 37
  3. Distinctive:

    Silence is better than noise: If unsure whether something is worth logging, don't log it.

    line 39
  4. Distinctive:

    No cross-session broadcasting of raw learnings: Only promote distilled, verified content.

    line 40
  5. Distinctive:

    Don't log obvious things. "Python needs indentation" is not a learning.

    line 106
  6. Distinctive:

    Don't log things already in the codebase or docs.

    line 107
  7. Distinctive:

    Prefer updating an existing entry over creating a duplicate.

    line 109
  8. Distinctive:

    When in doubt, skip the log.

    line 111

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Self-Improving Agent (Low-Noise Edition)

A conservative self-improvement system that treats .learnings/ as a write-first cache layer. Nothing reaches the main system files without human review.

Quick Reference

ActionTargetAuto?
Log a learning.learnings/LEARNINGS.mdYes
Log an error.learnings/ERRORS.mdYes
Log a feature gap.learnings/FEATURE_REQUESTS.mdYes
Promote to MEMORY.mdRequires user approvalNo
Promote to SOUL.mdRequires user approval + reviewNo
Promote to AGENTS.mdRequires user approvalNo
Promote to TOOLS.mdRequires user approvalNo

Core Principles

  1. Write to cache first. All observations go to .learnings/. No exceptions.
  2. Never auto-promote. The cache is not the system. Promotion is a deliberate act.
  3. SOUL.md is sacred. Modifications require explicit human review every time.
  4. MEMORY.md is for stable truths. Only long-term preferences, decisions, and goals belong there.
  5. Errors and learnings stay separate. Different logs, different purposes.
  6. Silence is better than noise. If unsure whether something is worth logging, don't log it.
  7. No cross-session broadcasting of raw learnings. Only promote distilled, verified content.

Logging Format

Learning Entry

## [YYYY-MM-DD] Category: brief title

- **Type**: correction | knowledge_gap | best_practice
- **Context**: What was happening
- **Learning**: What was learned
- **Confidence**: low | medium | high
- **Promote?**: no (default) | candidate | promoted

Error Entry

## [YYYY-MM-DD] brief description

- **Command/Tool**: What failed
- **Error**: The error message or symptom
- **Root Cause**: What actually went wrong
- **Resolution**: How it was fixed
- **Recurrence**: first | repeated

Feature Request Entry

## [YYYY-MM-DD] brief description

- **Gap**: What capability is missing
- **User Need**: Why it matters
- **Priority**: low | medium | high

Promotion Gates

A cached item may be promoted to a system file only when ALL of these are true:

  1. Repeated — The same insight has appeared in 2+ separate sessions
  2. Verified — The insight was confirmed correct (not a one-off misunderstanding)
  3. User-approved — The user explicitly agrees to promote it
  4. Relevant long-term — It's not a temporary workaround or context-specific hack

Promotion Targets

Content TypeTarget FileExtra Requirement
User preference / long-term decisionMEMORY.mdStable across sessions
Identity / behavior guidelineSOUL.mdHuman review mandatory
Agent capability / role definitionAGENTS.mdVerified in practice
Tool usage pattern / integrationTOOLS.mdTested and confirmed

Promotion Process

  1. Agent proposes promotion with rationale
  2. User reviews the exact content to be written
  3. User explicitly approves
  4. Agent writes to target file
  5. Agent marks the cached entry as Promote?: promoted

Best Practices (Low-Noise)

  • Don't log obvious things. "Python needs indentation" is not a learning.
  • Don't log things already in the codebase or docs.
  • One entry per insight. No walls of text.
  • Prefer updating an existing entry over creating a duplicate.
  • Review .learnings/ periodically. Prune stale entries.
  • When in doubt, skip the log. You can always add it later.

OpenClaw Integration

See references/openclaw-integration.md for how this skill fits into the OpenClaw workspace architecture.

Key Boundaries

┌─────────────────────────────────────┐
│  Main System Layer (protected)      │
│  SOUL.md · MEMORY.md · AGENTS.md   │
│  TOOLS.md                           │
│  ← promotion requires approval →    │
├─────────────────────────────────────┤
│  Cache Layer (free-write)           │
│  .learnings/LEARNINGS.md            │
│  .learnings/ERRORS.md               │
│  .learnings/FEATURE_REQUESTS.md     │
└─────────────────────────────────────┘

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.