Agent skill

Wiki Setup

by Ar9av in Ar9av/obsidian-wiki

Initialize or repair an Obsidian wiki vault's required structure and configuration.

MITAuto-check: notesKnowledge Management

Install Wiki Setup

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

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

GitHub CLI
$ gh skill install Ar9av/obsidian-wiki wiki-setup --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/Ar9av/obsidian-wiki.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.skills/wiki-setup .claude/skills/wiki-setup && 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-setup
GitHub stars
3.5k
Token cost
~3.7k tokens
SKILL.md length
1,552 words
Files
1
Skills in repo
39
Repo updated
First seen
Licence
MIT

At a glance

Initialize or repair an Obsidian wiki vault's required structure and configuration.

  • Works in 6 steps: Create .env → Create Vault Directory Structure → Create Special Files → …
  • New-vault setup
  • SKILL.md covers Step 1: Create .env, Step 2: Create Vault Directory…, Step 3: Create Special Files and Step 4: Create .obsidian…, plus 5 more sections
  • Calls git, curl and python3; reaches github.com

What it does

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.

When your agent uses it

  • New-vault setup
  • .env/config creation
  • Reconfiguration
  • Broken setup recovery

Example prompts

  • “/wiki-setup”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Create .env
  2. Create Vault Directory Structure
  3. Create Special Files
  4. Create .obsidian Configuration
  5. Recommend Obsidian Plugins
  6. Verify Setup

What it can do on your machine

Read from SKILL.md and the folder at commit 0cc5d90. 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:

    • git
    • curl
    • python3

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    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

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.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~3.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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:4
    configuration. Use for new-vault setup, .env/config creation, reconfiguration, or broken setup recovery.
  • NoteMentions a .env fileSKILL.md:11
    ## Step 1: Create .env
  • NoteMentions a .env fileSKILL.md:13
    If `.env` doesn't exist, create it from `.env.example`. Ask the user for:
  • NoteMentions a .env fileSKILL.md:238
    - [ ] `.env` has `OBSIDIAN_VAULT_PATH` set

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 Ar9av/obsidian-wiki at commit 0cc5d90, republished under its MIT licence (© Ar9av). 1,552 words, ~3,720 tokens.

Download SKILL.mdSave it as .claude/skills/wiki-setup/SKILL.md (or your agent's skills folder).
name
wiki-setup
description
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.

Obsidian Setup — Vault Initialization

You are setting up a new Obsidian wiki vault (or repairing an existing one).

Step 1: Create .env

If .env doesn't exist, create it from .env.example. Ask the user for:

  1. Where should the vault live? → OBSIDIAN_VAULT_PATH

    • Default: ~/Documents/obsidian-wiki-vault
    • Must be an absolute path (after expansion)
  2. Where are your source documents? → OBSIDIAN_SOURCES_DIR

    • Can be multiple paths, comma-separated
    • Default: ~/Documents
    • Local git repo clones (public or private, any host) can be listed here too — clone the repo locally first, then add its path. See "Ingesting Git Repositories" in wiki-ingest/SKILL.md for how repo sources are handled.
  3. Want to import Claude history? → CLAUDE_HISTORY_PATH

    • Default: auto-discovers from ~/.claude
    • Set explicitly if Claude data is elsewhere
  4. Have QMD installed? → QMD_WIKI_COLLECTION / QMD_PAPERS_COLLECTION / QMD_TRANSPORT

    • Optional. Enables semantic search in wiki-query and source discovery in wiki-ingest.
    • Default to QMD_TRANSPORT=mcp unless the user wants the agent to call the local qmd CLI directly.
    • If using CLI mode, set QMD_CLI_SEARCH_MODE=quality by default; suggest balanced if reranking is too slow.
    • If unsure, skip for now — both skills fall back to Grep automatically.
    • Install instructions: see .env.example (QMD section).
    • If 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.
  5. Token budget warning threshold? → WIKI_TOKEN_WARN_THRESHOLD

    • Default: 100000 (warn when full-wiki read would cost > 100K tokens)
    • Set to 0 to disable the warning entirely
    • wiki-status shows a token footprint table and emits this warning automatically
  6. Enable staged writes? → WIKI_STAGED_WRITES

    • Default: unset / false (pages written directly to their final location)
    • Set to true for team wikis, high-stakes domains, or any vault where the human wants final say on every LLM-written page
    • When enabled: all new/updated pages land in _staging/ first; run /wiki-stage-commit to review and promote them
    • wiki-status shows a "Staged writes pending" count when files are waiting

After 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:

  • Packaged install: <root>/skills/llm-wiki/references/WRITING.md
  • Source checkout: <root>/.skills/llm-wiki/references/WRITING.md
bash
GLOBAL_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"
fi

Step 2: Create Vault Directory Structure

bash
mkdir -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.

Step 3: Create Special Files

index.md
markdown
---
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
log.md
markdown
---
title: Wiki Log
---

# Wiki Log

- [TIMESTAMP] INIT vault_path="OBSIDIAN_VAULT_PATH" categories=concepts,entities,skills,references,synthesis,journal
hot.md
markdown
---
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.*
.manifest.json

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):

bash
printf '{}\n' > "$OBSIDIAN_VAULT_PATH/.manifest.json"

Step 4: Create .obsidian Configuration

Create minimal Obsidian config for a good out-of-box experience:

