create-command
CommandCreate a new obsidian-second-brain command via interview - zero markdown editing required
Bridge two unrelated domains using your vault's link graph - forces creative friction to spark new ideas
> /plugin marketplace add eugeniughelbur/obsidian-second-brain> /plugin install obsidian-second-brain@obsidian-second-brain
description: Bridge two unrelated domains using your vault's link graph - forces creative friction to spark new ideas category: thinking triggers_en: ["connect domains", "cross-pollinate", "bridge ideas", "find an unexpected link"] triggers_de: ["Themen verbinden", "Ideen kreuzen", "eine Brücke zwischen Ideen schlagen", "eine unerwartete Verbindung finden"] triggers_es: ["conecta estos dos temas", "cruza ideas de distintos mundos", "busca una conexión inesperada", "conecta esto con algo que no tenga que ver"] triggers_pt: ["conecte domínios", "cruze ideias", "crie pontes entre ideias", "encontre uma ligação inesperada"] triggers_zh: ["把这两个领域联系起来", "帮我找跨领域连接", "看看这些想法有什么意外联系", "用我的笔记做跨界联想"]
Use the obsidian-second-brain skill. Execute `/obsidian-connect $ARGUMENTS`:
Two arguments required: the two topics, domains, or note names to connect. If only one is given or none, ask the user for both.
1. Read `_CLAUDE.md` first if it exists in the vault root 2. Parse the two domains from arguments (e.g., `/obsidian-connect "distributed systems" "cooking"`) 3. For each domain, search the vault:
4. Find the bridge:
5. Generate creative connections:
6. Present 3-5 specific, actionable connections - not vague analogies but concrete ideas the user could act on 7. Offer to save the best connections to the ideas folder (resolved per `references/folder-map.md` - wiki-style `wiki/concepts/`, Obsidian-style `Ideas/`) with links to both source domains 8. Log the connection exercise in today's daily note
The value is in unexpected links. If the connection is obvious, dig deeper. The best output makes the user say "I never thought of it that way."
---
**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…