Daily Review

Daily Review — Knowledge Compilation

Process 00 - Inbox/ notes: detect raw clips, compile into atomic notes, split multi-topic entries, classify, and move to the correct vault location.

> Configure your vault path in setup.sh or set the VAULT_PATH environment variable.

Core principle: one topic or idea = one note.

Constants

• Vault: $VAULT_PATH
• Today: use date +%Y-%m-%d to determine

Process

Step 1 — Scan Inbox

Use Bash ls to list all .md files in 00 - Inbox/.

• Skip _index.md
• If the inbox is empty, inform the user and stop
• Display the note list with filenames and a first-line content summary

Step 2 — Build Vault Context

Before classifying, understand the existing vault structure. The results of this step feed into all subsequent classification, wikilink, and move steps.

1. ls to scan 10 - Projects/, 20 - Areas/, 30 - Notes/ subfolders and filenames
2. For each project subfolder, read the Overview or main file (if one exists) to understand project scope
3. Retain this structure in memory — do not re-scan later

Step 3 — Read Inbox Notes

Use the Read tool to read the full content (frontmatter + body) of each inbox note.

**Read order: short notes first (body 80%` → move automatically, log in report

• `= 3; word count > 300 with structure (>= 3 sections) |

| medium | Has structure (>= 2 sections); word count 100-300; has frontmatter with tags >= 2 | | low | Pure clipboard paste / no structure / fewer than 100 words / missing frontmatter fields |

Execution: Use the Edit tool to add quality: high/medium/low in frontmatter (after status:).

Notes:

• Notes going to 99 - Archive/ do not need quality scoring
• Do not overwrite an existing quality field

Step 7 — Execute Moves (Automatic)

Move all notes with confidence >80%.

Standard move pattern:

1. Confirm the target folder exists (create with mkdir -p if not)
2. Duplicate filename guard: check for existing files with the same name
3. Use the Edit tool to update the first frontmatter tag (see table below)
4. Use Bash mv to move

| Destination | First tag | Status | Additional action | |-------------|-----------|--------|-------------------| | 10 - Projects/{name}/ | projects | unchanged | — | | 20 - Areas/{name}/ | areas | unchanged | — | | 30 - Notes/ | notes | unchanged | Rewrite title as an assertion statement | | 99 - Archive/Sessions/ | archive | archived | — |

Move command:

mv "$VAULT_PATH/source/filename.md" "$VAULT_PATH/destination/new-filename.md"

Step 8 — Confirmation List

If any notes have confidence Auto-generated, last updated: YYYY-MM-DD

| Note | Date | Quality | Summary | |------|------|---------|---------| | [[Note Name]] | 2026-03-26 | high | One-sentence summary | | [[Note Name]] | 2026-03-25 | medium | One-sentence summary |

Total: N notes

**Notes:**
- Only update folders that received notes — do not refresh the entire vault
- Subfolders (e.g., `Projects/MyApp/`) have their own `_index.md`
- `99 - Archive/` does not need a MOC
- `40 - Daily/` does not need a MOC
- Summaries should be distilled from content, **not copied from the frontmatter title**

### Step 9 — Generate Daily Report

Write to `40 - Daily/YYYY-MM-DD Daily Review.md`. If the file already exists, use the Edit tool to append.

```markdown
---
title: "YYYY-MM-DD Daily Review"
date: "YYYY-MM-DD"
type: daily
status: active
tags: [daily, review]
---

# YYYY-MM-DD Daily Review

## Inbox Processing
Processed N notes

| Note | Destination | Remarks |
|------|-------------|---------|
| [[Note Name]] | Target folder | auto/confirmed |

## Raw Clip Compilation
(If none: "No raw clips processed")

| Original Clip | Compiled Notes |
|---------------|----------------|
| [[Clip Name]] | [[Atomic Note A]], [[Atomic Note B]] |

## Split Notes
(If none: "No notes needed splitting")

| Original | Split Into |
|----------|-----------|
| [[Original Name]] | [[Child A]], [[Child B]] |

## Pending Confirmations
(If none: "All processed automatically")

## New Wikilinks
- [[Note A]] linked to → [[Note B]]

## Orphan Note Reminder
The following notes have no wikilinks — consider adding connections:
- [[Note Name]]

Guidelines

1. Splitting is mandatory — Every daily review MUST check each note for splitting (Step 4). Notes with + in the title connecting multiple topics MUST be split. Never skip splitting and move directly to Archive. One topic = one note is the core principle.
2. Do not rewrite note content — Only modify frontmatter (title, tags, status) and add wikilinks. When splitting, extract original text without summarizing.
3. Move with mv — Do not copy + delete.
4. Assertion-style titles — Only for notes going to 30 - Notes/ (e.g., "Git Hooks" becomes "Git hooks can automate pre-commit checks").
5. Preserve frontmatter — Never delete existing fields when moving.
6. Create missing folders — Use mkdir -p.
7. Duplicate filename guard — Check before writing or moving; append (2) if collision.
8. Idempotent — Running multiple times on the same day causes no harm: daily report is appended (not overwritten), already-moved notes do not reappear in Inbox.

Related Skills

• [[session-to-obsidian]] — Creates the inbox notes this skill processes
• [[recall]] — Search for notes after they have been filed
• [[vault-lint]] — Health check complements daily review
• [[weekly-review]] — Aggregates daily review outcomes
• [[vault-lint]] — Vault health check after filing completes

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: kalawcreator919
• Source: kalawcreator919/claude-obsidian
• License: MIT

Install and usage instructions live in the source repository linked above.