Record insights to team memory at ~/.claude/team/memory/ with categorized entries.
npx skills add https://github.com/obenland/dotfiles --skill learn-obenland
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
Record insights to the team's persistent memory at ~/.claude/team/memory/.
Use the /learn command to record a learning into the team memory at ~/.claude/team/memory/.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
Leap0920Track characters, relationships, scenes, and themes across writing sessions.
drt0927Aggregate team learnings into a searchable append-only log with export.
yebotCategorize session learnings into taxonomy types and route them to memory files.
PiaoxuemoliAnswer repository questions by searching wiki, memory, and git log entries.
