What does this skill do?

The Skill Learning Log transforms specific experiences—failures, methodologies, discoveries—into reusable and searchable patterns, avoiding the common mistake of simply recounting events without extracting a transferable lesson. It applies Bole’s Principle to merge duplicates, guides root cause analysis with 3–5 “whys,” and generates entries using the formula “the next time I see [sign], I will do [action].” It works with any note-taking system: Markdown, Notion, Obsidian, or plain text.

Report a problem
After encountering a bug or a situation where you think, "This was harder than expected," identify the root cause by asking "why" 3–5 times and turn it into a transferable pattern.
Completing a Complex Task
After a multi-file change, a new feature, or an architectural change, document the non-obvious decision and the reasoning behind it.
Review of What We've Learned
Review what you've learned over a period of time by consulting searchable, interconnected entries.
Merge duplicates
Apply Bole's Principle: the same root cause with a different symptom is merged into the existing entry rather than duplicated.

Usage examples

🐛 After a major bug
I've been debugging for two hours to figure out why the session token wasn't persisting in production. Help me write a blog post explaining the root cause and the general pattern.
🏗️ After a complex task
I just finished a multi-file refactoring of the data pipeline. I'm documenting what I learned as a methodology post on my blog.
🧩 Merge entries
I think this issue with the outdated index and the post about overlooked valuations have the same root cause. Apply Bole's Principle and merge them.
🔍 Periodic review
Take a look at my blog posts from the last two months and tell me which patterns have appeared most often and which ones I should keep an eye on.

Features

Root Cause Analysis An iterative guide using 3–5 “whys” to identify the underlying mechanism, always distinguishing it from the symptom.
Bole's Principle Before creating a new entry, check for duplicates by root cause and merge those that share the same mechanism.
Entry Template Fixed 4–8-sentence structure: context, root cause, transferable pattern with a recognizable signal, and related inputs.
Four types of entry Judgment, Methodology, Pattern Discovery, and Capacity Shift—all using the same template but with different emphases.
Quality Checklist Check before closing each entry: title that identifies the pattern, the phrase "next time I'll...," a specific cue, and no duplicates.

Frequently asked questions

The criteria are: Did the task involve debugging, redoing work, rolling back, or a non-obvious decision? If not (typos, one-line adjustments), skip it.
No. It works with any note-taking system: Markdown in a `bitacora/` directory, Notion, Obsidian, or plain text. The important thing is to use a consistent naming convention.
A two-hour bug teaches you more than three features that worked on the first try: a failure holds more lessons than a success.
Before writing a new entry, ask yourself, "Is this essentially the same as what I've already recorded?" Entries with the same root cause but different symptoms are merged; a new root cause warrants a new entry.
Learning Log — Track patterns, not a diary, with Claude AI

¿Prefieres escuchar el contenido? Genera la narración de audio con un clic.