Daily Note to Knowledge
Most daily notes become a diary — you wrote it, felt productive, never looked at it again. Daily Note to Knowledge does the Zettelkasten processing step almost nobody does: extracting the 10-20% that has lasting value and giving it a permanent home.
What this skill does
The daily note is where most knowledge systems begin and where most of them quietly stall. People capture because something felt important in the moment — a realisation in a meeting, a pattern they half-noticed, a line from a book — but capture without processing is just journalling. Zettelkasten works because it forces two transformations: translating an observation into a standalone idea, and connecting that idea to what you already know. Both transformations require thinking. The notes are the residue of that thinking, not a substitute for it.
The skill reads the whole day's note before extracting anything, because the day's context matters — what the user was doing, what was on their mind. Then it scans for the eight things that become permanent-note candidates: realisations, pattern observations, mental models, decision rationales, contradictions, investigable questions, connections, and operating-condition data ("I always feel drained after X"). Everything else stays in the daily log where it belongs. Logistics aren't insights, and pretending they are bloats the vault.
Three filters then run on every candidate. The 6-month test — will this be useful or interesting in six months, stripped of today's context? "Follow up with Sarah" fails; "design reviews work better when aesthetic and functional feedback are separated" passes. The atomic test — can this be expressed as a single, specific claim? If it needs three paragraphs and five caveats, it's either not ready or it's actually three notes. The novelty test — is this genuinely new, or is the user rediscovering something they already noted? Rediscoveries get flagged as additions to the existing note, not duplicates.
Each surviving idea becomes a permanent note written in the user's voice (not cleaned up into AI prose), with a one-sentence "why this matters", two-to-five wikilinks each carrying a specific rationale ("connects to X because the mechanism is the same"), and an Open Thread pointing forward. When a day is purely operational, the skill says so — "no permanent knowledge to extract, that's normal." Not every day produces lasting insight. A productive day and a knowledge-producing day are different things, and treating them as the same is what kills the practice.
When this triggers
- ·You've been capturing in a daily note for weeks and none of it has been processed
- ·You want the actual permanent notes pulled out, not another summary
- ·You're trying to learn Zettelkasten and need an example of what 'processing' actually looks like
- ·You've got a batch of daily notes and want to see themes that span multiple days
- ·You suspect most of what you wrote was operational, and want an honest filter pass
Example
Trigger
User pastes a week of daily notes — meetings, errands, half-formed ideas, reading captures.
Output
Triage: 11 extraction candidates, 3 passed filters, 8 stay in the daily log. PERMANENT NOTE 1 — "Design reviews work better when aesthetic and functional feedback are separated." Realisation from Tuesday's review of the dashboard mock-up. The reason mixed feedback collapses: stakeholders argue about colour while the layout problem goes unaddressed. Why this matters: explains why design reviews feel chaotic even when participants are senior. Related: · [[Cognitive Load]] — same mechanism, different domain · [[Code Review Best Practices]] — the structural-vs-style split is the engineering version Open thread: does separation work for clients, or only for internal teams? PERMANENT NOTE 2 — [...] PERMANENT NOTE 3 — [...] Still cooking: 2 half-formed thoughts that need more data before they become claims.
Get this skill + 7 more
Get the full Second Brain pillar (8 skills) or the complete library.
Get the full stack — $299What you get
- 135-line SKILL.md, ready to drop into ~/.claude/skills/
- Tested through 3 Karpathy-loop iterations (versions v1.0.0 → v1.3.0)
- Triggers automatically when relevant — no command to remember
- Lifetime updates as the skill is refined further
More from Second Brain
When someone gives the user a book, article, or any long-form content, finds the 5-10 ideas worth remembering permanently — not a chapter-by-chapter summary
Takes content that exists in temporal, linear formats — YouTube videos, podcasts, lectures, interviews, webinars — and extract the permanent knowledge hiding inside them
Looks at someone's vault, note collection, or knowledge base and find what's *not* there — the orphan notes with no connections, the clusters that should link but don't, the topics that are…
Designs vault structures that people actually maintain — not theoretical systems that collapse under the weight of their own complexity
Find what's happening *between* sources — the agreements, contradictions, gaps, and emergent patterns that no single source reveals on its own
When someone shares a URL or web content, doesn't just copy it into markdown — it transforms it into a structured note that actually belongs in a knowledge system
Browse the full library
297 skills across 31 categories. One purchase, lifetime updates.
See all bundles