lessons-learned

Consolidates structured failure records into a centralized lessons_learned.json knowledge base.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/pr3t3l/openclaw-config --skill lessons-learned-pr3t3l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lessons-learned
Source: https://github.com/pr3t3l/openclaw-config/tree/main/workspace/skills/lessons-learned
Command: npx skills add https://github.com/pr3t3l/openclaw-config --skill lessons-learned-pr3t3l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automatically captures and codifies failure records into a centralized lessons_learned.json knowledge base, reducing repeated mistakes across cases.

Core Features & Use Cases

  • Automated extraction of structured failure records from case exports.
  • Updates lessons_learned.json with new entries while avoiding duplicates.
  • Supports anti-pattern discovery and knowledge base expansion.

Quick Start

After a case finishes, run the knowledge-base update to ingest structured failures and refresh lessons_learned.json.

Frequently Asked Questions about lessons-learned

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

FAQPage Schema
How do I automate failure analysis to prevent repeated mistakes across cases?

Automated failure analysis prevents repeated mistakes by extracting structured failure records from case exports and consolidating them into a centralized lessons_learned.json knowledge base. It runs after case completion or pipeline failures requiring human intervention.

What is the best way to consolidate structured failure records into a centralized knowledge base?

Consolidating structured failure records into a centralized knowledge base is best handled by reading case exports and updating a lessons_learned.json file. This process adds new entries while avoiding duplicates to support anti-pattern discovery and knowledge base expansion.

When do I need to update my lessons learned knowledge base after a pipeline failure?

You need to update your lessons learned knowledge base after every case completion or pipeline failure requiring human intervention. This ensures structured failure records are ingested and the lessons_learned.json file is refreshed accordingly.

Can I use automated case review to discover anti-patterns in structured failure data?

Automated case review supports anti-pattern discovery by reading structured failure records and related reports from cases/exports. It updates cases/config/lessons_learned.json to expand your knowledge base and codify recurring issues.

Does this knowledge base update process work with unstructured failure reports?

The knowledge base update process reads only structured failure records and related reports from cases/exports. It specifically updates cases/config/lessons_learned.json and does not process unstructured failure data.

How do I avoid duplicate entries when capturing lessons learned from case exports?

To avoid duplicate entries when capturing lessons learned, the skill reads structured failure records from case exports and updates lessons_learned.json with new entries while actively preventing duplication during the ingestion process.