Self-Improvement

Use this skill to capture lessons that should change future behavior.

• Log failures to .learnings/ERRORS.md — what failed, why, and the fix attempt.
• Log corrections and insights to .learnings/LEARNINGS.md — what was wrong and the better way.
• Log missing capabilities to .learnings/FEATURE_REQUESTS.md — the gap, impact, and desired behavior.
• Before major work, scan the recent entries in all .learnings/ files.
• Promote recurring lessons to the right workspace file:
  • AGENTS.md → workflow change
  • SOUL.md → behavior or tone
  • TOOLS.md → tool-specific gotcha
  • MEMORY.md → persistent fact
• Keep entries concise: one line per entry.
• Do not create weekly reports; rely on just-in-time review.
• Ignore random thoughts that do not affect future behavior.

When to write

Write immediately after:

• a command fails
• a user corrects you
• a capability is missing
• an external tool or API fails
• knowledge is outdated
• you discover a better recurring approach

When to review

Review recent learnings before:

• architectural or workflow changes
• repeating a task that previously failed
• major edits to skills or memory-related files

Minimal operating loop

1. Capture the lesson.
2. Decide whether it belongs in learnings or a workspace file.
3. Promote it only if it is broadly reusable.
4. Move on.