wiki-lint

Detect broken wiki links, orphans, duplicate slugs, and index drift in federated markdown knowledge bases.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/Walliiee/agent-harness --skill wiki-lint-walliiee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-lint
Source: https://github.com/Walliiee/agent-harness/tree/main/skills/wiki-lint
Command: npx skills add https://github.com/Walliiee/agent-harness --skill wiki-lint-walliiee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill catches cross-page wiki problems that are easy to miss by hand: dangling links, orphan pages, duplicate slugs, and index drift. It helps keep large federated knowledge bases navigable, honest, and low-friction to maintain.

Core Features & Use Cases

  • Dangling link detection: Identifies unresolved wiki links and ranks them by how many pages already point to them, showing which pages are worth writing next.
  • Orphan and duplicate analysis: Finds pages with no inbound links, pages missing from indexes, and duplicate slugs that create ambiguous references.
  • Health reporting and targeted checks: Produces summary, JSON, and detailed reports, and can check a single file’s unresolved links before a page is considered done.
  • Deterministic repair support: Can automatically repoint known broken reference prefixes to existing pages when safe, while leaving judgment calls to the user.

Quick Start

Run the wiki-lint skill against your workspace wiki to get a ranked report of dangling links, orphans, duplicate slugs, and index drift.

Frequently Asked Questions about wiki-lint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find broken markdown wiki links and orphan pages in my workspace?

To find broken markdown wiki links and orphan pages, run a link integrity check that parses markdown, reads frontmatter, and resolves global slugs to detect dangling references, duplicate slugs, and index drift. This produces a ranked report of unresolved wiki links.

What is index drift in a federated knowledge base and how do I detect it?

Index drift in a federated knowledge base occurs when pages are missing from indexes or have ambiguous references due to duplicate slugs. You detect index drift by running deterministic markdown parsing and global slug resolution to generate a consistency report.

How do I check a single markdown file for unresolved wiki links before publishing?

You can check a single markdown file for unresolved wiki links by running a targeted file-specific validation. This analyzes the page's references before it is considered done, ensuring no dangling links are introduced to the workspace wiki.

Can I automatically repoint broken wiki links to existing pages?

Yes, you can automatically repoint broken wiki links to existing pages using deterministic repair support. This safely repoints known broken reference prefixes while leaving ambiguous judgment calls to the user.

How do I know which missing wiki pages are worth writing next?

You can identify which missing wiki pages are worth writing next by analyzing dangling link detection reports. These reports rank unresolved wiki links by how many pages already point to them, highlighting the highest demand topics.

Does wiki link linting work for federated markdown knowledge bases?

Yes, wiki link linting works for federated markdown knowledge bases. It applies deterministic markdown parsing and global slug resolution across multiple workspaces to detect cross-page problems like orphans and dangling links.