菜单
Update Knowledge Base indexes. Smart mode detects changes and updates only what's needed. Full rebuild available with --full flag. Use after adding/moving documents or when indexes feel stale.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | kb-index |
| description | Update Knowledge Base indexes. Smart mode detects changes and updates only what's needed. Full rebuild available with --full flag. Use after adding/moving documents or when indexes feel stale. |
Update indexes efficiently. By default, detects what changed and updates only affected entries. Full rebuild available when needed.
/kb-index # Smart update (diff-based, fast)
/kb-index --full # Full rebuild (scan everything)
/kb-index --category Projects # Update one category only
/kb-index --dry-run # Preview changes without writing
Choose the lightest approach that fits the situation:
When: A single file was ingested or moved. How: kb-ingest already handles this — adds one line to _index.md, updates counts. No need to run kb-index separately.
When: A few files changed, or "something feels off." How: Compare existing _index.md entries against actual files on disk. Only process differences.
When: Major reorganization, initial setup, or indexes are badly corrupted. How: Scan everything from scratch, regenerate all indexes.
This is the default behavior when you run /kb-index.
Step 1: READ existing indexes (cheap — ~200 tokens total)
Read top-level index.md (~30 lines)
Read PARA category _index.md files
If a changed file is inside a project folder and that folder has _index.md, read that project hub too
Extract: listed items, counts, last updated date
Step 2: DETECT changes (cheap — tool calls only, no file reads)
For each PARA category:
Glob: list current subdirectories and .md files on disk
Compare against items listed in _index.md
Classify each item:
MATCH — in index AND on disk → skip (no action)
ADDED — on disk but NOT in index → needs adding
REMOVED — in index but NOT on disk → needs removing
If zero differences found:
Log "[date] index | no changes detected" → done
Total cost: ~200 tokens (just reading indexes + globs)
Step 3: PROCESS only differences
For ADDED items only:
Read the new file's overview/frontmatter (~50-100 tokens per file)
Generate one-line index entry
For REMOVED items:
Delete the line from _index.md
Skip MATCH items entirely — don't re-read, don't regenerate
Step 4: UPDATE indexes
Edit (not rewrite) each affected _index.md:
Insert new entries, remove deleted entries
Update summary count line
Update "updated: {today}" in frontmatter
Update top-level index.md:
Adjust category counts
Update Recent Activity from log.md (last 5 entries)
If a changed file is inside a project folder that has _index.md:
Update the project hub, especially its local document list and updated date
Step 5: LOG
"[date] index-update | added N, removed M | touched K categories"
| Scenario | Tokens | Why |
|---|---|---|
| Nothing changed | ~200 | Read top/category indexes + globs |
| 1 file added | ~350 | Above + read 1 overview and affected project hub if present |
| 3 files added, 1 removed | ~600 | Above + read 3 overviews |
| 10+ files changed | ~1500 | Consider --full instead |
| Major reorg (--full) | ~3-4K | Full vault scan |
Only runs with --full flag. Rebuild category indexes and project hubs from disk state:
1. SCAN each PARA directory
Projects/: list subdirs, read overview files and existing project hubs, extract status
Areas/: list subdirs, count files, extract topics
Resources/: list subdirs, count files
Archive/: count completed vs paused
2. GENERATE _index.md per category (from scratch)
---
title: {Category} Index
type: kb-index
updated: {today}
---
# {Category Name}
{Summary line}
- **[[item]]** — description
...
Rules:
- Maintain the standard entry points: `0. Common/index.md` and four PARA category `_index.md` files.
- Project hubs at `1. Projects/<slug>/_index.md` are supported when a vault uses project-level entrypoints for larger project folders. Do not force-create them in vaults that do not use this pattern.
- Do not create arbitrary sub-folder `_index.md` files outside supported project hubs. Group lower-level folders inside the nearest category index or project hub section.
- **Link to overview files directly** when present: `[[0. <project> 프로젝트 개요|<project>]]` rather than the folder name alone — prevents project overview files from showing up as orphans.
- Active/important items first, then alphabetical
- `[[wikilinks]]` for all references
3. GENERATE top-level index.md (from scratch)
Aggregate categories + last 5 log entries
Target: ~30 lines
Rules:
- **Each PARA section header is a wikilink to its category `_index`**, e.g.:
## [[1. Projects/_index|Projects]]
## [[2. Areas/_index|Areas]]
This is critical: without this, the four PARA `_index.md` files themselves show up as orphans in `obsidian orphans`. Header-as-wikilink resolves all four naturally.
- One-line summary per section (counts + key categories or active items)
4. LOG
"[date] index-rebuild | N categories | M total entries"
# Glob disk state
disk_items = Glob("1. Projects/*/") + Glob("1. Projects/*.md")
# Parse existing index
index_items = extract_entries_from("1. Projects/_index.md")
# Diff
added = disk_items - index_items
removed = index_items - disk_items
1. Projects/ (each project is a folder)1. Projects/<slug>/, excluding _index.md and _log.md unless the hub intentionally links logsStandalone .md files in a category root are also tracked when the vault uses them.
If diff detects >30% items changed, suggest: "Many changes detected. Rebuild with --full?"
When obsidian is available:
# Find all index files — `obsidian search` is full-text only, so use grep on frontmatter
grep -rln "^type: kb-index" . --include="*.md"
# Or inspect frontmatter properties broadly
obsidian properties
# Tag inventory for index enrichment (vault tag conventions)
obsidian tags
| Argument | Effect |
|---|---|
| (default) | Smart diff update — only process changes |
--full | Full rebuild from scratch |
--category <name> | Limit to: Projects, Areas, Resources, or Archive |
--dry-run | Show what would change without writing |
"added one file" (파일 하나 추가했어) → /kb-ingest already handled it (Tier 1)
"a few things changed" (몇개 바뀐 것 같은데) → /kb-index (Tier 2, default)
"major folder restructure" (폴더 구조 대폭 변경) → /kb-index --full (Tier 3)
"not sure if index is correct" (인덱스가 맞는지) → /kb-lint first, then /kb-lint --fix if needed
Ingest documents into the PARA Knowledge Base. Classifies, moves, links, and indexes new documents from Inbox or a specified path. Use when new documents need processing into the vault.
Initialize PARA Knowledge Base in your Obsidian vault. Creates index files, log, and adds KB rules to CLAUDE.md. Run this first before using other kb- skills.
Health check for the PARA Knowledge Base. Detects orphan documents, broken links, index drift, tag issues, and stale content. Run periodically or as part of weekly review.
Query the PARA Knowledge Base to find information, synthesize answers from vault documents, inspect recent activity when needed, and record compact query telemetry when configured. Use for any question about Obsidian vault content, projects, references, logs, links, or cross-document analysis.