self-improvement

Logs errors, learnings, and feature requests into a structured format.

375|38|Updated Dec 2, 2025
One-click install
npx skills add https://github.com/CraftOS-dev/CraftBot --skill self-improvement-craftos-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-improvement
Source: https://github.com/CraftOS-dev/CraftBot/tree/main/skills/self-improving-agent
Command: npx skills add https://github.com/CraftOS-dev/CraftBot --skill self-improvement-craftos-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps agents and developers continuously improve by systematically capturing, logging, and promoting learnings, errors, and feature requests encountered during development.

Core Features & Use Cases

  • Error Logging: Records command failures, exceptions, and unexpected behaviors.
  • Learning Capture: Logs corrections, insights, and knowledge gaps from interactions.
  • Feature Request Tracking: Documents user-requested capabilities.
  • Promotion: Facilitates promoting learnings to permanent project memory (e.g., CLAUDE.md, AGENTS.md).
  • Skill Extraction: Provides a workflow to turn valuable learnings into reusable skills.
  • Use Case: When an agent encounters a bug, it logs the error details. If a user corrects the agent's output, that correction is logged. These logs can then be reviewed to fix bugs, update documentation, or even create new skills for recurring problems.

Quick Start

Use the self-improvement skill to log a critical error encountered during a recent command execution.

Frequently Asked Questions about self-improvement

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

FAQPage Schema
How do I log errors and learnings for continuous improvement in software development?

Continuous improvement is achieved by capturing command failures, exceptions, and insights in a structured format. The skill automatically detects errors via hooks and supports manual logging for developers to systematically record interactions.

Can I promote captured learnings to permanent project memory files like CLAUDE.md?

Promoting learnings to permanent project memory involves moving structured logs into files like CLAUDE.md or AGENTS.md. This facilitates capturing corrections and knowledge gaps permanently for future project reference.

How do I extract reusable skills from recurring development errors?

Skill extraction from recurring errors uses a structured workflow to turn valuable learnings into reusable skills. By reviewing logged command failures and user corrections, developers can create new skills to prevent similar problems.

Does automatic error logging work with hooks for command failures and exceptions?

Automatic error logging via hooks records command failures, exceptions, and unexpected behaviors without manual intervention. This mechanism systematically captures errors encountered during development interactions for later review.

What is the best way to track feature requests and knowledge gaps during agent interactions?

Tracking feature requests and knowledge gaps requires documenting user-requested capabilities and logging corrections from interactions. This structured approach ensures insights are captured for future bug fixes and documentation updates.

When should I not use automatic logging for continuous improvement?

Automatic logging for continuous improvement may not suit contexts requiring manual curation of learnings or when hook-based error detection conflicts with existing project memory workflows. Manual logging provides more control over captured insights.