agentleFS
Ivy-Chen1999Ivy-Chen1999/llm-wiki-kit/skills/wiki-setup/SKILL.md

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
  1. Very specific:

    If .env doesn't exist, create it from .env.example.

    line 17
  2. Distinctive:

    Must be an absolute path (after expansion)

    line 21
  3. Very specific:

    Default: auto-discovers from ~/.claude

    line 28
  4. Very specific:

    If unsure, skip for now — both skills fall back to Grep automatically.

    line 33
  5. Distinctive:

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

    line 118
  6. Distinctive:

    Run a quick sanity check:

    line 148
  7. Very specific:

    Run wiki-status to see what's available to ingest

    line 159
  8. Very specific:

    Run wiki-ingest to add their first sources

    line 160
  9. Very specific:

    Run claude-history-ingest to mine their Claude conversations

    line 161
  10. Very specific:

    Run codex-history-ingest to mine their Codex sessions (if they use Codex)

    line 162
  11. Very specific:

    Run wiki-status again anytime to check the delta

    line 163

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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
  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
    • Optional. Enables semantic search in wiki-query and source discovery in wiki-ingest.
    • If unsure, skip for now — both skills fall back to Grep automatically.
    • Install instructions: see .env.example (QMD section).

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-ingest will 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

## Journal

log.md

---
title: Wiki Log
---

# Wiki Log

- [TIMESTAMP] INIT vault_path="OBSIDIAN_VAULT_PATH" categories=concepts,entities,skills,references,synthesis,journal

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

  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
  • .env has OBSIDIAN_VAULT_PATH set
  • .obsidian/ directory exists
  • Source directories (if configured) exist and are readable

Report the results 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.