lint-wiki
Skill1 starsChanged 6 months agoMITView on GitHub
Use this skill when the user says "lint", "audit the wiki", "wiki health check", or asks for stale pages, orphans, contradictions, or missing cross-references. This skill audits the wiki for structural and content issues but does NOT auto-fix them — it surfaces findings for the user to confirm before any change is made. Triggers include phrases like "lint", "lint the wiki", "audit", "what needs cleanup", "find orphan pages", or "check for stale content".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- enzobleuze/machine-claudetheir own version, first seen Nov 1, 2026
- HagaiHen/podcast-wikitheir own version, first seen Oct 9, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- HagaiHen/podcast-wiki★ 14same name
- enzobleuze/machine-claude★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ingest-sourceSkill
- save-sessionSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
If no inbound editorial links exist, flag as orphan
- Very specific: line 51
Check whether index.md lists it under any category
- Distinctive: line 78
Look for pages that disagree on facts.
- Distinctive: line 93
Check the target file exists
- Very specific: line 94
Check the link is within wiki/ (no links into raw/)
- Very specific: line 106
Check frontmatter status: against required sections for the page's type: (defined in wiki/_templates/<type>.md)
- Very specific: line 119
Check wiki/plans/ (if it exists) for plans where:
- Very specific: line 133
Check wiki/log.md against the wiki's actual activity:
- Very specific: line 136
If processed/ files significantly outnumber log entries, flag — ingests bypassed the log
- Distinctive: line 161
Run on a schedule or in the background — only when the user invokes it
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Lint the wiki
Trigger
The user explicitly asks for a wiki audit, lint, or health check.
Output format
Produce a single report in chat with sections per check below. Each finding should be actionable — name the file, name the issue, suggest a fix. Do not auto-fix without user confirmation.
Checks to run
1. Stale pages
For every .md file in wiki/:
- Read frontmatter
last_updated - Flag pages where
last_updatedis more than 60 days old - Flag pages with no
last_updatedfield (broken frontmatter)
Report:
Stale pages (last_updated > 60 days):
- wiki/<category>/foo.md — last_updated 2025-12-01
- wiki/bar.md — no last_updated field2. Orphan pages
A page is an orphan if no other wiki page links to it (other than index.md, which links to everything by design). For each .md file:
- Grep all other wiki files for a markdown link pointing to this page
- Ignore inbound links from
index.md— that link is structural, not editorial - If no inbound editorial links exist, flag as orphan
Report:
Orphan pages (no inbound wiki links other than index.md):
- wiki/<category>/foo.md
- wiki/bar.mdOrphans aren't always wrong, but they suggest the page either isn't useful or isn't being discovered through cross-references. Worth reviewing.
3. Missing index entries
For every .md file in wiki/ (excluding _templates/, index.md, log.md):
- Check whether
index.mdlists it under any category - Flag any page not present in the index
Report:
Pages missing from index.md:
- wiki/<category>/foo.md
- wiki/bar.mdA page should be discoverable from index.md. The ingest-source skill is supposed to add the entry; missing entries usually mean a page was created or moved without going through ingest.
4. Concepts mentioned without their own page
Scan for terms that appear repeatedly across wiki pages but lack a dedicated page. Heuristic: any term that appears in 3+ pages and isn't already a page filename.
Report:
Possible missing pages:
- "<term>" — referenced in 4 pages
- "<term>" — referenced in 3 pagesThese are suggestions, not requirements. Some terms don't need their own page.
5. Contradictions
Look for pages that disagree on facts. Specifically:
- Same entity described with different attributes across pages
- Same concept with different definitions
- Pages with
⚠️ Conflict notedcallouts that haven't been resolved
Report:
Contradictions:
- wiki/<page-a>.md and wiki/<page-b>.md disagree on <attribute> for <entity>
- wiki/<page>.md has unresolved conflict callout from 2026-04-126. Broken or weak cross-references
For every markdown link in every wiki page:
- Check the target file exists
- Check the link is within
wiki/(no links intoraw/)
Report:
Broken links:
- wiki/foo.md → ../bar/missing.md (target does not exist)
- wiki/baz.md → /raw/whatever (links into raw/ — should reference the wiki abstraction instead)7. Incomplete pages
For every page in wiki/:
- Check frontmatter
status:against required sections for the page'stype:(defined inwiki/_templates/<type>.md) - Flag pages marked
status: completethat have empty required sections - Flag pages marked
status: draftfor more than 30 days
Report:
Incomplete pages:
- wiki/<category>/foo.md — status=complete but required sections empty
- wiki/<category>/bar.md — status=draft for 45 days8. Plans that should be archived
Check wiki/plans/ (if it exists) for plans where:
status: executedbut file not yet moved towiki/plans/archive/status: rejectedbut file not yet moved towiki/plans/archive/status: activebutlast_updatedis more than 30 days old (likely abandoned)
Report:
Plans to archive or revisit:
- wiki/plans/foo.md — status=executed, should be in archive/
- wiki/plans/bar.md — status=active, last touched 2026-03-01 (45 days)9. Log freshness
Check wiki/log.md against the wiki's actual activity:
- Count
## [YYYY-MM-DD] ingest |entries inlog.md - Count files under
raw/processed/(sources actually ingested) - If
processed/files significantly outnumber log entries, flag — ingests bypassed the log - Find the most recent log entry; if there are recent commits touching
wiki/but the log hasn't been appended to in >30 days, flag
Report:
Log freshness:
- raw/processed/ contains 47 files, wiki/log.md has 12 entries — log appears incomplete
- Latest log entry 2026-02-14, but wiki/ has commits as recent as 2026-04-30 — log may be staleThe log is content-level audit. Skipping log entries breaks the timeline of how the wiki evolved.
After the report
End with one line:
"These are findings, not fixes. Tell me which to act on and I'll address them one at a time."
Then stop. Wait for the user to direct action. Do not auto-fix.
What this skill does NOT do
- Auto-rewrite pages, even for obviously stale content
- Auto-create missing pages — surface the suggestion only
- Auto-archive plans without user confirmation
- Run on a schedule or in the background — only when the user invokes it
- Modify
raw/for any reason
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
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.

