obsidian-second-brain

Review today's daily note, extract what matters, file it properly, and set up tomorrow. This is a 5-minute ritual, not a lengthy report.

Takes two separate topics or domains and uses the vault's graph to find non-obvious connections between them.

Run an interactive daily startup session to begin the day with clarity and focus.

Scan recent daily notes, surface ideas worth promoting to standalone permanent notes, and help you decide what to graduate into your PARA system.

Find ideas implied by the vault's contents but never explicitly articulated. These are conclusions the vault's evidence points toward, patterns its structure reveals, but that have never been written down.

Generate writing from vault thinking. Takes a topic (from argument or today's daily note), mines the vault for raw material, then produces drafts at three levels.

Run a comprehensive vault health check to identify and report issues. This is **read-only** - no changes will be made automatically.

Go beyond what the vault contains to figure out how to make more money. The vault is the starting point, not the ceiling. Surface opportunities the user cannot see from inside their own perspective.

EXECUTE THIS WORKFLOW NOW. Do not describe it - actually run the commands and process notes.

Facilitate quarterly, monthly, or weekly OKR reviews with progress tracking and goal alignment.

Compare stated intentions against actual behavior over the past 30 days. Surface gaps between what you say matters and where time and energy actually go. Find what's being avoided.

Surface patterns, insights, and candidate topics from the week's daily notes. Output everything to terminal. Do NOT create any files.

Link health specialist that finds broken wiki links, identifies orphaned notes, and suggests meaningful connections between related notes to maintain a healthy knowledge graph.

Goal tracking specialist that monitors OKR progress across the vault, identifies goal mentions in notes, generates progress dashboards, and ensures alignment between quarterly, monthly, and weekly goals.

PARA categorization specialist that analyzes note content and suggests optimal placement in Projects, Areas, Resources, or Archives based on actionability and content analysis.

Tag consistency specialist that ensures tags follow the vault's PARA-aligned Tag Taxonomy, suggests appropriate cross-cutting tags, and maintains a clean, discoverable tagging system.

Organizes Obsidian vaults using PARA methodology, progressive summarization, and PKM workflows including inbox processing, Maps of Content, and review cadences. Make sure to use this skill whenever the user asks about organizing notes, second brain, inbox processing, MOCs, review cadences, PARA method, or knowledge management — even if they just say "how should I organize my notes?"

Performs all Obsidian vault operations — reading notes, creating files, appending content, searching, and listing files — using CLI-first approach with MCP fallback. Make sure to use this skill whenever the user mentions obsidian, vault, notes, daily note, or any vault file operation. If the user mentions Obsidian in any context, use this skill.

Selects and applies the right Obsidian note template based on note type — project briefs, meeting notes, daily notes, learning notes, book reviews. Make sure to use this skill whenever the user wants to create a structured note, asks which template to use, or starts a new project note, meeting note, weekly review, or learning session.

Provides the user's specific Obsidian vault structure — folder organization (PARA), tagging taxonomy, templates, and file conventions. Contains paths and patterns Claude cannot know without this skill. Make sure to use this skill whenever placing notes in the vault, choosing tags, or needing vault-specific folder structure and paths.

1 hook across 1 event