Fast note-taking assistant for quick journaling with automatic entity linking. Optimized for speed and frictionless daily-note capture. Use when the user wants to add quick notes, tasks, or entries to their daily note.
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-second-brain:journalThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fast, frictionless note-taking for daily journaling. Optimized for speed with automatic entity linking and smart formatting.
Fast, frictionless note-taking for daily journaling. Optimized for speed with automatic entity linking and smart formatting.
/journal [note content]
Examples:
/journal fixed upload bug in payment flow
/journal need to update React components for the new API
/journal learned about DNS configuration today
Identify entry type from context:
[x] (completed work)[ ] (todo)📝📝💭🍱 (also cross-post if a diet/fitness project exists — see §5)Priority search order:
01_Project/*.md02_Area/**/*.md03_Resource/**/*.mdAuto-link rules:
Never ask for confirmation. Speed is the priority.
Task completions:
[x] [Task description] - [[Auto-linked Entity]]
New tasks:
[ ] [Task description] - [[Auto-linked Entity]]
Problems/Notes:
📝 [Description] - [[Auto-linked Entity]]
Ideas:
💭 [Idea] - [[Auto-linked Entity]]
Location: Periodic_notes/YYYY/<MonthName>/YYYY-MM-DD.md (or wherever the vault keeps daily notes — match the vault's structure)
Section placement:
### Work: section### Life: section### Notes: sectionMatch the existing daily-note style. Preserve existing content. If no daily note exists, create one with a basic structure.
If the user maintains a topical tracking project (e.g. 01_Project/diet-project.md, 01_Project/fitness-tracker.md), cross-post relevant entries to it:
Detect the relevant project by matching keywords in the entry against active project filenames. Skip if no matching project exists.
Only if an unlinked entity is:
Then ask once:
"Create note for X?" Yes/No/Skip
Skip for: generic terms (bug, fix, DNS, authentication), common words, minor concepts already covered by existing notes.
User: "/journal fixed upload bug in payment flow"
Process:
1. Parse → Task completion [x]
2. Search → Found: "Payment Flow.md"
3. Auto-link → [[Payment Flow]]
4. Add → [x] Fixed upload bug in payment flow - [[Payment Flow]]
User: "/journal need to update React components for the new API"
Process:
1. Parse → New task [ ]
2. Search → Found: "React.md" and "API.md"
3. Add → [ ] Update React components for the new API - [[React]] [[API]]
User: "/journal learned about DNS configuration today"
Process:
1. Parse → Learning 📝
2. Search → no matches; "DNS" is generic → skip linking
3. Add → 📝 Learned about DNS configuration today
✅ Speed first — auto-link immediately, no confirmation ✅ Simple is better — don't over-analyze entities ✅ One question max — only ask when creating an important new entity note ✅ Skip generic terms — don't link common words ✅ Match existing daily-note style ✅ Frictionless — the goal is fast, uninterrupted journaling
The goal: make journaling so fast it becomes a frictionless habit.
create-note — for creating new entity notes (journal calls this when needed)weekly-review — uses journal entries for the weekly recapmonthly-review — uses journal entries for monthly analysisGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub thongntit/prompts --plugin obsidian-second-brain