learn

Log, search, prune, and export project learnings stored in a JSONL file.

Updated May 22, 2026
One-click install
npx skills add https://github.com/kitfunso/claude-config --skill learn-kitfunso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/kitfunso/claude-config/tree/main/skills/learn
Command: npx skills add https://github.com/kitfunso/claude-config --skill learn-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose hard-won lessons between sessions: the same bug gets rediscovered, stale advice lingers, and contradictory guidance goes unnoticed. This Skill manages a persistent project learnings store so insights are captured, reviewed, and kept trustworthy over time. ## Core Features & Use Cases - Log learnings: Record durable patterns, pitfalls, and preferences with confidence scores and file references, while declining one-off transient events. - Review and search: Show what the project has learned and search entries when asked "what have we learned" or "didn't we fix this before?" - Prune and export: Flag stale entries pointing at deleted files, surface contradicting entries, and export the learnings set. - Use Case: Ask "what have we learned on this project?" and get a report that flags a stale entry referencing a removed module and two contradictory cache-TTL preferences before you trust the file. ## Quick Start Ask the assistant to show what we have learned on this project and flag anything stale or contradicting in the learnings file.

Frequently Asked Questions about learn

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

FAQPage Schema
How do I log a learning from a coding session?▼

Ask to log a learning and describe the durable pattern or pitfall. The Skill records it as a JSONL entry with a type, key, insight, confidence score, and referenced files, but declines one-off transient events like a dropped network connection.

How do I check what a project has learned so far?▼

Ask "what have we learned" or "show learnings" to review the learnings.jsonl file. The Skill lists entries and, when there are more than a handful, surfaces the most relevant ones via search.

Can it detect stale or contradicting learnings?▼

Yes. It flags entries that reference files no longer present in the repository as stale, and surfaces entries sharing a key with conflicting insights, such as two contradictory cache-TTL preferences.

What kinds of lessons should not be logged?▼

Do not log obvious facts or one-time transient errors, such as a deploy failing once because WiFi dropped. The Skill declines these and explains that only durable, reusable patterns are worth persisting.

Does managing learnings modify project source code?▼

No. The Skill only reads and writes the learnings store; it never edits source files. Verification of stale entries is done by checking file existence with read-only operations.