agentleFS
VladTheProgrammerVladTheProgrammer/claude-asimov/.claude/skills/wiki-lint/SKILL.md

wiki-lint

Skill0 starsChanged 4 months agoMITView on GitHub

Health-check the wiki — contradictions, orphan pages, dangling/stale [[links]], missing index entries. Writes a dated report. Usage: /wiki-lint

43 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use wiki-status, cross-linker and 9 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.
  • 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

  • bozhouDevSkill

    wiki-update

    Use when revising existing wiki pages because knowledge has changed, a new piece of information updates or contradicts existing content, or the user wants to directly edit wiki content with LLM assistance.

    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

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read wiki/SCHEMA.md for the conventions being checked.

    line 6
  2. Very specific:

    Write wiki/_lint-YYYY-MM-DD.md with the findings grouped by check, each with the file(s) and a one-line fix suggestion.

    line 28

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

Read wiki/SCHEMA.md for the conventions being checked.

Scan every page under wiki/ (excluding raw/, which is immutable and not linted for content). Report, do not silently fix — surface findings and let the user choose what to repair.

Checks

  1. Frontmatter integrity — every page has the required fields (title, type, created, updated, confidence); type matches the directory it lives in.
  2. Dangling links — every [[slug]] resolves to an existing page. List the broken ones and where they appear.
  3. Orphans — pages with no incoming [[links]] (unreachable knowledge). List them.
  4. Missing concepts — concepts referenced in prose but with no page yet. List them as fill candidates.
  5. Index drift — every page appears in wiki/index.md under the correct type; no index entries point to deleted pages.
  6. Source traces — concept/entity key facts cite a sources: entry; flag unsourced claims.
  7. Contradictions — pages making conflicting claims about the same thing. List the pair + the conflict.
  8. Stale claims — pages whose updated: is old and whose sources: have since been superseded by a newer source page. Flag for review.

Output

Write wiki/_lint-YYYY-MM-DD.md with the findings grouped by check, each with the file(s) and a one-line fix suggestion. Append a line to wiki/log.md: YYYY-MM-DD | lint | _lint-YYYY-MM-DD.md | {N findings}. Summarize the top issues to the user.

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.