REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
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.
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/eugeniughelbur-obsidian-second-brain)在同一工作中把 AI 连到服务的 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同类工作,排序与 Skill 列表相同
| 本项 obsidian-second-brain | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | eugeniughelbur | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub 星标 | 5,370 | 467,235 | 234,125 | 149,873 | 144,332 |
| 最近代码更新 | 2026年11月17日 | 2026年11月18日 | 2026年4月20日 | 2026年11月18日 | 2026年11月18日 |
| 许可证 | MIT | MIT | – | Apache-2.0 | MIT |
eugeniughelbur 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
Claude CodeCodexCursorGemini CLIOpenCode
依据开发者 README 和 repo 中的文件夹
GitHub account eugeniughelbur (person), 1 years old
★ 5,370 stars · code last changed 2026年11月17日
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
Could not check every script (some are too large); read them first
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
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
Uploading to claude.ai would fail: the description is over 200 characters (1351). Use "Let the AI install it" instead
复制这句话,粘贴到 Claude Code 的对话中
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
重新打开 Claude Code,输入 /obsidian-second-brain,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brain摘自开发者 README,会下载并运行开发者的代码
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 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-brainChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
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
把 obsidian-second-brain 文件夹放到 ~/.agents/skills/obsidian-second-brain
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 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-brainChecked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
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 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 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复制这句话,粘贴到 Cursor 的对话中
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
在 Cursor 的 Agent 聊天中输入 / 并选择 obsidian-second-brain
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 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-brain适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · 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 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月16日
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
显示前 8,000 个字符 · 在 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**提问、分享技巧或报告无法使用。按“有帮助”数量排序。