Indexion Wiki

This teaches Claude how to maintain a project wiki that lives in `.indexion/wiki/` as Markdown files with a JSON manifest. The key insight is that each wiki page is actually four synchronized artifacts (content, manifest entry, search index, and audit log), so editing a .md file directly leaves the other three stale. The skill walks through the complete lifecycle: creating pages with proper provenance tracking, detecting stale pages when source files change via `ingest`, running structural checks with `lint`, and catching semantic drift with `plan reconcile` to find when code symbols described in docs no longer match reality. You'd use this if you're maintaining technical documentation as code and need to keep it synchronized with an evolving codebase.

skills.sh installs: 4.9K
GitHub stars: 2
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add trkbt10/indexion-skills --skill indexion-wiki --agent claude-code

Installs into .claude/skills of the current project.

Files

indexion wiki

indexion's wiki system maintains a knowledge base at .indexion/wiki/ as a collection of Markdown files governed by a wiki.json manifest.

A wiki page is not just a `.md` file

A wiki page consists of four synchronized artifacts:

Artifact	File	Updated by
Page content	`<id>.md`	`wiki pages add`, `wiki pages update`
Manifest entry	`wiki.json`	`wiki pages add`, `wiki pages update`
Search index	`vectors.db`, `search-sections.json`, `tfidf-vocabulary.json`	`wiki pages update`, `wiki index build --full`
Audit log	`log.json`	Every wiki-modifying command

wiki pages update updates all four at once. Editing the .md file directly updates only the first. The other three become stale — search returns old results, the manifest carries wrong provenance, and the log has no record of the change.

If you edit a .md directly (e.g. via Edit tool), you must immediately follow up:

SKILL.md on GitHub