Evaluate Knowledge

Overview

Transforms passive knowledge into actionable insights by evaluating notes against your interest profile, generating personalized suggestions for work and personal life, and organizing clippings into your knowledge base.

When to Use

• •Reviewing a note and want personalized takeaways
• •Processing new additions to your knowledge base
• •Finding patterns across a folder of notes
• •Refreshing stale evaluations after note updates
• •Processing Clippings inbox (auto-organizes, tags, and moves to knowledge base)

Quick Reference

Core Pattern

1. Load {{ profile.interest_profile }} from vault root
2. For each note in scope:
   - Skip if evaluated >= modified (unless --force)
   - Skip if < 100 words
   - If in {{ folders.clippings }}/: organize first (move + tag)
   - Generate evaluation (adaptive sizing)
   - Append to note + update frontmatter
   - Add entry to daily note (Daily Dose of Know-How)
3. Update evaluation-log.md (add/update entry for each evaluated note)

Implementation

Input Parsing

Important: Folder processing ALWAYS includes all subfolders. For example, {{ folders.clippings }}/ processes both {{ folders.clippings }}/*.md AND {{ folders.youtube }}/*.md.

Interest Profile

Read {{ profile.interest_profile }} from vault root. Extract:

• •Work section: Role, priorities, professional interests
• •Private section: Personal interests, life context

Evaluation Output

Append to each note:

---

## Evaluation

*Evaluated: YYYY-MM-DD*

### For Work
- [Suggestions connecting to work priorities]

### For Personal
- [Suggestions for personal life application]

Update frontmatter: evaluated: YYYY-MM-DD

Adaptive Sizing

Evaluation Log (Always Updated)

Update {{ folders.knowledge_base }}/evaluation-log.md after every evaluation (single or batch):

If log doesn't exist: Create it with header and first entry.

If log exists:

• •Add new entry to table (or update if note already listed)
• •Re-analyze patterns section based on all entries

# Knowledge Evaluation Log

Last updated: YYYY-MM-DD
Total evaluated: N notes

## Aggregated Patterns

### [Theme Name]
- [[Note]] - Key insight

## All Evaluations

| Note | Evaluated | Category | Key Insight |
|------|-----------|----------|-------------|
| [[Note path]] | 2026-01-18 | Leadership | One-line insight |

Group notes by detected themes (2+ notes sharing a pattern).

Daily Dose of Know-How

After evaluating each note, append a summary to today's daily note.

Daily note path: {{ folders.daily_notes }}/YYYY-MM-DD.md (today's date)

If daily note doesn't exist:

1. •Read template from {{ folders.templates }}/Daily Note.md
2. •Create daily note with template content
3. •Replace any date placeholders (e.g., {{date}}) with today's date

If section doesn't exist: Add ## Daily Dose of Know-How section at the end of the note.

Entry format (append under the section):

- [[Note Title]] → *{{ folders.knowledge_base }}/Product/AI & ML/*
  - **Takeaway:** One-line key insight from the evaluation
  - **Action:** Specific suggestion for applying this knowledge

Field definitions:

Example daily note section:

## Daily Dose of Know-How

- [[How to give feedback]] → *{{ folders.knowledge_base }}/Leadership/*
  - **Takeaway:** The SBI (Situation-Behavior-Impact) framework makes feedback specific and actionable
  - **Action:** Use SBI format in your next 1:1 when discussing the delayed project delivery

- [[AI Product Strategy 2024]] → *{{ folders.knowledge_base }}/Product/AI & ML/*
  - **Takeaway:** AI features should solve existing user problems, not showcase technology
  - **Action:** Review your team's AI roadmap for features that might be "tech-first" vs "problem-first"

Skip Conditions

• •evaluated >= modified (already current)
• •Word count < 100 (stubs)
• •Filename starts with _ (drafts)
• •Frontmatter has status: template

Clippings Inbox Processing

When note is in {{ folders.clippings }}/ or any subfolder:

1. •Analyze content → determine best-fit folder in {{ folders.knowledge_base }}/
2. •Add tags → max 5 relevant tags to frontmatter properties
3. •Move note → to target folder (delete from {{ folders.clippings }})
4. •Continue → with normal evaluation

Target folders: List existing subfolders in {{ folders.knowledge_base }}/ using Obsidian MCP and pick the best-fit folder for each note. If no good fit exists, create a new subfolder with a descriptive name.

Tag format: Frontmatter properties

tags:
  - leadership
  - feedback
  - management

Common Mistakes

Dependencies

• •Obsidian MCP - read/write notes
• •{{ profile.interest_profile }} - in vault root with Work/Private sections
• •Daily Notes folder - {{ folders.daily_notes }}/ with date-named files (YYYY-MM-DD.md)
• •Daily note template - {{ folders.templates }}/Daily Note.md (used when creating new daily notes)