wiki-lint
Has your agent check the health of the LLM Wiki. It looks for errors, broken links, or information that doesn't make sense.
What it does
This tool checks if the information in a knowledge base (wiki) is correct and organized. It looks for errors like contradictory information, broken links, or pages not connected to others.
When to use it
- ✓When you suspect there is incorrect or outdated information in a wiki.
- ✓Before making major changes to a wiki to understand existing issues.
- ✓To ensure all important links and pages are working correctly.
Example of what to ask your AI
“Check the 'Project Alpha' wiki for inconsistencies and broken links.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool reads all wiki pages and compares the information. It looks for specific problems like links that don't go anywhere or conflicting information.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add paperclipai/paperclip --skill wiki-lintOr download just the file:
curl -L https://raw.githubusercontent.com/paperclipai/paperclip/master/packages/plugins/plugin-llm-wiki/skills/wiki-lint/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Wiki Lint
Audit, do not edit. Return findings the maintainer (human or agent) can triage.
Inputs
- An operation issue with
operationType: "lint". - The operation issue's target
wikiId,spaceSlug, and space root. Lint only that space unless the issue explicitly says this is a multi-space sweep.
Workflow
- Walk the target space's
wiki/index.mdand wiki tree withwiki_searchandwiki_read_page, always passing the operation issue'swikiIdandspaceSlug. Build a mental map of: pages that exist, pages referenced fromindex.md, pages referenced from other pages, and raw sources. - Check for the seven recurring issues, in this order:
- Contradictions — two pages making incompatible claims about the same entity, decision, or status. Flag both pages, name the conflicting claims, and quote evidence.
- Stale claims — a page asserts X, but a newer source under
raw/has superseded it. Flag the older page; never overwrite. - Orphan pages — a
wiki/page is not linked fromindex.mdand not referenced from any other wiki page. Either it should be linked, removed, or merged. - Concept gaps — a term appears on three or more pages but has no dedicated
wiki/concepts/<slug>.md. Recommend creating one. - Broken
[[wiki-links]]— a link target file does not exist. - Weak provenance — a non-trivial claim is uncited or cites only the wiki itself in a circle. The original source ref should be findable.
- Index / log drift — pages exist that are not in
index.md, orindex.mdlists pages that no longer exist. Recent operations inwiki/log.mdthat did not produce a corresponding page change.
- Return a triage list, grouped by severity:
- critical: contradictions, broken links to active pages, fabricated citations.
- medium: stale claims, weak provenance, large concept gaps.
- low: orphans, log drift, small index gaps.
Each item has: file path, evidence (a 1–2 line quote), suggested fix, and the operation that should follow up (
ingest,paperclip-distill,index-refresh, manual review).
- Do not write to
wiki/. Lint is read-only by design — the maintainer or the routine that follows decides which findings to act on. - Append a log entry describing the run:
## [YYYY-MM-DD] lint | <N findings, M critical> - operation issue: <issue identifier> - critical: <count> - medium: <count> - low: <count>
Voice
- Lead with the count by severity.
- Each finding is one bullet. Resist commentary.
- When in doubt about severity, say so and surface it as medium with a "verify" note.
Verification
Before closing the operation issue:
- Findings are grouped by severity with file paths, evidence, and suggested fix per item.
- No files under
raw/were modified. No files underwiki/were modified exceptwiki/log.md. - If the run found nothing, the issue is closed with "no findings" and the log entry still exists so future audits can see this run happened.
Tools
wiki_search, wiki_read_page, wiki_list_sources, wiki_read_source, wiki_write_page (only wiki/log.md). Always include the operation issue's wikiId and spaceSlug.
FAQ
Does the tool fix the problems automatically?
No, it only points out the issues found. A human or another AI agent needs to review and fix the errors.
What are 'orphan pages'?
These are pages that exist in the wiki but are not mentioned or linked from any other page, making them hard to find.
What does 'weak provenance' mean?
It means an important piece of information lacks a clear or reliable source cited, or the source is the wiki itself, creating a loop.
Details
Original description by the author
Use when an LLM Wiki operation issue is a lint or health check. Audit for contradictions, orphans, weak provenance, broken links, missing concept pages, and index/log drift; return triage findings without auto-fixing.
repo: paperclipai/paperclip
Popularity
- GitHub stars
- 103k
- Ranking position
- #372
- License
- MIT
- Updated
- 10/16/2026
Comments
- …
More skills from this repository
delegate-work
Helps your agent delegate work to another agent. It's useful for breaking down complex tasks and tracking progress in an organized way.
paperclipai/paperclip
follow-up-results
Has your agent check results from previous work. It's useful for tracking task progress and adding human feedback.
paperclipai/paperclip
review-my-team
Helps your agent review the connected team. It's useful for getting a summary of the team, tasks, blockers, and pending approvals.
paperclipai/paperclip
paperclip-task-bridge
Has your agent create and manage tasks on another platform. It's useful for interacting with project management systems directly.
paperclipai/paperclip
Similar skills
architecture-decision-records
Has your agent record important project structure decisions. It helps to understand the reasoning behind choices and maintain a clear history of changes.
affaan-m/ECC
code-tour
Lets your agent create step-by-step code walkthroughs with exact file and line anchors. It's useful for project introductions, code explanations, or change reviews. Helps understand how a system works.
affaan-m/ECC
codebase-onboarding
Helps your agent analyze unfamiliar code and create an onboarding guide. It includes an architecture map, entry points, and conventions. Ideal for starting on a new project.
affaan-m/ECC