New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Obsidian Wiki Vault Setup

by AgriciDaniel in AgriciDaniel/claude-obsidian

Sets up or adopts a separate Obsidian knowledge vault through the claude-obsidian core script and routes follow-up work to the right wiki sub-skill.

MITAuto-check passedKnowledge Management

Install Obsidian Wiki Vault Setup

skills CLI
$ npx skills add AgriciDaniel/claude-obsidian --skill wiki -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AgriciDaniel/claude-obsidian wiki --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-obsidian.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/wiki .claude/skills/wiki && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
wiki
GitHub stars
15k
Token cost
~1.3k tokens
SKILL.md length
545 words
Files
11 (incl. references)
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Sets up or adopts a separate Obsidian knowledge vault through the claude-obsidian core script and routes follow-up work to the right wiki sub-skill.

  • Creating a new Obsidian vault with a standard structure
  • SKILL.md covers Set up a vault, Route operations, Mutation contract and Installation context, plus 2 more sections
  • Calls python3
  • Adopting an existing Obsidian vault for use with the claude-obsidian core

What it does

The skill keeps the plugin install and your vault apart and refuses to use the product folder as a vault, even when it is the current directory. It calls the portable core script `scripts/claude-obsidian.py` by absolute path and picks the vault from an explicit `--vault` option, then the `CLAUDE_OBSIDIAN_VAULT` variable, then the nearest `.claude-obsidian.json`, then a single initialized vault at or above the current folder. If the choice is missing or ambiguous it stops.

Two commands do the setup: `init` for a new vault and `adopt` for an existing Obsidian vault. Both run as a dry run first. Before `--apply`, the agent shows the chosen path and the list of changed paths, then passes back the approved plan hash unchanged, and it avoids `--force` unless you have approved replacements. Baseline setup uses no network. Domain-specific scaffolds are drafted as one transaction after the baseline, using the modes reference, rather than by editing vault files directly.

A routing table sends other requests to sibling skills: ingesting sources, answering from the vault, saving a conversation result, budgeted web research, health checks, rolling up log entries and canvas work. Queries stay read-only, and saving anything from a query is a separate step you ask for.

When your agent uses it

  • Creating a new Obsidian vault with a standard structure
  • Adopting an existing Obsidian vault for use with the claude-obsidian core
  • Choosing which wiki sub-skill should handle ingest, query or lint
  • Configuring which vault a workspace or project should use

Example prompts

  • “Set up a new wiki vault in D:/notes/research and show me the preview first.”
  • “Adopt my existing Obsidian vault at ~/Documents/Vault as a claude-obsidian wiki.”
  • “Which wiki skill should I use to add these three PDFs to my vault?”

Requirements

  • Python 3
  • An Obsidian vault location you control

What it can do on your machine

Read from SKILL.md and the folder at commit 32ac5a0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Obsidian Wiki Vault Setup loads about 1.3k tokens when it runs, and up to ~8.7k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 545 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~96
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AgriciDaniel/claude-obsidian at commit 32ac5a0, republished under its MIT licence (© AgriciDaniel). 545 words, ~1,347 tokens.

Download SKILL.mdSave it as .claude/skills/wiki/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
wiki
description
Initialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt this vault, Obsidian vault, second brain setup, persistent wiki.

Wiki orchestration

Treat the installed product as code and the selected user vault as data. Never use the plugin/product root as a vault, even when the current directory happens to be the product checkout.

Resolve the portable core from this skill's installation and invoke it by absolute path:

bash
CORE=/absolute/product/root/scripts/claude-obsidian.py
python3 "$CORE" --help

Resolve a vault in this order: explicit --vault, CLAUDE_OBSIDIAN_VAULT, the nearest .claude-obsidian.json, then an unambiguous initialized vault at or above the current directory. Fail closed when selection is missing or ambiguous.

Baseline setup requires no network egress. Do not fetch templates, plugins, or remote content unless the user separately approves the destinations and budget.

Set up a vault

Use the deterministic setup commands. Both are dry-run by default.

For a new, separate vault:

bash
python3 "$CORE" init /absolute/path/to/vault \
  --generated-at <ISO-UTC> --operation-id init-reviewed
python3 "$CORE" init /absolute/path/to/vault \
  --generated-at <ISO-UTC> --operation-id init-reviewed \
  --approved-plan-sha256 <reviewed-sha256> --apply

For an existing Obsidian vault:

bash
python3 "$CORE" adopt /absolute/path/to/vault \
  --generated-at <ISO-UTC> --operation-id adopt-reviewed
python3 "$CORE" adopt /absolute/path/to/vault \
  --generated-at <ISO-UTC> --operation-id adopt-reviewed \
  --approved-plan-sha256 <reviewed-sha256> --apply

Before --apply, show the selected path and changed-path preview, then pass the emitted approved_plan_sha256 unchanged. Do not use --force unless the user has reviewed the conflicts and explicitly approved replacement. Setup is non-destructive by default and creates no upstream Git remote.

