Build Your AI Second Brain: Obsidian + Claude + Steph Ango's Official Skills

The Problem Every Note-Taker Hits — and Why Obsidian Fixes It

Most people who take notes seriously hit the same wall: the knowledge goes in but rarely comes back out. You wrote something important six months ago. You will never find it. The folder system breaks down. The tags get inconsistent. The connections between ideas — the whole point of a second brain — never actually get made, because making them manually takes more effort than the system saves. Obsidian's Graph View makes the problem visible: isolated nodes with no connections. The insight that changed this in 2026 is that you were never supposed to maintain those connections yourself. Claude Code, pointed at a vault of plain Markdown files, can read every note you have ever written, find the relationships you missed, and build the links for you. The vault becomes something you actually use rather than something you maintain.

Steph Ango's obsidian-skills: Why It Changes Everything

In January 2026, Steph Ango — CEO of Obsidian, known as kepano on GitHub — published an official repository called obsidian-skills. It reached 13,900+ stars within weeks. This is not a community plugin or a third-party integration. It is the product leadership officially signaling that AI agents are now first-class collaborators in Obsidian. The repository ships five skills that teach Claude Code the correct syntax for every Obsidian file type. Without them, Claude guesses at the format and often gets it wrong: broken wikilinks, invalid Bases JSON, Canvas files that won't open. With them, Claude writes notes exactly as a human Obsidian expert would — proper frontmatter, correct wikilink syntax, valid database queries, and spatial canvas layouts. Installation takes one command. The difference in output quality is immediate.

How to Structure Your Vault So Claude Can Actually Use It

The most common failure mode is creating hundreds of notes with no consistent structure, then wondering why Claude's answers are generic. Two things make the difference. First, the CLAUDE.md file at your vault root — Claude Code reads this automatically at the start of every session. Put your folder structure, your tagging schema, your note templates, and the rules you want Claude to follow. This is your contract with the AI. Second, YAML frontmatter at the top of every note. Without it, Claude treats all files as equal. With it, you can ask for 'all notes with status active and tag project-alpha' and get exactly that. The minimum frontmatter is four fields: date, tags, status, and type. That is enough to turn a folder of text files into a queryable knowledge database.

The Prompts That Actually Build the Second Brain

The key mental shift is asking for outcomes, not instructions. Instead of 'read this note and find related notes,' say 'scan everything I added this week, find 3-5 existing notes each new note relates to, add wikilinks in both directions, and tell me why each connection matters.' Claude reads across your entire vault, identifies relationships you never noticed, and builds a mesh of links that compounds every time you add something new. The 50th note you add is dramatically more connected than the first — because Claude cross-references it against everything that already exists. Other high-value prompts: building topic wiki pages that synthesize everything you know about a subject, processing your inbox into the right PARA folder with correct metadata, and running weekly synthesis that surfaces decisions made, open questions, and new connections across your projects.

Prompt

# ─── STEP 1: INSTALL OBSIDIAN-SKILLS (The Most Important Step) ───
# Open your terminal inside your Obsidian vault folder, then run:
git clone https://github.com/kepano/obsidian-skills .claude/skills

# Or via Claude Code plugin marketplace:
/plugin marketplace add kepano/obsidian-skills
/plugin install obsidian@obsidian-skills

# Before working with a specific file type, load the relevant skill:
/obsidian-markdown    # For .md notes — correct wikilinks & frontmatter
/obsidian-bases       # For .base database files
/json-canvas          # For .canvas spatial maps
/defuddle             # Strip web pages to clean markdown before saving

# ─── STEP 2: CREATE YOUR CLAUDE.md AT VAULT ROOT ───
# This is the most important file — Claude reads it first in every session.
# Template:

## Vault Overview
This is a personal knowledge base organized using the PARA method.
Owner: [Your name] | Focus: [Your main topics]

## Folder Structure
- 0. Inbox/     → Unsorted incoming notes
- 1. Projects/  → Active work with deadlines
- 2. Areas/     → Ongoing responsibilities
- 3. Resources/ → Reference and research
- 4. Archive/   → Completed or inactive items

## Note Schema (always use this frontmatter):
---
date: YYYY-MM-DD
tags: [topic, subtopic]
status: active | draft | archived
project: project-name
type: note | meeting | research | idea | decision
---

## Rules for Claude:
- Always use [[wikilinks]] for internal references
- Never modify files in 4. Archive/
- When adding a new note, check for existing related notes and link them
- Use /obsidian-markdown skill before writing any .md file

# ─── STEP 3: PROMPTS THAT ACTUALLY BUILD YOUR SECOND BRAIN ───

# Connect everything — run this after adding new notes:
"Scan all notes in 3. Resources/ added this week.
For each new note, find 3-5 existing notes it relates to and add
[[wikilinks]] to both files. Write a one-line reason for each link."

# Build a topic wiki page automatically:
"Read all notes tagged [your topic]. Create a new wiki page in
3. Resources/[topic].md that summarizes the key ideas, lists
all related notes as wikilinks, and highlights contradictions or gaps."

# Process your inbox:
"Go through every file in 0. Inbox/. For each one:
1. Determine the correct PARA category
2. Move it to the right folder
3. Add proper frontmatter (date, tags, type, status)
4. Link it to 2-3 related existing notes
Report what you moved and why."

# Weekly synthesis:
"Summarize all notes modified or created this week.
Group by project. List decisions made, open questions,
and new connections found between topics.
Save as _Weekly/[YYYY-WXX].md"

# Ask your own knowledge base:
"What have I decided about [topic]? Check my decision notes
and quote the relevant parts with file references."

# ─── PRO TIPS ───
# /defuddle before saving any web article — cuts token cost by ~60%
# YAML frontmatter is essential — without it Claude treats all files the same
# The 50th note you add is more useful than the first — connections compound
# Claude Code does NOT need MCP for this — just open terminal in vault folder