self-improvement

Capture and organize learnings, errors, and feature requests for AI agents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/laurenzseifried/hektor-workspace --skill self-improvement-laurenzseifried
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-improvement
Source: https://github.com/laurenzseifried/hektor-workspace/tree/main/skills/self-improving-agent
Command: npx skills add https://github.com/laurenzseifried/hektor-workspace --skill self-improvement-laurenzseifried

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a structured way to capture learnings, errors, and feature requests, enabling continuous improvement of AI agents and workflows by creating a feedback loop for knowledge refinement.

Core Features & Use Cases

  • Error Logging: Records command failures, API errors, and unexpected behaviors.
  • Learning Capture: Logs corrections, knowledge gaps, and discovered best practices.
  • Feature Request Tracking: Documents user-requested capabilities.
  • Promotion: Facilitates promoting learnings to permanent project memory (e.g., CLAUDE.md, AGENTS.md) or extracting them as new skills.
  • Use Case: When an agent fails to execute a command due to a configuration error, this skill logs the error, its context, and a suggested fix. If this error recurs, it can be promoted to TOOLS.md or even become a new skill for future reference.

Quick Start

Log a new learning by appending a markdown entry to the .learnings/LEARNINGS.md file.

Frequently Asked Questions about self-improvement

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

FAQPage Schema
How do I log agent errors and learning opportunities for continuous improvement?

Agent errors and learning opportunities are logged by appending structured markdown entries to a `.learnings/LEARNINGS.md` file, capturing command failures, user corrections, and knowledge gaps for future reference.

What is the best way to capture AI agent feedback loops and recurring command failures?

AI agent feedback loops are captured through automated hook integration that detects command failures and unexpected behaviors, logging their context and suggested fixes to facilitate continuous workflow improvement.

How do I promote discovered best practices into permanent project memory?

Discovered best practices are promoted by elevating logged insights to permanent project memory files such as `CLAUDE.md`, `AGENTS.md`, or `TOOLS.md`, ensuring recurring corrections persist across future agent sessions.

Can I extract recurring error fixes into reusable skills for my development workflow?

Recurring error fixes can be extracted as new reusable skills, transforming repeated command failures and documented knowledge gaps into structured capabilities that prevent identical errors in future development workflows.

Does this continuous improvement approach work without external dependencies?

This continuous improvement approach works without external dependencies, relying solely on internal scripts, references, and assets to manage structured logging of feature requests, errors, and best practices.

When should I not use a structured learning log for AI agent knowledge management?

Structured learning logs should not be used for ephemeral errors or one-off command failures that lack reusable context, as the overhead of logging outweighs the benefit when insights cannot be promoted to permanent memory.