learn

Extract non-obvious session learnings and persist them into MEMORY.md.

4|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/d-o-hub/chaotic_semantic_memory --skill learn-d-o-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/d-o-hub/chaotic_semantic_memory/tree/main/.agents/skills/learn
Command: npx skills add https://github.com/d-o-hub/chaotic_semantic_memory --skill learn-d-o-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture non-obvious session learnings and persist insights into a central memory store for future reference and continuous improvement.

Core Features & Use Cases

  • Identify Insight: surface non-obvious takeaways from a session.
  • Verify Novelity: compare against MEMORY.md and existing docs to avoid duplicates.
  • Formulate Pattern: express insights as actionable guidance with clear implementation notes.
  • Save to Memory: append the validated pattern to the appropriate MEMORY.md section for long-term recall and reuse.

Quick Start

After finishing a session, instruct the AI to identify a non-obvious insight and save it to MEMORY.md.

Frequently Asked Questions about learn

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

FAQPage Schema
How do I capture non-obvious learnings into a memory store after a coding session?

To capture learnings into a memory store, instruct the AI to identify non-obvious session insights, verify their novelty against existing records, formulate actionable patterns, and append them to MEMORY.md for future reference.

What is the best way to avoid saving duplicate insights into knowledge management files?

The best way to avoid duplicate insights in knowledge management is to compare newly identified session learnings against existing MEMORY.md entries and current documentation before formulating and saving the pattern.

When should I persist debugging quirks and patterns into memory for future reference?

You should persist debugging quirks and patterns into memory after finishing a coding, debugging, or problem-solving session to ensure non-obvious takeaways are captured for future reference and continuous improvement.

How does identifying non-obvious session insights work with a memory store?

Identifying non-obvious session insights works by applying disciplined prompts to extract takeaways from a session, verifying their novelty against the memory store, and formatting them as actionable patterns before saving them.

Do I need an existing MEMORY.md file to save retrospective patterns?

You need an existing memory store like MEMORY.md to save retrospective patterns, as the process requires appending validated insights to appropriate sections within the file for long-term recall and reuse.