lesson-curator

Capture, classify, and govern engineering lessons with lifecycle states and taxonomy.

1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/wangbinquan/skills --skill lesson-curator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lesson-curator
Source: https://github.com/wangbinquan/skills/tree/main/.claude/skills/lesson-curator
Command: npx skills add https://github.com/wangbinquan/skills --skill lesson-curator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Engineering work generates a lot of tacit knowledge in the form of lessons, but without governance they become scattered, duplicated, or forgotten. Lesson-curator provides a structured, auditable workflow to capture, classify, and preserve actionable engineering lessons as reusable knowledge assets.

Core Features & Use Cases

  • Centralized taxonomy and categories to avoid duplicates and conflicting guidance.
  • Lifecycle management (active, validated, stable, superseded, deprecated) with audit trails.
  • Templates and standardized fields (Symptom, Root cause, Fix, Generalizable lesson, Evidence) to ensure high-quality entries.
  • Cross-linking between related lessons and postmortems to build a navigable knowledge graph.
  • Use Case: after a production incident or code review, capture the lessons and surface them during future projects.

Quick Start

Initiate a new lesson by describing the observed symptom, root cause, concrete fix, and a generalizable lesson, then follow the governance prompts to store and index it.

Frequently Asked Questions about lesson-curator

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

FAQPage Schema
How do I capture engineering lessons from postmortems to prevent duplicated knowledge entries?

Capture engineering lessons by documenting the symptom, root cause, fix, generalizable lesson, and evidence. Use a centralized taxonomy and standardized templates to classify entries, preventing duplicates and ensuring high-quality, reusable knowledge assets.

What is the best way to govern engineering lessons across multiple projects and languages?

Govern engineering lessons by applying a controlled workflow with lifecycle states like active, validated, stable, superseded, and deprecated. This taxonomy and indexing approach enables cross-project and cross-language reuse while maintaining auditability.

How do I structure a postmortem lesson to make it a reusable knowledge asset?

Structure a postmortem lesson using standardized fields: Symptom, Root cause, Fix, Generalizable lesson, and Evidence. This enforces a controlled workflow that ensures high-quality entries and cross-links related lessons to build a navigable knowledge graph.

Can I manage the lifecycle states of engineering lessons to ensure auditability?

Yes, manage engineering lessons through lifecycle states including active, validated, stable, superseded, and deprecated. These states enforce a controlled workflow with audit trails to ensure repeatability and prevent conflicting guidance.

When do I need a taxonomy for engineering lesson curation?

You need a taxonomy for engineering lesson curation when engineering work generates scattered or duplicated tacit knowledge. A centralized taxonomy classifies lessons from bug fixes and reviews, enabling cross-linking and preventing low-quality entries.

Does lesson curation work for both code reviews and production incident retrospectives?

Yes, lesson curation works for code reviews and production incident retrospectives. It provides a structured workflow to capture actionable lessons during these events and surfaces them as reusable knowledge assets for future projects.