If the user asks for a domain-specific scaffold, establish the baseline first, then read modes.md. Draft the additional pages and configuration as one operation-level transaction. Never mutate vault files with host Write/Edit tools or an Obsidian transport.

Route operations

Route the user's intent without silently broadening it:

IntentSkill
Ingest supplied sourceswiki-ingest
Answer from existing vault knowledgewiki-query
Save a specific conversation resultsave
Research the public web under a budgetautoresearch
Check vault healthwiki-lint
Roll up log entrieswiki-fold
Work with a canvascanvas

Query is read-only. Persistence from a query must be an explicit, separately scoped Save operation. Never capture a transcript or update the hot cache merely because a session ended.

Show full SKILL.md (262 more words)Show less

Mutation contract

Read operation-transactions.md before any custom scaffold or mutation. One logical operation must produce one inspected and recoverable claude-obsidian.transaction.v1 bundle. Parallel agents may return drafts and evidence only; the orchestrator merges them and applies once. Every canonical page create or removal includes an active index or MOC update in that bundle; update the overview only when the stable high-level picture changed. Raw source payloads are create-only. There are no automatic commits.

Use provenance.md when initializing or changing source and claim ledgers. Unsupported evidence stays unsupported; never invent a source, quote, date, locator, or confidence.

After a successful apply, report the operation ID and exact changed paths. If the user explicitly wants a Git checkpoint, run it separately:

bash
python3 "$CORE" checkpoint OPERATION_ID --vault /absolute/path/to/vault

On a conflict, re-read and rebuild. On interruption, use transaction recover. Reuse an operation ID only with the identical bundle.

Installation context

Read install-modes.md when installation or host behavior matters. Hooks are optional adapters; portable behavior lives in the core and skills.

Conditional references

Read only the reference needed for the current request:

  • frontmatter.md when defining or adopting a property schema;
  • css-snippets.md for requested Obsidian visual customization;
  • git-setup.md for explicit local Git or checkpoint setup;
  • plugins.md when evaluating optional Obsidian integrations;
  • mcp-setup.md when the user asks to evaluate an external read transport;
  • rest-api.md only when the user explicitly has or requests the Local REST API adapter.

Think, verify, grow

Before applying, pause once: observe existing state, verify the vault selection and evidence, then choose the smallest reversible operation that satisfies the request. Afterward, report uncertainty and the next useful improvement without performing it automatically.

© AgriciDaniel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (references) in skills/wiki of AgriciDaniel/claude-obsidian.

  • SKILL.md
  • references/css-snippets.md
  • references/frontmatter.md
  • references/git-setup.md
  • references/install-modes.md
  • references/mcp-setup.md
  • references/modes.md
  • references/operation-transactions.md
  • references/plugins.md
  • references/provenance.md
  • references/rest-api.md

Open the folder on GitHubat commit 32ac5a0

Compare with similar skills

Obsidian Wiki Vault Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Obsidian Wiki Vault Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Obsidian Wiki Vault Setup this skillAgriciDaniel/claude-obsidian15k—~1.3kAutomated safety check: PassMIT
LLM Wikilewislulu/llm-wiki-skill655—~3.7kAutomated safety check: PassNone
NanoClaw LLM Wiki Setupnanocoai/nanoclaw31k1 repos~1.3kAutomated safety check: PassMIT
Swarmvaultswarmclawai/swarmvault708—~6.1kAutomated safety check: PassMIT
LLM Wikipraneybehl/llm-wiki-plugin117—~5.7kAutomated safety check: PassMIT
Karpathy WikiSherwinQ/karpathy-wiki113—~967Automated safety check: PassMIT

Similar skills

  • LLM Wiki

    lewislulu/llm-wiki-skill

    Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…

    655 GitHub stars~3.7k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed

  • NanoClaw LLM Wiki Setup

    nanocoai/nanoclaw

    Adds a persistent wiki knowledge base to a NanoClaw group following Karpathy's LLM Wiki pattern, with folders, a tailored container skill and a CLAUDE.md section.

    31k GitHub starsUsed in 1 repo~1.3k tokens
    Knowledge ManagementAuto-check passed

  • Swarmvault

    swarmclawai/swarmvault

    Use SwarmVault when the user needs a local-first knowledge vault that writes durable markdown, graph, search, dashboard, review, chat-session, context-pack, task-ledger, static AI export, retrieval…

    708 GitHub stars~6.1k tokensUpdated 3 mo ago
    Knowledge ManagementAuto-check passed

  • LLM Wiki

    praneybehl/llm-wiki-plugin

    Build and maintain an LLM-curated knowledge base from papers, articles, transcripts, notes and project findings.

    117 GitHub stars~5.7k tokensUpdated 24 days ago
    Knowledge ManagementAuto-check passed

  • Karpathy Wiki

    SherwinQ/karpathy-wiki

    A skill your agent uses when building or maintaining a personal knowledge base with LLM assistance.

    113 GitHub stars~967 tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed

  • My LLM Wiki

    MartinLwx/dotfiles

    Provides access to the user's personal wiki, including notes, research, project documentation, decisions, and archived knowledge.

    140 GitHub stars~2.7k tokensUpdated 17 days ago
    Knowledge ManagementAuto-check passed

