learn

Record insights to team memory at ~/.claude/team/memory/ with categorized entries.

Updated Feb 12, 2026

Search Tags:#memory #team #knowledge-base #memory-management #learn #entry

Ready to run

npx skills add https://github.com/obenland/dotfiles --skill learn-obenland

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/obenland/dotfiles/tree/main/claude/.claude/skills/learn
Command: npx skills add https://github.com/obenland/dotfiles --skill learn-obenland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Record insights to the team's persistent memory at ~/.claude/team/memory/.

Core Features & Use Cases

Capture learnings from code reviews, debugging sessions, and architectural decisions to build a centralized, consultable knowledge base.
Categorize entries into patterns, debugging insights, decisions, and review findings for quick retrieval.
Enforce concise entries with a 100-line cap and deduplication to avoid memory bloat.

Quick Start

Use the /learn command to record a learning into the team memory at ~/.claude/team/memory/.

Frequently Asked Questions about learn

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

FAQPage Schema

How do I record team learnings from debugging sessions into a persistent knowledge base?▼

You can record team learnings by using the /learn command to write entries to persistent memory at ~/.claude/team/memory/. This builds a centralized, consultable knowledge base for your team.

Can I categorize architectural decisions and code review findings in team memory?▼

Yes, you can categorize architectural decisions and code review findings in team memory. Entries are structured into patterns, debugging insights, decisions, and review findings for quick retrieval.

What is the best way to prevent memory bloat in a team knowledge base?▼

The best way to prevent memory bloat in a team knowledge base is to enforce concise entries with a 100-line cap and apply deduplication. This avoids bloated records while maintaining a consultable knowledge base.

Does the team memory skill require any external dependencies to capture insights?▼

No, the team memory skill requires no external dependencies to capture insights. It records learnings directly to the local persistent memory directory at ~/.claude/team/memory/ without needing additional components.

How do I save code review findings to persistent memory for future reference?▼

You can save code review findings to persistent memory by using the /learn command. It records your findings into ~/.claude/team/memory/, categorizing them as review findings for quick retrieval.