From obsidian-wiki
Use when the user asks to refresh, rebuild, or regenerate Home.md in their Obsidian vault, mentions "/vault-rebuild-home", or notices that Home.md has drifted from the actual files on disk. Trigger on "rebuild the index", "refresh Home.md", "Home is out of date", or "the index is stale".
How this skill is triggered — by the user, by Claude, or both
Slash command
/obsidian-wiki:vault-home-rebuildThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Regenerate the tables in `~/dev/knowledge/Home.md` from the actual filesystem state,
Regenerate the tables in ~/dev/knowledge/Home.md from the actual filesystem state,
catching drift caused by manual page additions, renames, or deletions in Obsidian.
Home.md is a hand-curated Map-of-Content. The vault-ingest skill only adds rows
to it; it never removes or reorders. Over time, when the user creates pages directly in
Obsidian (or deletes them), Home.md falls out of sync. This skill catches that.
This skill is destructive — it rewrites parts of Home.md. It always produces a
diff first and waits for confirmation before applying.
Read Home.md in full and parse out:
[[Name]].The introduction and narrative content are sacred. Only the table rows are candidates for regeneration.
For each page file under the six category directories:
title, tags, optional summary or first-line
description).Home.md section the page belongs to. Use the page's category
directory plus its tags. The current Home.md shows the precedent — match it.Build a target table for each section, sorted to match the existing order convention (usually alphabetical or grouped by sub-theme).
For each table, compute:
Home.md row says one thing, the page's frontmatter title or summary
says another).Do not auto-reorder existing rows. Drift in row order is not a bug — the user may have ordered rows intentionally.
Show the user, table by table:
## Table: Infrastructure & Networking
### To add (3)
- `[[new-tor-bridge-tool]]` — GPU-accelerated Tor bridge enumeration
- ...
### To remove (1)
- `[[old-deleted-page]]` — page no longer exists on disk
### To change (2)
- `[[caddy]]` — description drift:
- Home.md says: "Auto-HTTPS web server"
- Page title says: "Auto-HTTPS web server + reverse proxy (Go)"
Per-section, ask: "Apply additions? Remove obsolete rows? Update descriptions?" The user answers per category, per operation type. Do not batch into one big yes/no.
For each confirmed change, edit Home.md with the Edit tool. Edit one row at a time
when possible. Never Write the whole file — Edit only.
Order of operations within a single table:
Append to log.md:
## [YYYY-MM-DD] schema | Rebuilt Home.md
- Added: <list of pages>
- Removed: <list of pages>
- Updated: <list of pages>
- Reason: <one-line, e.g. "manual page additions in Obsidian since last sync">
Use type schema because Home.md is part of the vault's structural layer, even
though vault-schema-maintain doesn't touch it. (Alternatively, the user may want to
extend the schema to allow a home type — flag this if it comes up repeatedly.)
Home.md wholesale. Always Edit-by-row.title or first-paragraph summary, not from your own paraphrase of the
body.tor and gotcha). Ask the user where it goes.Home.md — update Home.md to match the page, never
the other way around.Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub sureserverman/obsidian-wiki-plugin --plugin obsidian-wiki