.obsidian/app.json
json
{
  "strictLineBreaks": false,
  "showFrontmatter": false,
  "defaultViewMode": "preview",
  "livePreview": true
}
.obsidian/appearance.json
json
{
  "baseFontSize": 16
}

Step 5: Recommend Obsidian Plugins

Tell the user about these recommended community plugins (they install manually):

  1. Dataview — Query page metadata, create dynamic tables. Essential for a wiki.
  2. Graph Analysis — Enhanced graph view for exploring connections.
  3. Templater — If they want to create pages manually using templates.
  4. Obsidian Git — Auto-backup the vault to a git repo.

Step 6: Verify Setup

Run a quick sanity check:

  • Vault directory exists with: concepts/, entities/, skills/, references/, synthesis/, journal/, projects/, _archives/, _raw/
  • index.md exists at vault root
  • log.md exists at vault root
  • hot.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 directory
  • Source directories (if configured) exist and are readable

Report the results, including the resolved absolute WRITING_PROFILE path, and tell the user they can now:

  1. Open the vault in Obsidian (File → Open Vault → select the directory)
  2. Run wiki-status to see what's available to ingest
  3. Run wiki-ingest to add their first sources
  4. Run claude-history-ingest to mine their Claude conversations
  5. Run codex-history-ingest to mine their Codex sessions (if they use Codex)
  6. Run wiki-status again anytime to check the delta
Show full SKILL.md (702 more words)Show less

Optional: Install the Stop Hook (Auto-Capture)

Ask 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:

  1. 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.

  2. 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):

    bash
    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.

  3. Merge the hook entry into ~/.claude/settings.json:

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.json registering 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.

  1. Confirm: "Stop hook installed. Claude Code will prompt /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).

Optional: Configure GitHub Sync

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:

  1. Ask for the repo URL (e.g. https://github.com/you/my-wiki.git). Recommend it be private if the vault holds personal notes.
  2. Run the CLI, which handles 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):
    bash
    obsidian-wiki sync-setup "<repo-url>" --vault "$OBSIDIAN_VAULT_PATH"
    If the 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.
  3. Tell the user they can run 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.

Optional: Refresh QMD After Setup

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

Files

Just SKILL.md in .skills/wiki-setup of Ar9av/obsidian-wiki.

Open the folder on GitHubat commit 0cc5d90

Compare with similar skills

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.

Wiki Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wiki Setup this skillAr9av/obsidian-wiki3.5k—~3.7kAutomated safety check: NotesMIT
LLM Wikilewislulu/llm-wiki-skill655—~3.7kAutomated safety check: PassNone
LLM Wikizosmaai/pi-llm-wiki605—~4.4kAutomated safety check: PassMIT
LLM Wikipraneybehl/llm-wiki-plugin117—~5.7kAutomated safety check: PassMIT
Karpathy WikiSherwinQ/karpathy-wiki113—~967Automated safety check: PassMIT
My LLM WikiMartinLwx/dotfiles140—~2.7kAutomated safety check: PassNone

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
  • LLM Wiki

    zosmaai/pi-llm-wiki

    Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern.

    605 GitHub stars~4.4k tokensUpdated yesterday
    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 25 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 18 days ago
    Knowledge ManagementAuto-check passed
  • Sage Wiki

    xoai/sage-wiki

    Reference skill for sage-wiki — local-first knowledge graph with MCP server, REST API, compiled wiki, and Obsidian-compatible output.

    620 GitHub stars~2.4k tokensUpdated yesterday
    Knowledge ManagementAuto-check passed

More from Ar9av/obsidian-wiki

All 39 skills in this repo
  • Hermes History Ingest

    Ar9av/obsidian-wiki

    Ingest Hermes agent history into Obsidian as distilled knowledge.

    3.5k GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check: notes
  • Codex History Ingest

    Ar9av/obsidian-wiki

    Ingest Codex CLI conversation/session history into Obsidian as distilled knowledge.

    3.5k GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Copilot History Ingest

    Ar9av/obsidian-wiki

    Ingest GitHub Copilot CLI/session history into Obsidian as distilled knowledge.

    3.5k GitHub stars~4.4k tokensUpdated yesterday
    Auto-check: notes
  • Obsidian Layout Adjustment

    Ar9av/obsidian-wiki

    Adjust the user's Obsidian visual layout with CSS snippets. An agent skill from Ar9av/obsidian-wiki.

    3.5k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Openclaw History Ingest

    Ar9av/obsidian-wiki

    Ingest OpenClaw session/history data into Obsidian as distilled knowledge.

    3.5k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check: notes
  • Wiki Capture

    Ar9av/obsidian-wiki

    Turn the current conversation or finding into a structured permanent wiki note.

    3.5k GitHub stars~4.3k tokensUpdated yesterday
    Auto-check: notes

Works with

Questions about Wiki Setup

What does Wiki Setup do?

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.

When should I use Wiki Setup?

Wiki Setup fits situations like: new-vault setup; .env/config creation; reconfiguration; broken setup recovery.

How do I install Wiki Setup in Claude Code?

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.

How do I install Wiki Setup in Codex?

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.

Can I use Wiki 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 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.

What does Wiki Setup need to run?

Going by SKILL.md and its folder, Wiki Setup needs the command-line tools its instructions call (git, curl and python3).

Does Wiki Setup access the network?

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.

Is Wiki Setup safe to install?

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.

What licence does Wiki Setup use?

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.

How many tokens does Wiki Setup use?

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.

What are the alternatives to Wiki Setup?

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.

Who maintains Wiki Setup?

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.