obsidian-brain
SolidBuild a local Obsidian vault that acts as the company and founder second brain, the knowledge layer every other skill reads before acting and writes back to. Input: your raw material (PDFs, decks, transcripts, email, WhatsApp exports, loose notes). Output: a structured, linked vault (domain hubs, maps of content, atomic notes) with read-first/write-back protocols, no orphans, and a single source of truth for numbers. Use when the user mentions Obsidian, a vault, a knowledge base, a second brain, importing documents or transcripts, or wants to give Claude context once instead of repeating it every conversation.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- Thibaultbm
- Repository
- Thibaultbm/claude-seo-geo
- Created
- 2 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
obsidian-second-brain
Operate any Obsidian vault as a living, self-rewriting second brain (an evolution of Karpathy's LLM Wiki pattern: sources rewrite existing pages, contradictions reconcile automatically, scheduled agents maintain the vault while you sleep). Use this skill whenever the user asks Claude to read, write, update, search, or manage their Obsidian vault - including saving notes from conversation, creating daily entries, updating kanban boards, logging dev work, managing people notes, capturing decisions, tracking deals, or maintaining any vault structure. Also triggers when the user wants to bootstrap a new vault from scratch, run a vault health check, or drop a _CLAUDE.md into their vault so all Claude surfaces share the same operating rules. Includes a research toolkit (7 commands: /x-read, /x-pulse, /research, /research-deep, /notebooklm, /youtube, /podcast) for AI-powered research via Grok, Perplexity, NotebookLM, YouTube, and podcast feeds - findings save to the vault automatically following the AI-first vault r
second-brain
Set up and operate a file-based second brain — a knowledge vault that every Claude Code session reads on start and writes back to before it ends, so context compounds across sessions instead of evaporating. Use "second-brain setup" to bootstrap a new vault (folder structure, brain CLAUDE.md, note templates, optional session-log hook), and follow the OPERATE rules in every session once a vault exists. Built for Obsidian-flavored markdown but works with any plain-markdown folder.
second-reader
Build and run a source-verified Markdown knowledge vault (opens as an Obsidian vault). Ingests books, PDFs, transcripts, and articles into atomic, cross-linked, cited notes, then gates every note and every answer behind an independent verification pass that re-reads the source cold and loops until a round finds nothing. Includes a closed learning loop, the vault designs a curriculum from its own gap analysis, runs vault-blind tutoring sessions (spoken or text), grades them, and feeds results back into the vault. Use when the user wants to build a knowledge base from sources, ingest material into a vault, query accumulated knowledge with cited answers, audit vault quality, find knowledge gaps, or study and learn a subject from their vault (the category some call a second brain). Not for one-off summarization, ordinary Markdown editing, generic note formatting, or casual capture. This skill is expensive by design and gates everything it writes.