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…
Initialize or repair an Obsidian wiki vault's required structure and configuration.
$ npx skills add Ar9av/obsidian-wiki --skill wiki-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Ar9av/obsidian-wiki wiki-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.skills/wiki-setup .claude/skills/wiki-setup && rm -rf skills-srcUse ~/.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/
Install the "wiki-setup" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-setup into .claude/skills/wiki-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiki-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Ar9av/obsidian-wiki --skill wiki-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Ar9av/obsidian-wiki wiki-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.skills/wiki-setup .agents/skills/wiki-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wiki-setup" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-setup into .agents/skills/wiki-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiki-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ar9av/obsidian-wiki --skill wiki-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Ar9av/obsidian-wiki wiki-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.skills/wiki-setup .cursor/skills/wiki-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wiki-setup" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-setup into .cursor/skills/wiki-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiki-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Ar9av/obsidian-wiki.git --path .skills/wiki-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Ar9av/obsidian-wiki --skill wiki-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Ar9av/obsidian-wiki wiki-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.skills/wiki-setup .gemini/skills/wiki-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wiki-setup" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-setup into .gemini/skills/wiki-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiki-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Ar9av/obsidian-wiki wiki-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Ar9av/obsidian-wiki --skill wiki-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .github/skills && cp -r skills-src/.skills/wiki-setup .github/skills/wiki-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wiki-setup" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-setup into .github/skills/wiki-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiki-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ar9av/obsidian-wiki --skill wiki-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Ar9av/obsidian-wiki wiki-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.skills/wiki-setup .opencode/skills/wiki-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wiki-setup" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-setup into .opencode/skills/wiki-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiki-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
wiki-setupInitialize or repair an Obsidian wiki vault's required structure and configuration.
Wiki Setup is an agent skill from Ar9av/obsidian-wiki. Initialize or repair an Obsidian wiki vault's required structure and configuration. Use for new-vault setup, .env/config creation, reconfiguration, or broken setup recovery.
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Knowledge Management, covering LLM wikis. It works with Obsidian. The repository describes itself as: Framework for AI agents to build and maintain a digital brain through Obsidian wiki | Memory System for Agents. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 0cc5d90. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
gitcurlpython3From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Wiki Setup loads about 3.7k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 1,552 words of instructions outside code blocks.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
configuration. Use for new-vault setup, .env/config creation, reconfiguration, or broken setup recovery.## Step 1: Create .envIf `.env` doesn't exist, create it from `.env.example`. Ask the user for:- [ ] `.env` has `OBSIDIAN_VAULT_PATH` setAutomated 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.
The full file from Ar9av/obsidian-wiki at commit 0cc5d90, republished under its MIT licence (© Ar9av). 1,552 words, ~3,720 tokens.
.claude/skills/wiki-setup/SKILL.md (or your agent's skills folder).You are setting up a new Obsidian wiki vault (or repairing an existing one).
If .env doesn't exist, create it from .env.example. Ask the user for:
Where should the vault live? → OBSIDIAN_VAULT_PATH
~/Documents/obsidian-wiki-vaultWhere are your source documents? → OBSIDIAN_SOURCES_DIR
~/Documentswiki-ingest/SKILL.md for how repo sources are handled.Want to import Claude history? → CLAUDE_HISTORY_PATH
~/.claudeHave QMD installed? → QMD_WIKI_COLLECTION / QMD_PAPERS_COLLECTION / QMD_TRANSPORT
wiki-query and source discovery in wiki-ingest.QMD_TRANSPORT=mcp unless the user wants the agent to call the local qmd CLI directly.QMD_CLI_SEARCH_MODE=quality by default; suggest balanced if reranking is too slow.Grep automatically..env.example (QMD section).QMD_WIKI_COLLECTION is set, verify the collection excludes _raw/. The wiki
collection and papers collection must stay disjoint — wiki-query cites them as
separate layers (compiled knowledge vs. raw staging), and OBSIDIAN_VAULT_PATH contains
_raw/, so a plain qmd collection add <vault> silently merges the two.
Read ~/.config/qmd/index.yml, find the entry for $QMD_WIKI_COLLECTION, and check its
ignore list includes _raw/** (and ideally log.md, which has no semantic value). If
the collection doesn't exist yet, create it (qmd collection add "$OBSIDIAN_VAULT_PATH" --name <collection-name>), then add the ignore block to index.yml by hand — qmd
has no --ignore flag and refuses a second collection add on a path that already has
one, so editing the YAML is the only way to scope it. Run qmd update after editing.
If the collection already exists without the ignore block, tell the user their
wiki collection is indexing _raw/ (including _raw/_archived/ drafts left behind by
wiki-ingest) and offer to add the ignore block and re-run qmd update.Token budget warning threshold? → WIKI_TOKEN_WARN_THRESHOLD
100000 (warn when full-wiki read would cost > 100K tokens)0 to disable the warning entirelywiki-status shows a token footprint table and emits this warning automaticallyEnable staged writes? → WIKI_STAGED_WRITES
false (pages written directly to their final location)true for team wikis, high-stakes domains, or any vault where the human wants final say on every LLM-written page_staging/ first; run /wiki-stage-commit to review and promote themwiki-status shows a "Staged writes pending" count when files are waitingAfter resolving config, assign the global config directory with the exact
obsidian_wiki_config_dir algorithm from the Config Resolution Protocol in
.skills/llm-wiki/SKILL.md. Create the shared writing profile only when it does not
already exist. Preserve an existing $GLOBAL_CONFIG_DIR/WRITING.md; never overwrite it
and do not ask additional writing-style questions.
Use OBSIDIAN_WIKI_REPO when it was loaded from config. When it is absent, derive the
absolute repository/data root from this loaded skill's absolute path, distinguishing the
packaged <root>/skills/wiki-setup/SKILL.md layout from the source
<root>/.skills/wiki-setup/SKILL.md layout. Then check both canonical template layouts:
<root>/skills/llm-wiki/references/WRITING.md<root>/.skills/llm-wiki/references/WRITING.mdGLOBAL_CONFIG_DIR="$(obsidian_wiki_config_dir)"
mkdir -p "$GLOBAL_CONFIG_DIR"
SKILL_FILE="<absolute path of this loaded wiki-setup/SKILL.md>"
SKILL_DIR="$(cd "$(dirname "$SKILL_FILE")" && pwd)"
if [ -n "${OBSIDIAN_WIKI_REPO:-}" ]; then
WIKI_ROOT="${OBSIDIAN_WIKI_REPO%/}"
else
case "$SKILL_DIR" in
*/.skills/wiki-setup) WIKI_ROOT="${SKILL_DIR%/.skills/wiki-setup}" ;;
*/skills/wiki-setup) WIKI_ROOT="${SKILL_DIR%/skills/wiki-setup}" ;;
*) echo "Cannot derive writing-profile template root from $SKILL_DIR" >&2; exit 1 ;;
esac
fi
WRITING_TEMPLATE=""
for candidate in \
"$WIKI_ROOT/skills/llm-wiki/references/WRITING.md" \
"$WIKI_ROOT/.skills/llm-wiki/references/WRITING.md"
do
if [ -f "$candidate" ]; then
WRITING_TEMPLATE="$candidate"
break
fi
done
[ -n "$WRITING_TEMPLATE" ] || { echo "Writing profile template not found under $WIKI_ROOT" >&2; exit 1; }
WRITING_PROFILE="$GLOBAL_CONFIG_DIR/WRITING.md"
if [ ! -e "$WRITING_PROFILE" ]; then
cp "$WRITING_TEMPLATE" "$WRITING_PROFILE"
fimkdir -p "$OBSIDIAN_VAULT_PATH"/{concepts,entities,skills,references,synthesis,journal,projects,_archives,_raw,_staging,.obsidian}.obsidian/ — Obsidian's own config. Creates vault recognition.projects/ — Per-project knowledge (populated during ingest)._archives/ — Stores wiki snapshots for rebuild/restore operations._raw/ — Staging area for unprocessed drafts. Drop rough notes here; wiki-ingest will promote them to proper wiki pages and move the originals into _raw/_archived/ (created on first use)._staging/ — Review queue for LLM-written pages when WIKI_STAGED_WRITES=true. Pages here are not visible in Obsidian's graph until promoted via /wiki-stage-commit.---
title: Wiki Index
---
# Wiki Index
*This index is automatically maintained. Last updated: TIMESTAMP*
## Concepts
*No pages yet. Use `wiki-ingest` to add your first source.*
## Entities
## Skills
## References
## Synthesis
## Journal---
title: Wiki Log
---
# Wiki Log
- [TIMESTAMP] INIT vault_path="OBSIDIAN_VAULT_PATH" categories=concepts,entities,skills,references,synthesis,journal---
title: Hot Cache
updated: TIMESTAMP
---
# Hot Cache
*A ~500-word semantic snapshot of recent activity. Updated after every major write operation.*
## Recent Activity
- [TIMESTAMP] INIT — vault created at OBSIDIAN_VAULT_PATH
## Active Threads
*None yet — start ingesting sources to populate.*
## Key Takeaways
*None yet.*
## Flagged Contradictions
*None yet.*Create an empty manifest so ingest skills have a tracking file to append to and
obsidian-wiki doctor reports the vault as complete (it treats .manifest.json
as a required core file):
printf '{}\n' > "$OBSIDIAN_VAULT_PATH/.manifest.json"Create minimal Obsidian config for a good out-of-box experience:
{
"strictLineBreaks": false,
"showFrontmatter": false,
"defaultViewMode": "preview",
"livePreview": true
}{
"baseFontSize": 16
}Tell the user about these recommended community plugins (they install manually):
Run a quick sanity check:
concepts/, entities/, skills/, references/, synthesis/, journal/, projects/, _archives/, _raw/index.md exists at vault rootlog.md exists at vault roothot.md exists at vault root.manifest.json exists at vault root (empty {} is fine).env has OBSIDIAN_VAULT_PATH set.obsidian/ directory exists_staging/ directory exists (required even when WIKI_STAGED_WRITES is not set — created on setup for future use)WRITING_PROFILE exists at the resolved global config directoryReport the results, including the resolved absolute WRITING_PROFILE path, and tell the user they can now:
wiki-status to see what's available to ingestwiki-ingest to add their first sourcesclaude-history-ingest to mine their Claude conversationscodex-history-ingest to mine their Codex sessions (if they use Codex)wiki-status again anytime to check the deltaAsk the user: "Want to auto-capture findings at session end?"
If yes, install the Stop hook into their global Claude Code settings so that every session
with meaningful work automatically prompts /wiki-capture --quick before closing.
What the hook does: reads the session transcript on Stop, counts file edits and shell
calls, and if significant work happened, asks Claude to run /wiki-capture --quick once.
The wiki-capture quick-mode KEEP/SKIP gate prevents noise — routine or
inconclusive sessions are skipped automatically.
Installation steps:
Find the obsidian-wiki repo path. If OBSIDIAN_WIKI_REPO is set in config, use that.
Otherwise, check common locations: ~/Documents/projects/obsidian-wiki, ~/obsidian-wiki,
or ask the user.
Locate the wiki-stop-capture.sh script. Its path differs between a pip/uv install and a
source checkout, so check both layouts under <REPO_PATH> and use the first that exists:
<REPO_PATH>/hooks/wiki-stop-capture.sh — packaged install (OBSIDIAN_WIKI_REPO
points at the bundled _data/ dir, which ships the hook under hooks/).<REPO_PATH>/.claude/hooks/wiki-stop-capture.sh — source checkout.If neither exists (e.g. an older wheel that predates bundling the hook), fetch the canonical
copy to a stable location and point at that instead. Use the global config dir from the
Config Resolution Protocol in llm-wiki/SKILL.md (XDG-style ~/.config/obsidian-wiki by
default, or the legacy ~/.obsidian-wiki if that already exists):
CONFIG_DIR="$( [[ -d "$HOME/.obsidian-wiki" && ! -e "${XDG_CONFIG_HOME:-$HOME/.config}/obsidian-wiki" ]] && echo "$HOME/.obsidian-wiki" || echo "${XDG_CONFIG_HOME:-$HOME/.config}/obsidian-wiki" )"
mkdir -p "$CONFIG_DIR/hooks"
curl -fsSL https://raw.githubusercontent.com/Ar9av/obsidian-wiki/main/.claude/hooks/wiki-stop-capture.sh \
-o "$CONFIG_DIR/hooks/wiki-stop-capture.sh"
chmod +x "$CONFIG_DIR/hooks/wiki-stop-capture.sh"Use the resolved absolute path as <HOOK_PATH> below.
Merge the hook entry into ~/.claude/settings.json:
{
"hooks": {
"Stop": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "bash <HOOK_PATH>"
}
]
}
]
}
} If ~/.claude/settings.json already exists and has a hooks.Stop array, append the new
entry rather than replacing — don't clobber existing hooks.
Note — expect a duplicate nudge inside this repo. The obsidian-wiki repo ships its own git-tracked
.claude/settings.jsonregistering the same Stop hook at a relative path. Claude Code merges project-level and user-level hook config rather than letting one override the other, so sessions ending inside the repo itself fire both registrations. This is expected and harmless — the hook claims an atomic per-session sentinel, so only one nudge is emitted. Leave both in place: removing the project entry dirties a tracked framework file and disables capture for anyone who clones the repo without doing the global install.
/wiki-capture --quick at the
end of any session where you write files or run ≥ 4 shell commands."To uninstall later: remove the hook entry from ~/.claude/settings.json or set
WIKI_STOP_CAPTURE=false in your shell to skip capture for a single session
(HIVEMIND_CAPTURE=false is still honoured).
Ask the user: "Want to sync your vault to a private GitHub repo?"
The vault is plain markdown, so pushing it to git gets you version history, backup, and cross-device sync for free. This is opt-in — skip it if the user declines or has no repo ready.
If yes:
https://github.com/you/my-wiki.git). Recommend it be private
if the vault holds personal notes.git init, a default .gitignore, and wiring the origin remote —
this is the same code path obsidian-wiki setup's interactive prompt and setup.sh use, so
there's one implementation to keep correct (see issue #153 for why that matters):obsidian-wiki sync-setup "<repo-url>" --vault "$OBSIDIAN_VAULT_PATH"obsidian-wiki binary isn't on PATH (source checkout without an install), run it from
the repo instead: PYTHONPATH="$OBSIDIAN_WIKI_REPO" python3 -m obsidian_wiki.cli sync-setup ...
using whichever of OBSIDIAN_WIKI_REPO or a local checkout path is available.obsidian-wiki sync any time afterward to commit and push pending
vault changes (stages everything, commits with a timestamp, pushes). There's no config file to
check for sync status — the vault's own git remote is the source of truth.If QMD_WIKI_COLLECTION is configured and the local QMD CLI is available, run qmd update after the initial vault files exist so the fresh vault is immediately queryable. No embedding pass is usually needed at setup time because the vault starts empty, so a plain update is enough unless you have already populated pages. Before running it, confirm the _raw/ exclusion described in Step 1.4 is in place — otherwise this update indexes the (currently empty) staging directory into the wiki collection too, and every future draft dropped there joins it silently.
© Ar9av, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .skills/wiki-setup of Ar9av/obsidian-wiki.
Open the folder on GitHubat commit 0cc5d90
Wiki 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wiki Setup this skillAr9av/obsidian-wiki | 3.5k | — | ~3.7k | Automated safety check: Notes | MIT | |
| LLM Wikilewislulu/llm-wiki-skill | 655 | — | ~3.7k | Automated safety check: Pass | None | |
| LLM Wikizosmaai/pi-llm-wiki | 605 | — | ~4.4k | Automated safety check: Pass | MIT | |
| LLM Wikipraneybehl/llm-wiki-plugin | 117 | — | ~5.7k | Automated safety check: Pass | MIT | |
| Karpathy WikiSherwinQ/karpathy-wiki | 113 | — | ~967 | Automated safety check: Pass | MIT | |
| My LLM WikiMartinLwx/dotfiles | 140 | — | ~2.7k | Automated safety check: Pass | None |
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…
zosmaai/pi-llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern.
praneybehl/llm-wiki-plugin
Build and maintain an LLM-curated knowledge base from papers, articles, transcripts, notes and project findings.
SherwinQ/karpathy-wiki
A skill your agent uses when building or maintaining a personal knowledge base with LLM assistance.
MartinLwx/dotfiles
Provides access to the user's personal wiki, including notes, research, project documentation, decisions, and archived knowledge.
xoai/sage-wiki
Reference skill for sage-wiki — local-first knowledge graph with MCP server, REST API, compiled wiki, and Obsidian-compatible output.
Ar9av/obsidian-wiki
Ingest Hermes agent history into Obsidian as distilled knowledge.
Ar9av/obsidian-wiki
Ingest Codex CLI conversation/session history into Obsidian as distilled knowledge.
Ar9av/obsidian-wiki
Ingest GitHub Copilot CLI/session history into Obsidian as distilled knowledge.
Ar9av/obsidian-wiki
Adjust the user's Obsidian visual layout with CSS snippets. An agent skill from Ar9av/obsidian-wiki.
Ar9av/obsidian-wiki
Ingest OpenClaw session/history data into Obsidian as distilled knowledge.
Ar9av/obsidian-wiki
Turn the current conversation or finding into a structured permanent wiki note.
Works with
Categories
Initialize or repair an Obsidian wiki vault's required structure and configuration. Wiki Setup is an agent skill from Ar9av/obsidian-wiki. Initialize or repair an Obsidian wiki vault's required structure and configuration.
Wiki Setup fits situations like: new-vault setup; .env/config creation; reconfiguration; broken setup recovery.
Run `npx skills add Ar9av/obsidian-wiki --skill wiki-setup -a claude-code`. Or copy the skill folder (.skills/wiki-setup in Ar9av/obsidian-wiki) into .claude/skills/wiki-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Ar9av/obsidian-wiki --skill wiki-setup -a codex`. Or copy the skill folder (.skills/wiki-setup in Ar9av/obsidian-wiki) into .agents/skills/wiki-setup in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ar9av/obsidian-wiki --skill wiki-setup -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-setup, .gemini/skills/wiki-setup, .github/skills/wiki-setup and .opencode/skills/wiki-setup in your project.
Going by SKILL.md and its folder, Wiki Setup needs the command-line tools its instructions call (git, curl and python3).
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Wiki Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Wiki Setup: LLM Wiki (lewislulu/llm-wiki-skill, 655 stars), LLM Wiki (zosmaai/pi-llm-wiki, 605 stars), LLM Wiki (praneybehl/llm-wiki-plugin, 117 stars) and Karpathy Wiki (SherwinQ/karpathy-wiki, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Ar9av (a GitHub user) maintains it in Ar9av/obsidian-wiki, which has 3,529 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 6, 2026.
Source: Ar9av/obsidian-wiki on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.