What it does
Persistent memory for Claude Code, Codex and 6 other AI agents, stored as plain markdown in your Obsidian vault. New: Crew, one shared logbook so Claude Code, Codex, Cursor and Grok Bot know what each other did. 48 commands: semantic search, self-rewriting notes, key-less research, scheduled agents.
- Connects Instruction files the AI reads, with steps that call an outside service
- Account or key Some steps need a key for Perplexity, KEENABLE_API_KEY, OpenAI, OPENROUTER_API_KEY, XAI_API_KEY, Google Gemini (per the README)
- Category Coding
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/eugeniughelbur-obsidian-second-brain)Use together with
MCP servers that connect the AI to services for the same work
Fallow
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
Desktop Commander
MCP server for terminal commands, file operations, and process management
Similar Skills
Same kind of work, ordered like the Skills list
| This one obsidian-second-brain | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Maker | eugeniughelbur | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 5,370 | 467,235 | 234,125 | 149,873 | 144,332 |
| Last code change | Nov 17, 2026 | Nov 18, 2026 | Apr 20, 2026 | Nov 18, 2026 | Nov 18, 2026 |
| License | MIT | MIT | – | Apache-2.0 | MIT |
1 skills (instruction sets) by eugeniughelbur that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeCodexCursorGemini CLIOpenCode
From the maker’s README and the folders in the repo
Install
Is it safe?
- Who made it
GitHub account eugeniughelbur (person), 1 years old
- Use and upkeep
★ 5,370 stars · code last changed Nov 17, 2026
- Any scripts?
214 scripts that can run on a computer: adapters/claude-code/adapter.sh, adapters/codex-cli/adapter.sh, adapters/gemini-cli/adapter.sh, adapters/opencode/adapter.sh and 210 more
- Uses the internet?
Could not check every script (some are too large); read them first
- Changes machine-wide settings?
Installing the maker’s way adds hooks that run without you asking: run every time the AI edits a file · run every time a chat starts · run on the PostCompact event · Installed as a plugin (/plugin) it will run every time the AI edits a file in every project · Scripts that touch settings folders (~/.claude or settings.json): scripts/install-codex-wrappers.sh
Checked automatically from the repo files at commit 248fa50 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (1351). Use "Let the AI install it" instead
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /obsidian-second-brain or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
The maker’s recommended way
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brainCopied from the maker’s README; it downloads and runs the maker’s code
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/eugeniughelbur/obsidian-second-brain.git /tmp/popnx-skill-eugeniughelbur-obsidian-second-brain-248fa50 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-eugeniughelbur-obsidian-second-brain-248fa50/.' ~/.claude/skills/obsidian-second-brainRestart Claude Code, then type /obsidian-second-brain or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the obsidian-second-brain folder at ~/.agents/skills/obsidian-second-brain
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/eugeniughelbur/obsidian-second-brain.git /tmp/popnx-skill-eugeniughelbur-obsidian-second-brain-248fa50 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-eugeniughelbur-obsidian-second-brain-248fa50/.' ~/.agents/skills/obsidian-second-brain
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/eugeniughelbur/obsidian-second-brain.git /tmp/popnx-skill-eugeniughelbur-obsidian-second-brain-248fa50 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-eugeniughelbur-obsidian-second-brain-248fa50/.' ~/.agents/skills/obsidian-second-brainRestart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick obsidian-second-brain
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/eugeniughelbur/obsidian-second-brain.git /tmp/popnx-skill-eugeniughelbur-obsidian-second-brain-248fa50 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-eugeniughelbur-obsidian-second-brain-248fa50/.' ~/.cursor/skills/obsidian-second-brainIn Cursor’s Agent chat, type / and pick obsidian-second-brain
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 16, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: obsidian-second-brain
description: >
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.
Also runs Crew (/crew): one shared logbook so Claude Code, Codex, Cursor, and Grok Bot
know what each other did, in any plain folder or the vault.
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 rule. Use proactively whenever
the conversation produces information worth preserving (decisions, people met, projects
started, tasks completed, lessons learned, research findings).
---
# Obsidian Second Brain
> Claude operates your Obsidian vault as a self-rewriting knowledge base. An evolution of [Karpathy's LLM Wiki pattern](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f): sources rewrite existing pages instead of just appending, contradictions reconcile automatically, and scheduled agents maintain the vault while you sleep.
> Everything worth remembering gets saved. Every update propagates everywhere it belongs.
---
## Quick Start
### 0. Choose vault access method (in order of preference)
Try these methods in order. Use the first one available:
**Method 0 - SessionStart hook (if configured):**
If `hooks/load_vault_context.py` is wired as a SessionStart hook in `~/.claude/settings.json`, `_CLAUDE.md` is injected into context automatically at session start.
Skip step 1 only when the manual is actually in your context, not merely because the hook is configured. Claude Code caps hook context at 10,000 characters, so a larger manual cannot be injected; in that case the hook says so in as many words ("NOT loaded - read it") and you read the file yourself (#270). A vault whose `.claude/CLAUDE.md` holds `@../_CLAUDE.md` sidesteps the cap entirely - Claude Code imports that natively at any size.
To wire it: `bash scripts/setup.sh "/path/to/vault"`.
If another Obsidian plugin also holds a SessionStart hook, the injected context opens with a precedence note naming it (#300). Claude Code runs every SessionStart hook and adds each output here, so you may be holding two folder maps and two frontmatter schemas for one vault. The vault's own `_CLAUDE.md` governs every write. Where the other tooling disagrees, follow the manual and say so in your reply.
**Method A - Direct filesystem (default, always works):**
Use standard file tools (Read, Write, Edit, Glob) against the vault path. The vault is plain markdown, so every operation in this skill works this way with no setup. This is the normal path in Claude Code - the commands below use these tools directly.
**Method B - MCP server (optional, mainly for non-Claude-Code clients):**
This repo ships its own MCP server at `integrations/obsidian-mcp-server/` that exposes the vault as tools (`obsidian_search`, `obsidian_read_note`, `obsidian_save_note`, `obsidian_capture`, plus curator tools). It exists so other MCP clients - Hermes Agent, Claude Desktop, Cursor - can use the vault as a knowledge layer; in Claude Code itself, Method A is simpler and preferred. If those `obsidian_*` tools happen to be available in your client, you may use them instead of raw file tools. Setup lives in `integrations/obsidian-mcp-server/README.md` (it is `uv run --no-project --with 'mcp<2' python .../server.py` with `OBSIDIAN_VAULT_PATH` set, not an `npx` package). Since the bookkeeping change, every write through the server also validates the note, adds the index entry, appends the operation-log line, and runs `OBSIDIAN_POST_WRITE_CMD` when set - see `integrations/obsidian-mcp-server/README.md`, "Bookkeeping after writes".
### 1. First time in a vault → read `_CLAUDE.md`
Before doing anything in a vault, check if `_CLAUDE.md` exists at the vault root and read it:
```
Read <vault>/_CLAUDE.md
```
If it exists: follow its rules exactly - they override the defaults in this skill. Where `_CLAUDE.md` is silent, fall back to the defaults below.
If it doesn't exist: use the defaults in this skill, then offer to create one.
Skip this step only if `_CLAUDE.md` is actually in your context already - the SessionStart hook injects it, but not when the manual is over Claude Code's 10,000-character hook limit, and the hook says which case you are in. If you cannot quote a rule from it, you do not have it: read the file.
### 2. First time with a new user → run discovery
```
Glob <vault>/**/*.md
```
Scan the structure to understand: folder names, template locations, naming conventions, frontmatter patterns. Then read 2-3 existing notes to calibrate writing style before creating anything new.
### 3. Bootstrap a new vault
If the user has no vault yet, bootstrap it from the local copy of the skill. The skill is already installed if you are reading this file, so never pipe a remote install script into a shell on the user's behalf.
```bash
python scripts/bootstrap_vault.py --path ~/path/to/vault --name "Your Name"
# With a preset:
python scripts/bootstrap_vault.py --path ~/my-vault --name "Your Name" --preset executive
python scripts/bootstrap_vault.py --path ~/my-vault --name "Your Name" --preset builder
python scripts/bootstrap_vault.py --path ~/my-vault --name "Your Name" --preset creator
python scripts/bootstrap_vault.py --path ~/my-vault --name "Your Name" --preset researcher
# Wiki-style layout (wiki/daily/, wiki/entities/, ...) instead of the default Obsidian-style one:
python scripts/bootstrap_vault.py --path ~/my-vault --name "Your Name" --style wiki
# With assistant mode (maintaining vault for someone else):
python scripts/bootstrap_vault.py --path ~/my-vault --name "Your Name" --mode assistant --subject "Boss Name"
```
Then just point the skill at the new vault path (Method A above). If you use the optional bundled MCP server, set `OBSIDIAN_VAULT_PATH` to the new path and restart the client.
**Presets** customize the vault for different use cases:
- **`executive`** - Decisions, people, meetings, strategic planning. Kanban: OKRs, Quarterly, Weekly.
- **`builder`** - Projects, dev logs, architecture decisions, debugging. Kanban: Backlog, Sprint, Done.
- **`creator`** - Content calendar, ideas pipeline, audience notes, publishing. Kanban: Ideas, Drafts, Published.
- **`researcher`** - Sources, literature notes, hypotheses, methodology. Kanban: Reading, Processing, Synthesized.
Default (no preset) gives a general-purpose vault. All presets use wiki-style by default.
**Assistant mode** creates a `_CLAUDE.md` configured for operating a vault on behalf of someone else. See `references/claude-md-assistant-template.md`.
See `references/vault-schema.md` for full structural details.
---
## Core Operating Principles
### AI-first vault rule (applies to every note)
The vault is designed for **future agent** to read and reason over, not for human review. Every note Claude writes - across all 49 commands - must follow `references/ai-first-rules.md`:
1. **Self-contained context** - each note explains itself; don't rely on backlinks alone
2. **"For future agent" preamble** - 2-3 sentence summary so any compatible agent can decide relevance in 10 seconds
3. **Rich, consistent frontmatter**Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 5,370
- Maker
- eugeniughelbur
- License
- MIT
- Last code change
- Nov 17, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- agent-memory, agent-skills, ai-note-taking, ai-second-brain, claude, claude-code, claude-code-skill, claude-memory, claude-plugin, claude-skill, codex, karpathy-llm-wiki