More from AgriciDaniel/claude-obsidian

All 15 skills in this repo

  • Bounded Autoresearch

    AgriciDaniel/claude-obsidian

    Runs a bounded, source-grounded research loop that drafts a cited dossier and can propose a separately reviewed merge into an Obsidian vault.

    15k GitHub stars~1.6k tokensUpdated 26 days ago
    Auto-check passed

  • Obsidian Canvas Boards

    AgriciDaniel/claude-obsidian

    Creates, inspects and updates Obsidian JSON Canvas boards in a vault, with text, file, link, group and edge nodes, using safe recoverable edits.

    15k GitHub stars~1.4k tokensUpdated 26 days ago
    Auto-check passed

  • Obsidian Wiki Log Fold

    AgriciDaniel/claude-obsidian

    Creates a bounded, extractive rollup of recent Obsidian wiki log entries, previewed by default, with one optional apply step and no changes to child pages.

    15k GitHub stars~1.2k tokensUpdated 26 days ago
    Auto-check passed

  • Defuddle Web Page Cleaner

    AgriciDaniel/claude-obsidian

    Plans, and with explicit network consent runs, an external Defuddle extractor that turns an article-like HTTPS page into clean Markdown for later wiki ingestion.

    15k GitHub stars~1.1k tokensUpdated 26 days ago
    Auto-check passed

  • Obsidian Bases Editor

    AgriciDaniel/claude-obsidian

    Explains, drafts and validates Obsidian Bases .base files, building filters, formulas and table, card or list views, and applying edits only through one inspected transaction.

    15k GitHub stars~1.2k tokensUpdated 26 days ago
    Auto-check passed

  • Obsidian Markdown Syntax

    AgriciDaniel/claude-obsidian

    Explains, drafts and validates Obsidian Flavored Markdown such as properties, wikilinks, embeds, callouts and Mermaid, with vault edits applied through approved transactions.

    15k GitHub stars~1.1k tokensUpdated 26 days ago
    Auto-check passed

Works with

Categories

Questions about Obsidian Wiki Vault Setup

What does Obsidian Wiki Vault Setup do?

Sets up or adopts a separate Obsidian knowledge vault through the claude-obsidian core script and routes follow-up work to the right wiki sub-skill. The skill keeps the plugin install and your vault apart and refuses to use the product folder as a vault, even when it is the current directory.json`, then a single initialized vault at or above the current folder.

When should I use Obsidian Wiki Vault Setup?

Obsidian Wiki Vault Setup fits situations like: creating a new Obsidian vault with a standard structure; adopting an existing Obsidian vault for use with the claude-obsidian core; choosing which wiki sub-skill should handle ingest, query or lint; configuring which vault a workspace or project should use.

How do I install Obsidian Wiki Vault Setup in Claude Code?

Run `npx skills add AgriciDaniel/claude-obsidian --skill wiki -a claude-code`. Or copy the skill folder (skills/wiki in AgriciDaniel/claude-obsidian) into .claude/skills/wiki in your project. Claude Code loads it when a task matches its description.

How do I install Obsidian Wiki Vault Setup in Codex?

Run `npx skills add AgriciDaniel/claude-obsidian --skill wiki -a codex`. Or copy the skill folder (skills/wiki in AgriciDaniel/claude-obsidian) into .agents/skills/wiki in your project. Codex loads it when a task matches its description.

Can I use Obsidian Wiki Vault Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AgriciDaniel/claude-obsidian --skill wiki -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wiki, .gemini/skills/wiki, .github/skills/wiki and .opencode/skills/wiki in your project.

What does Obsidian Wiki Vault Setup need to run?

Going by SKILL.md and its folder, Obsidian Wiki Vault Setup needs the command-line tools its instructions call (python3). Our summary lists: Python 3; An Obsidian vault location you control.

Does Obsidian Wiki Vault Setup access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Obsidian Wiki Vault Setup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Obsidian Wiki Vault Setup use?

Obsidian Wiki Vault Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Obsidian Wiki Vault Setup use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.4k tokens, read only when the agent opens those files.

What are the alternatives to Obsidian Wiki Vault Setup?

Skills that share tags, products or a category with Obsidian Wiki Vault Setup: LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), NanoClaw LLM Wiki Setup (nanocoai/nanoclaw, 31k stars), Swarmvault (swarmclawai/swarmvault, 708 stars) and LLM Wiki (praneybehl/llm-wiki-plugin, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Obsidian Wiki Vault Setup?

AgriciDaniel (a GitHub user) maintains it in AgriciDaniel/claude-obsidian, which has 15,379 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on September 10, 2026.

Source: AgriciDaniel/claude-obsidian on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.