How do I install the Kb Lint skill?

Run npx skillmds@latest add chendaiwei-99/kb-lint in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kb Lint safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kb Lint?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kb Lint free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kb Lint?

ChenDaiwei-99 (@chendaiwei-99) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kb Lint by chendaiwei-99 — Agent Skill

Name: Kb Lint
Rating: 4.666666666666667 (3 reviews)
Author: ChenDaiwei-99

Kb Lint

Audit an Obsidian LLM knowledge base and personal note space for structure, links, stale summaries, duplicate concepts, weak citations, unresolved contradictions, project-note consistency, and human/agent ownership violations. Use when checking workspace health, reviewing whether personal notes and sources are consistent, preparing cleanup work, or finding issues that should be added to knowledge-base/wiki/review.md.

ChenDaiwei-99 Updated Sep 22, 2026

File contents

KB Lint

Use this skill to inspect knowledge-base health without making risky rewrites.

Workflow

Read the vault root AGENTS.md.
Confirm the expected folders and control files exist.
Check human-owned personal-notes/ for schema drift only; do not edit them during lint.
Check raw-source records for required frontmatter, required body sections, preserved links, and source locators.
Check wiki pages for citations back to raw-source records or human notes.
Search for duplicate concepts, orphan synthesis pages, broken wikilinks, and missing backlinks.
Identify contradictions or stale claims and route them to knowledge-base/wiki/review.md.
Produce a prioritized report with concrete file paths and suggested fixes.

Checks

Use lint-checks.md for the full checklist.

Fix Policy

Apply low-risk mechanical fixes in the knowledge base only when the user asks for direct cleanup.
Apply personal-notes/ link/frontmatter formatting fixes directly when they are low-risk.
For substantive personal-notes/ fixes, list exact proposed changes and ask for permission before editing.
Do not rewrite personal notes by default.
Do not resolve contradictory claims automatically.
Prefer review items over silent changes when evidence is ambiguous.

Output

Group findings by severity:

Critical: broken schema, missing raw-source records, or ownership violations.
High: contradictions, missing citations, or important dead links.
Medium: duplicate concepts, orphan wiki pages, weak summaries.
Low: naming drift, minor frontmatter gaps, index freshness.

---name: kb-lintdescription: Audit an Obsidian LLM knowledge base and personal note space for structure, links, stale summaries, duplicate concepts, weak citations, unresolved contradictions, project-note consistency, and human/agent ownership violations. Use when checking workspace health, reviewing whether personal notes and sources are consistent, preparing cleanup work, or finding issues that should be added to knowledge-base/wiki/review.md.---# KB LintUse this skill to inspect knowledge-base health without making risky rewrites.## Workflow1. Read the vault root `AGENTS.md`.2. Confirm the expected folders and control files exist.3. Check human-owned `personal-notes/` for schema drift only; do not edit them during lint.4. Check raw-source records for required frontmatter, required body sections, preserved links, and source locators.5. Check wiki pages for citations back to raw-source records or human notes.6. Search for duplicate concepts, orphan synthesis pages, broken wikilinks, and missing backlinks.7. Identify contradictions or stale claims and route them to `knowledge-base/wiki/review.md`.8. Produce a prioritized report with concrete file paths and suggested fixes.## ChecksUse [lint-checks.md](references/lint-checks.md) for the full checklist.## Fix Policy- Apply low-risk mechanical fixes in the knowledge base only when the user asks for direct cleanup.- Apply `personal-notes/` link/frontmatter formatting fixes directly when they are low-risk.- For substantive `personal-notes/` fixes, list exact proposed changes and ask for permission before editing.- Do not rewrite personal notes by default.- Do not resolve contradictory claims automatically.- Prefer review items over silent changes when evidence is ambiguous.## OutputGroup findings by severity:- `Critical`: broken schema, missing raw-source records, or ownership violations.- `High`: contradictions, missing citations, or important dead links.- `Medium`: duplicate concepts, orphan wiki pages, weak summaries.- `Low`: naming drift, minor frontmatter gaps, index freshness.

Frequently asked questions