How do I install the Maintain Wiki skill?

Run npx skillmds@latest add mikeyobrien/maintain-wiki in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Maintain Wiki safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Maintain Wiki?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Maintain Wiki free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Maintain Wiki?

mikeyobrien (@mikeyobrien) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Maintain Wiki by mikeyobrien — Agent Skill

Name: Maintain Wiki
Author: mikeyobrien

Maintain Wiki

Run a deep, whole-wiki health-check and maintenance pass on this OKF wiki. Use when the user asks to lint, clean up, health-check, audit, or maintain the wiki, or periodically after ingesting many sources — to find contradictions, stale claims, orphan pages, missing pages/cross-references, and broken links.

mikeyobrien 25307d1 3.6 KB Updated Sep 17, 2026

File contents

Maintain this wiki

Agent-neutral workflow. okf-init copies this skill into both .agents/skills/maintain-wiki/ (where Codex and other agents that scan .agents/skills/ find it) and .claude/skills/maintain-wiki/ (where Claude Code finds it) — identical copies of the preset's canonical skills/maintain-wiki/. Agents that only read AGENTS.md are pointed here from there.

This vault is an OKF LLM-wiki built by the autowiki autoloop preset. The loop runs an automatic lint as part of its maintenance batch (every 5 merged sources + a final drain pass); THIS is the deep, on-demand, WHOLE-WIKI sweep Karpathy describes ("periodically, ask the LLM to health-check the wiki"). Run it over the whole graph whenever you want a thorough pass between (or after) loop runs.

Knowledge lives in concepts/ (core), summaries/ (per-topic), entities/, comparisons/, the single synthesis.md thesis, and the nav layer index.md / log.md / overview.md.

Health checks (find, then FIX or FLAG)

Sweep the whole wiki for:

Contradictions — pages (or the thesis) asserting conflicting claims. Make the conflict explicit on both sides (name each source + what it says); never silently delete one side.
Stale claims — older claims a newer source superseded. Mark them superseded (link the newer page/claim), don't quietly erase the history.
Orphans — pages with no inbound links. Add a relative link from a sensible related page (or from synthesis.md / a concept hub).
Missing pages — a concept/entity referenced repeatedly but lacking its own page. Add a short stub (proper type + sources:), link it, and flag it to deepen later.
Missing cross-references — clearly-related pages not linked to each other; add both ways.
Broken/loose links — relative links pointing at non-existent files; fix the path.
Wikilinks — any [[…]] Obsidian wikilink: CONVERT to a relative markdown link ([Title](../concepts/name.md)). This vault standardizes on relative md links (the pre-commit hook rejects new [[…]]); never leave wikilinks behind.
Gaps — important sub-topics the wiki barely covers. Suggest sources/questions to fill them (the user can add URLs to the ingest queue, or ask via the query workflow).

Process

Get the lay of the land: read index.md and overview.md, then scan the content folders.
Apply safe fixes (surgical — you're maintaining, not rewriting). Keep every page's non-empty type. Use relative links, not wikilinks.
Refresh overview.md if the wiki's shape has shifted, and the gists in index.md if any are stale.

Log it: PREPEND a maintenance entry to log.md (keep its type: log header):

## [<YYYY-MM-DD>] maintain | full sweep
- fixed: <e.g. 3 contradictions flagged, 2 orphans linked, 1 stub added, 1 broken link>
- flagged: <gaps / things to deepen / sources to add>

Summarize for the user what you changed and what you flagged for them to act on.

Rules

Read/maintain the wiki; don't fetch external sources (that's the ingest pipeline). For filling a gap with a new source, tell the user to add the URL to the ingest queue.
Never edit sources/raw/ or sources/clean/ (immutable provenance).
Relative links, not wikilinks. Keep changes reviewable in one git diff.

---name: maintain-wikidescription: Run a deep, whole-wiki health-check and maintenance pass on this OKF wiki. Use when the user asks to lint, clean up, health-check, audit, or maintain the wiki, or periodically after ingesting many sources — to find contradictions, stale claims, orphan pages, missing pages/cross-references, and broken links.---# Maintain this wikiAgent-neutral workflow. `okf-init` copies this skill into both `.agents/skills/maintain-wiki/`(where Codex and other agents that scan `.agents/skills/` find it) and`.claude/skills/maintain-wiki/` (where Claude Code finds it) — identical copies of the preset'scanonical `skills/maintain-wiki/`. Agents that only read `AGENTS.md` are pointed here from there.This vault is an OKF LLM-wiki built by the `autowiki` autolooppreset. The loop runs an automatic lint as part of its maintenance batch (every 5 mergedsources + a final drain pass); THIS is the deep, on-demand, WHOLE-WIKI sweep Karpathy describes("periodically, ask the LLM to health-check the wiki"). Run it over the whole graph whenever youwant a thorough pass between (or after) loop runs.Knowledge lives in `concepts/` (core), `summaries/` (per-topic), `entities/`, `comparisons/`,the single `synthesis.md` thesis, and the nav layer `index.md` / `log.md` / `overview.md`.## Health checks (find, then FIX or FLAG)Sweep the whole wiki for:- **Contradictions** — pages (or the thesis) asserting conflicting claims. Make the conflict explicit on both sides (name each source + what it says); never silently delete one side.- **Stale claims** — older claims a newer source superseded. Mark them superseded (link the newer page/claim), don't quietly erase the history.- **Orphans** — pages with no inbound links. Add a relative link from a sensible related page (or from `synthesis.md` / a concept hub).- **Missing pages** — a concept/entity referenced repeatedly but lacking its own page. Add a short stub (proper `type` + `sources:`), link it, and flag it to deepen later.- **Missing cross-references** — clearly-related pages not linked to each other; add both ways.- **Broken/loose links** — relative links pointing at non-existent files; fix the path.- **Wikilinks** — any `[[…]]` Obsidian wikilink: CONVERT to a relative markdown link (`[Title](../concepts/name.md)`). This vault standardizes on relative md links (the pre-commit hook rejects new `[[…]]`); never leave wikilinks behind.- **Gaps** — important sub-topics the wiki barely covers. Suggest sources/questions to fill them (the user can add URLs to the ingest queue, or ask via the query workflow).## Process1. Get the lay of the land: read `index.md` and `overview.md`, then scan the content folders.2. Apply safe fixes (surgical — you're maintaining, not rewriting). Keep every page's non-empty `type`. Use relative links, not wikilinks.3. Refresh `overview.md` if the wiki's shape has shifted, and the gists in `index.md` if any are stale.4. Log it: PREPEND a maintenance entry to `log.md` (keep its `type: log` header): ``` ## [<YYYY-MM-DD>] maintain | full sweep - fixed: <e.g. 3 contradictions flagged, 2 orphans linked, 1 stub added, 1 broken link> - flagged: <gaps / things to deepen / sources to add> ```5. Summarize for the user what you changed and what you flagged for them to act on.## Rules- Read/maintain the wiki; don't fetch external sources (that's the ingest pipeline). For filling a gap with a new source, tell the user to add the URL to the ingest queue.- Never edit `sources/raw/` or `sources/clean/` (immutable provenance).- Relative links, not wikilinks. Keep changes reviewable in one git diff.

Frequently asked questions