Wiki Structure Linter
Script-backed structure check for a markdown wiki: broken links and anchors, orphans, name clashes, index drift, bad frontmatter.
Before & after
Same prompt, same agent — the only difference is the skill.
I can review your wiki for common issues. What kind of consistency are you targeting? Are you looking at page templates, heading structure, formatting standards, navigation clarity, or something else? I could also check for things like broken links, outdated information, or missing sections. Do you have existing style guidelines? It would help to know what the current state is and what your ideal outcome looks like before I provide feedback.
Runs STRUCTURAL AUDIT: page hierarchy, orphaned articles, missing parent links. TEMPLATE COMPLIANCE: heading levels, required sections per page type. FORMATTING SCAN: inconsistent bullet styles, bold/italic misuse. LINK INTEGRITY: broken internal references, redirect chains. CONTENT STALENESS: dates, version numbers, outdated examples. NAVIGATION MAP: breadcrumb gaps, missing sidebar entries. Returns a REPAIR CHECKLIST with critical issues first, estimated time per fix, and diff-style view of suggested edits. Activates automatically when the request matches wiki-lint.
About this skill
Find every broken link, unreachable page, and malformed file in your wiki with a script instead of guesswork. Findings come with exact fixes, ranked by severity.
What it does
- Runs a bundled Python check for broken wikilinks, filename clashes (including case-only), and orphans, ignoring code blocks
- Checks heading anchors, index drift, frontmatter validity, and supersession links
- Finds raw files never ingested and source pages whose raw file is missing
- Verifies the log is well-formed and append-only
- Applies only safe mechanical fixes, with approval, and hands restructures to the Librarian
What you get
A lint report with blockers, should-fix items, and nits, each with the file and the fix, plus real script output and a log entry.
Best for
Obsidian and markdown wiki maintainers after renames or imports, and before publishing or re-indexing a knowledge base.
SKILL.md preview
---
name: wiki-lint
description: Run a mechanical structure check on a markdown wiki or Obsidian vault - broken wikilinks and heading anchors, orphan pages, duplicate or case-colliding filenames, index and log drift, invalid frontmatter, missing source files, and un-ingested raw files - with a runnable script and a prioritized fix list. Use when the user says "lint the wiki", "check for broken links", "find orphan pages", "is my index up to date", "validate the vault before I publish", "something's wrong with my links after the rename", or "health check the knowledge base".
---
# Wiki Structure Linter
… (sign up to view the full skill)More ai & agents skills
View all AI & Agents skills →New Skill Scaffolder
Create a new Claude Code skill correctly: right mechanism, valid name and folder, a triggering description, and a smoke test.
Skill Library Lint and Overlap Report
Lint every skill in a repo at once: frontmatter, name-folder match, weak descriptions, overlapping triggers, broken refs, plus a CI script.
Self-Verifying Agent Loop: Plan, Check, Retry, Close
Turns a goal into a task plan with machine-run checks, executes with retry caps, escalates, and refuses to close until verified.
Skill Test Runner (Trigger and A/B)
Test a skill in fresh sessions: ready-to-run prompts, commands, and rubric for trigger recall, false triggers, and blind A/B.