agentleFS
ggoosenggoosen/Digital-Workforce/.claude/skills/wiki-lint/SKILL.md

wiki-lint

Skill1 starsChanged 4 months agoMITView on GitHub

Health-check your context/ knowledge wiki. Finds contradictions, stale claims, orphan pages, broken/missing cross-references, index drift, and gaps — then fixes the ones you approve. Run it periodically (weekly is good). Voice triggers — "wiki lint", "lint the wiki", "check my context", "wiki health", "is my context stale", "clean up the wiki".

44 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use wiki-capture, wiki-status and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jehrhardtSkill

    wiki-capture

    Quickly capture raw thoughts, links, images, or notes to today's Obsidian daily note from anywhere in Pi. Use when the user wants to jot something down for later wiki processing.

    Also in 6 projects that use this

  • nexuschainsSkill

    wiki-status

    Reports the current state of the wiki vault — page counts, category breakdown, hub pages, orphans, stale entries, and a delta showing what has changed since the last ingest. Use this skill when the operator asks "what's the status", "wiki dashboard", "how many pages", "what's stale", "what's been ingested", "show me the delta", or "wiki health overview". Also surfaces structural insights (top hubs, fragmented clusters, bridge pages) when the operator asks "wiki insights", "what's central", or "show me the hubs". Read-only: this skill reports and recommends; it does not modify any files.

    Also in 5 projects that use this

  • nexuschainsSkill

    cross-linker

    Scans the wiki vault and adds missing [[wikilinks]] between pages that are related but not yet connected. Use this skill when the operator says "link my pages", "find missing links", "cross-reference the wiki", "connect my wiki", "add wikilinks", or after any large ingest to weave new pages into the existing knowledge graph. Also trigger when orphaned pages need connecting or when wiki-lint reports fragmented tag clusters. This is a write-heavy skill — it modifies page files to insert links, unlike wiki-lint which only reports.

    Also in 4 projects that use this

  • Ivy-Chen1999Skill

    wiki-synthesize

    Systematically discover synthesis opportunities across the Obsidian wiki — pairs or clusters of concepts that co-occur frequently across pages but have no synthesis page connecting them. Creates new synthesis/ pages that draw explicit cross-cutting conclusions. Use when the user says "synthesize my wiki", "find connections", "what concepts keep coming up together", "/wiki-synthesize", or after a large ingest when the vault has grown significantly.

    Also in 4 projects that use this

  • Ivy-Chen1999Skill

    wiki-setup

    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.

    Also in 5 projects that use this

  • bozhouDevSkill

    wiki-init

    Use when bootstrapping a new personal wiki for any knowledge domain — research, codebase documentation, reading notes, competitive analysis, or any long-term knowledge accumulation project.

    Also in 7 projects that use this

  • +1 more from nexuschains
  • +4 more from Ivy-Chen1999

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 35 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .claude/WIKI.md, context/index.md, and context/log.md.

    line 26
  2. Very specific:

    Add the approved [[links]].

    line 57
  3. Very specific:

    Lint after big ingests: After a large /sort-knowledge run, lint to catch contradictions the new material introduced.

    line 71

“Common” is measured: kept by at least 6 in 10 of the 35 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

Wiki Lint — keep the knowledge base healthy

Purpose

A wiki rots when nobody maintains the cross-references, contradictions, and stale claims. The whole reason the Living Wiki works (.claude/WIKI.md) is that an LLM can do that maintenance at near-zero cost. This skill is the Lint operation: it audits context/ and fixes what's drifted, so every other employee keeps getting trustworthy context. Catching a stale assumption here prevents a bad decision later.

Operating principles applied

  • The Lint operation of the Living Wiki — the third verb after Ingest and Query (.claude/WIKI.md).
  • Principle 4 (separate planning from execution): propose findings + fixes, get the user's call, then apply. Never silently rewrite their context.
  • Principle 5 (intervention point): contradictions and deletions are the user's call; mechanical fixes (index re-sync, adding obvious links) can be auto-applied if they say so.

Step 1 — Orient

Read .claude/WIKI.md, context/index.md, and context/log.md. Note the last LINT: entry in the log so you can report what's changed since. If index.md / log.md don't exist yet, say so and offer to seed them from the examples (the wiki probably hasn't been used much yet — point the user to /onboard).

Step 2 — Audit (spawn the Wiki Linter)

Spawn the wiki-lint subagent (subagent_type: wiki-lint). It scans every page under context/, builds the [[link]] graph, checks file ages, and returns a structured report grouped by: contradictions · stale claims · orphans · missing cross-refs · broken links · index drift · gaps · provenance gaps, each with a file/quote/date, a proposed fix, and a severity — plus a 1–10 health score and the top 3 fixes.

For a large wiki, you may run several linters over disjoint sections in parallel and merge.

Step 3 — Present findings, get the call (intervention point)

Show the report cleanly: health score, then findings worst-first. For each, give the user a clear choice. Be especially careful with:

  • Contradictions — show both conflicting claims with dates/sources; ask which is current (or whether both should be kept as history). Never auto-resolve.
  • Stale claims — ask whether to refresh, archive, or keep.
  • Deletions / merges — always confirm. Offer a fast path: "apply all the safe mechanical fixes (index re-sync, add the obvious missing links, fix dangling links) and let me decide the rest?"

Step 4 — Apply approved fixes + log

Apply only what the user approved, following the Wiki Contract:

  • Merge/refresh pages under dated headings (never destroy history; move outdated facts to an "Outdated / superseded" note with the date rather than deleting, unless told to delete).
  • Add the approved [[links]]; create missing pages or route to the skill that should (/onboard, /brain-dump, /research-analyst…).
  • Re-sync context/index.md.
  • Append a LINT: line to context/log.md (date via date "+%F %H:%M") noting the health score and what you fixed.

Step 5 — Report

Summarize: before/after health score, what you fixed, what the user deferred, and the gaps that need a skill to fill. Tell them when to lint next.

Pro tips

  • Schedule it. A weekly /wiki-lint keeps drift from accumulating — set it up with Claude Code's /schedule or /loop (when available). Stale context is the silent killer of AI quality.
  • Lint after big ingests. After a large /sort-knowledge run, lint to catch contradictions the new material introduced.
  • The score is a trend, not a grade. Watch it over time via the LINT: lines in context/log.md — rising is good.
  • Gaps are a to-do list. The gaps section tells you exactly what context to capture next to make every employee sharper.

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.