kb-lint
Skill1 starsChanged 39 days agoMITView on GitHub
Audits the knowledge base and, when asked, applies the fixes. Health mode writes a dated lint report (frontmatter, broken links, orphans, stale sources, concept clusters) and edits no page; apply mode fixes what a report found, one category per commit. Use for: lint, audit, health-check, find broken links or orphans (health); apply the lint fixes, fix the broken links, clean up or reorganise from the audit (apply). Not for adding or re-fetching sources (kb-intake, kb-ingest).
3 other projects use a version of this.
Adopted by
Most recently taken up by
- pfeff/claude-skillstheir own version, first seen Nov 1, 2026
- viniciusbedum/vb-ai-contexttheir own version, first seen Sep 25, 2026
- yinqd3/workbuddy-skillstheir own version, first seen Jun 3, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- yinqd3/workbuddy-skills★ 10same name
- pfeff/claude-skills★ 4same name
- viniciusbedum/vb-ai-context★ 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 repository4 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- kb-ingestSkill
- kb-intakeSkill
- kb-querySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Run bash "${CLAUDE_SKILL_DIR}/scan.sh" <vault> <stale-days> (0 when the Instance sets no staleness).
- Distinctive: line 16
check 5: read the densest pages.
- Very specific: line 17
Write wiki/synthesis/lint-YYYY-MM-DD.md (type: synthesis, title: Lint report YYYY-MM-DD).
≈ “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
kb-lint
Two modes. Health (lint, audit, check, find) writes a report and edits no page. Apply (apply, fix, clean up, reorganise) fixes what the latest report found. Vault and staleness come from CLAUDE.md ## Instance.
Health
- Run
bash "${CLAUDE_SKILL_DIR}/scan.sh" <vault> <stale-days>(0 when the Instance sets no staleness). It prints checks 1–4. Its filters exclude known false positives, so use its output rather than your own scans. - Judge what the scan can't:
- each broken link is probable-typo (an existing page name is a near-miss) or pending (a deliberate forward reference, valid by design);
- an unknown type in the histogram (not in the Vocabulary) is a finding;
- check 5: read the densest pages; a term used across ≥3 pages without its own page is a candidate, listed with the pages that use it.
- Write
wiki/synthesis/lint-YYYY-MM-DD.md(type: synthesis,title: Lint report YYYY-MM-DD). Headers exactly## 1. Frontmatter validity,## 2. Broken wikilinks,## 3. Orphan pages,## 4. Stale sources,## 5. Concept clusters without a home. Each finding gives a path and a proposed action; a clean section starts withClean.. Stale living-doc sources are proposed for kb-ingestrefresh <slug>; dated ones are a count. - Log
lint | health-checkwith per-check counts; commit the report and the log only. Health ends at that commit: offer apply, don't start it.
Health never edits a page, even for an obvious typo: list it. Apply's one-category commits are what make each fix revertable.
Apply
Needs the latest wiki/synthesis/lint-*.md (none → run health first) and a vault tree clean apart from raw/curation/ (otherwise stop: a category commit must hold only its own changes).
Per category, in report order and only those the operator chooses: propose the changes in chat, apply them, log refactor | <category> with - Source: wiki/synthesis/lint-YYYY-MM-DD.md, commit.
- Without asking: missing frontmatter fields; slug ≠ stem → fix the
slug:field, never rename the file (inbound links use the stem); a link typo with exactly one near-miss, every occurrence; a skill, tool or command name in[[ ]]→ backticks. - Confirm first: a typo with two or more plausible targets; concept-cluster pages (type from the Vocabulary, index line, citing pages relinked); anything else creative.
- An unknown type is proposed to the operator as a schema update, never silently changed.
- Archive, never delete: move to that folder's
_archive/. - Stale sources are not an apply category: hand them to kb-ingest as
refresh <slug>.
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.

