Obsidian Skills
kepano/obsidian-skillsSix skills by Obsidian's Steph Ango (kepano) for Obsidian Markdown, Bases, JSON Canvas, the Obsidian CLI, Defuddle and Knap.
Persistent, self-rewriting memory in your Obsidian vault: 48 commands, a shared cross-agent logbook (Crew), scheduled maintenance and a research toolkit.
An unusually deep, tested memory system with a real cross-agent logbook, but it rewrites your notes automatically and its research commands depend on several paid APIs; read the freshness policy before trusting it with a real vault.
This is one very large skill (about 90 KB) rather than a bundle: it turns an Obsidian vault into a knowledge base that Claude Code and other agents read, write and reconcile over time. The core idea, credited as an evolution of Karpathy's LLM Wiki pattern, is that new information rewrites existing notes instead of only appending, and contradictions are reconciled automatically under a documented freshness policy (OKM) that marks each stored fact as timeless, dated, or a pointer. A small CRITICAL_FACTS.md file (about 120 tokens) loads identity context at session start, with progressive token budgets for more.
Crew is a separate addition: a shared logbook, usable without Obsidian, so Claude Code, Codex, Cursor and Grok Bot can see what the other agents did and leave lessons that a human promotes to a rule with keep. The 48 commands include /obsidian-init, /obsidian-save, /obsidian-find, daily entries, kanban and people notes, decision and deal tracking, 4 scheduled maintenance agents, and a 7-command research toolkit (/research, /research-deep, /x-read, /x-pulse, /notebooklm, /youtube, /podcast) that calls Perplexity, xAI, Gemini, YouTube and OpenAI Whisper APIs when keys are set, falling back to free key-less sources (Wikipedia, HackerNews, arXiv, Reddit and others) when they are not. It ships 172 scripts, 111 tests and 10 eval files, needs Python via uv, and documents where its .env file lives on each OS.
One skill at 90 KB with 78 references, 172 scripts, 111 tests and 10 eval files in the repository, the top of the depth scale.
Counted from the repository file tree. How we score depth.
An Obsidian-vault memory skill with commands, hooks and an MCP server that read and rewrite your notes. It registers SessionStart, PostToolUse and PostCompact hooks and edits ~/.claude/settings.json; an optional background agent runs headless with permissions skipped but is off until you set two environment flags. Several install and research scripts are missing from our copy, and the quick-install one-liner pipes the main branch to bash.
curl -fsSL https://raw.githubusercontent.com/eugeniughelbur/obsidian-second-brain/main/scripts/quick-install.sh | bash from the unpinned main branch (also in SKILL.md line 75); quick-install.sh is not in our files.README.md:43git pull in the checkout.install.sh:59uv sync in the repo to install Python dependencies.install.sh:116uv run --no-project --with mcp<2 python .../server.py, resolving the mcp package at launch under only an upper-bound constraint..claude-plugin/plugin.json:15The repository (397 files) on Oct 29, 2026. Not a full review: 272 of 397 files were not downloaded (large repository; we reviewed the skill folders); we read 4 of 32 code files; it relies on code outside the repository: 272 repo files we do not have, including scripts/quick-install.sh, scripts/setup_settings_hook.py, scripts/platform-home.sh, the scripts/research toolkit, .env.example and integrations/obsidian-mcp-server/server.py; Not read in full: hooks/*.sh and *.py, adapters/lib.sh, and the Python scripts under scripts/ (inspected only by grep for network, subprocess, cron and delete operations); External services: xAI, Perplexity, Gemini, YouTube, OpenAI APIs.
NVIDIA SkillSpector static scan: 93 pattern hits (Agent Snooping 17, analysis-evasion 13, Privilege Escalation 10, Supply Chain 10, Rogue Agent 9, Excessive Agency 7). The YARA 'backdoor_persistence' hit is a sentence in architecture.md about not creating crontab artifacts; 'analysis-evasion' hits are the scanner noting partially analysed referenced files; credential hits are .env examples and the research key table. --dangerously-skip-permissions appears in documentation and in the opt-in background-agent hook described above.
A review, not a certification. Skills change after we check them — read the files before installing.
MIT — commercial use allowed.
Yes. The README describes 4 scheduled agents that maintain the vault while you sleep and a Crew logbook with no background loop of its own, so unattended maintenance is a stated design goal, though the research commands and rewrites still warrant a later review.
Six skills by Obsidian's Steph Ango (kepano) for Obsidian Markdown, Bases, JSON Canvas, the Obsidian CLI, Defuddle and Knap.
Forty skills that let an agent build and maintain a linked Obsidian vault from your notes, code and past agent sessions, then answer questions with citations.
Memory layer that mines agent session logs into a shared markdown wiki and re-injects it across Codex, Claude Code, Cursor and others, locally or via memU Cloud.
Cross-agent persistent memory for Claude Code, Codex, OpenClaw, OpenCode and DeepSeek Harness: Markdown files as the source of truth, with a Milvus search index.
It is an agent skill that operates an Obsidian vault as persistent, self-rewriting memory for Claude Code and other agents, with 48 commands for saving, searching and maintaining notes, plus a cross-agent shared logbook called Crew.
The README's quick path is a curl | bash installer, after which you restart Claude Code and run /crew setup or /obsidian-init, pointing it at your vault or a plain folder. It also supports Codex, Gemini CLI, OpenCode and others.
No for basic note operations. The 7 research commands use paid APIs (Perplexity, xAI, Gemini, YouTube, OpenAI) when keys are set, and 2 of them fall back to free, key-less sources like Wikipedia and arXiv when keys are absent.
The author documents a freshness policy for how facts are marked and reconciled, but automatic rewriting is still a real behavior change to your vault. Review the policy and consider versioning your vault with git before relying on it for important notes.