wiki-setup
Skill21 starsChanged 4 months agoMITView on GitHub
Initialize a new Obsidian wiki vault with the correct structure, special files, and configuration. Use this skill when the user wants to set up a new wiki from scratch, initialize the vault structure, create the .env file, or says things like "set up my wiki", "initialize obsidian", "create a new vault", "get started with the wiki". Also use when the user needs to reconfigure their existing vault or fix a broken setup.
- Reads credentials
We split this skill into the rules it gives an agent
11 rules. 0 are common, 3 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
If .env doesn't exist, create it from .env.example.
- Distinctive: line 21
Must be an absolute path (after expansion)
- Very specific: line 28
Default: auto-discovers from ~/.claude
- Very specific: line 33
If unsure, skip for now — both skills fall back to Grep automatically.
- Distinctive: line 118
Create minimal Obsidian config for a good out-of-box experience:
- Distinctive: line 148
Run a quick sanity check:
- Very specific: line 159
Run wiki-status to see what's available to ingest
- Very specific: line 160
Run wiki-ingest to add their first sources
- Very specific: line 161
Run claude-history-ingest to mine their Claude conversations
- Very specific: line 162
Run codex-history-ingest to mine their Codex sessions (if they use Codex)
- Very specific: line 163
Run wiki-status again anytime to check the delta
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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:
- Where should the vault live? →
OBSIDIAN_VAULT_PATH- Default:
~/Documents/obsidian-wiki-vault - Must be an absolute path (after expansion)
- Default:
- Where are your source documents? →
OBSIDIAN_SOURCES_DIR- Can be multiple paths, comma-separated
- Default:
~/Documents
- Want to import Claude history? →
CLAUDE_HISTORY_PATH- Default: auto-discovers from
~/.claude - Set explicitly if Claude data is elsewhere
- Default: auto-discovers from
- Have QMD installed? →
QMD_WIKI_COLLECTION/QMD_PAPERS_COLLECTION- Optional. Enables semantic search in
wiki-queryand source discovery inwiki-ingest. - If unsure, skip for now — both skills fall back to
Grepautomatically. - Install instructions: see
.env.example(QMD section).
- Optional. Enables semantic search in
Step 2: Create Vault Directory Structure
mkdir -p "$OBSIDIAN_VAULT_PATH"/{concepts,entities,skills,references,synthesis,journal,projects,_archives,_raw,.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-ingestwill promote them to proper wiki pages and delete the originals.
Step 3: Create Special Files
index.md
---
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
## Journallog.md
---
title: Wiki Log
---
# Wiki Log
- [TIMESTAMP] INIT vault_path="OBSIDIAN_VAULT_PATH" categories=concepts,entities,skills,references,synthesis,journalhot.md
---
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.*Step 4: Create .obsidian Configuration
Create minimal Obsidian config for a good out-of-box experience:
.obsidian/app.json
{
"strictLineBreaks": false,
"showFrontmatter": false,
"defaultViewMode": "preview",
"livePreview": true
}.obsidian/appearance.json
{
"baseFontSize": 16
}Step 5: Recommend Obsidian Plugins
Tell the user about these recommended community plugins (they install manually):
- Dataview — Query page metadata, create dynamic tables. Essential for a wiki.
- Graph Analysis — Enhanced graph view for exploring connections.
- Templater — If they want to create pages manually using templates.
- 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.mdexists at vault rootlog.mdexists at vault roothot.mdexists at vault root.envhasOBSIDIAN_VAULT_PATHset.obsidian/directory exists- Source directories (if configured) exist and are readable
Report the results and tell the user they can now:
- Open the vault in Obsidian (File → Open Vault → select the directory)
- Run
wiki-statusto see what's available to ingest - Run
wiki-ingestto add their first sources - Run
claude-history-ingestto mine their Claude conversations - Run
codex-history-ingestto mine their Codex sessions (if they use Codex) - Run
wiki-statusagain anytime to check the delta
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- chobizzy/llm-wiki★ 249% same
Wrote their own version · 3
- giovannifrontera/academic-research-prisma-wiki-rag★ 2same name
- dexio-wiki/llm-wiki-skills★ 1same name
- SkinnnyJay/wiki-llm★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- claude-history-ingestSkill
- codex-history-ingestSkill
- cross-linkerSkill
- data-ingestSkill
- graph-colorizeSkill
- ingest-urlSkill
- llm-wikiSkill
- tag-taxonomySkill
- wiki-captureSkill
- wiki-dashboardSkill
- wiki-exportSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-rebuildSkill
- wiki-researchSkill
- wiki-statusSkill
- wiki-synthesizeSkill
- wiki-updateSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

