create-command
CommandCreate a new obsidian-second-brain command via interview - zero markdown editing required
Load your identity, values, priorities, and current state in one shot - with progressive context levels to avoid burning tokens
> /plugin marketplace add eugeniughelbur/obsidian-second-brain> /plugin install obsidian-second-brain@obsidian-second-brain
description: Load your identity, values, priorities, and current state in one shot - with progressive context levels to avoid burning tokens category: vault triggers_en: ["load context", "what is going on", "where am I", "load my world"] triggers_de: ["Kontext laden", "was ist gerade los", "wo stehe ich", "meine Welt laden"] triggers_es: ["carga el contexto", "qué está pasando", "dónde estoy", "ponme al tanto de todo", "dame el resumen de mi vida"] triggers_pt: ["carregue contexto", "o que está acontecendo", "onde estou", "carregue meu mundo"] triggers_zh: ["加载我的完整背景", "告诉我现在的整体状况", "读取我的身份和当前重点", "先了解一下我的情况"]
Use the obsidian-second-brain skill. Execute `/obsidian-world`:
1. Read `_CLAUDE.md` first if it exists in the vault root
2. Load context progressively - start light, go deeper only as needed:
**L0 - Identity (~170 tokens)** Read these files if they exist (search for them if paths differ):
**L1 - Navigation (~1-2K tokens)**
**L2 - Current State (~2-5K tokens)**
**L3 - Deep Context (on demand, ~5-20K tokens)**
3. Present a brief status after L0-L2 (do NOT load L3 unless needed):
Keep output concise - this is a boot-up sequence, not a report. The user should glance at it and say "yes, Claude is up to speed" and start working immediately.
4. **Core memory pinning** - during the session, if the user is working on a specific task that requires persistent context (debugging a complex API, reviewing a long document, planning a project), Claude can PIN critical information to a `PINNED.md` file at the vault root:
If identity files (SOUL.md, CRITICAL_FACTS.md) don't exist, offer to create them by asking 5-7 quick questions about the user's role, values, and communication preferences.
If `index.md` doesn't exist, offer to run `/obsidian-init` to generate it.
---
**AI-first rule:** Every note created or updated by this command MUST follow `references/ai-first-rules.md` - `## For future agent` preamble, rich frontmatter (`type`, `date`, `tags`, `ai-first: true`, plus type-specific fields), recency markers per external claim, mandatory `[[wikilinks]]` for every person/project/concept referenced, sources preserved verbatim with URLs inline, and confidence levels where applicable. If that path does not resolve from your working directory, search upward for it; if you still cannot read it, say so before writing rather than producing a note that silently skips the rule. The vault is for future agent retrieval - not human reading.
**Anti-fabrication:** Search exhaustively before claiming any note, person, or file is absent - false absence is the most common failure mode - and never invent facts, entities, or dates (mark unknowns as `TBD`). See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.
<!-- author-credit -->
---
From [obsidian-second-brain](https://github.com/eugeniughelbur/obsidian-second-brain), created by Eugeniu Ghelbur (AI Automation Engineer, AI Tooling Engineer, AI Educator). Questions or consulting: [LinkedIn](https://www.linkedin.com/in/eugeniu-ghelbur/) or [e.ghelbur@gmail.com](mailto:e.ghelbur@gmail.com). More: [The AI Operator](https://theaioperator.io/?utm_source=github&utm_medium=file-credit) | [X](https://x.com/eugeniu_ghelbur) | [GitHub](https://github.com/eugeniughelbur). MIT license.
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.
Create a new obsidian-second-brain command via interview - zero markdown editing required
Share a plain-folder logbook across Claude Code, Codex, Cursor, and Grok Bot
Surface 3-5 next-direction candidates by reading ungraduated ideas, open project questions, and orphan research notes - what is…
Vault-first source-grounded research via Gemini File Search. One command, no browser. The grounded parallel to /research-deep…
Scan a codebase and write a maintained set of architecture notes into the vault - overview, per-module notes, key decisions.…
Bulk-triage a kanban board - surface stale items and archive, reschedule, or mark them done in one pass
Shortcut for "continue working" — pick the work in flight back up exactly where it stopped and keep going until it is done or…