chsh-sk-llm-wiki-maintain

Audits a Karpathy-style LLM wiki for schema violations, broken links, orphans, and stale content.

1|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/chshzh/claude --skill chsh-sk-llm-wiki-maintain-chshzh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chsh-sk-llm-wiki-maintain
Source: https://github.com/chshzh/claude/tree/main/skills/chsh-sk-llm-wiki-maintain
Command: npx skills add https://github.com/chshzh/claude --skill chsh-sk-llm-wiki-maintain-chshzh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Personal knowledge wikis accumulate structural rot over time: broken links, orphan pages, missing frontmatter, stale entries, and index drift. This Skill runs a systematic daily health audit that finds and reports these issues before they compound. ## Core Features & Use Cases - Schema & Frontmatter Validation: Checks every wiki page against the wiki's own SCHEMA.md rules, including required fields, tag taxonomy, and date formats. - Link & Index Health: Detects broken wikilinks, orphan pages with zero inbound links, duplicate headings, and pages missing from index.md. - Staleness & Drift Detection: Flags pages older than 180 days, sha256 mismatches in raw sources, contested or low-confidence pages, and runs a credential leak scan. - Use Case: Schedule it as a daily cloud routine; it early-exits when the wiki repo is unchanged, otherwise reports P0/P1/P2 findings in-session and asks how to fix each severity group. ## Quick Start Run the daily wiki audit on my LLM wiki and report any schema violations, broken links, or stale pages.

Frequently Asked Questions about chsh-sk-llm-wiki-maintain

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

FAQPage Schema
How do I audit a personal wiki for broken links and orphan pages?

Run this audit skill against the wiki directory; it inventories all Markdown pages, resolves every wikilink and Markdown link, and flags unresolved targets plus pages with zero inbound links. Findings are reported by severity in the chat session.

How to validate Markdown frontmatter against a custom schema?

The skill reads the wiki's own SCHEMA.md first, then checks every page for required fields like title, created, updated, type, tags, and sources. It validates tag values against the schema's closed taxonomy and dates against YYYY-MM-DD format.

Does the wiki audit work with both wikilinks and Markdown links?

Yes, it supports both [[wikilinks]] and [text](path.md) conventions. It checks which convention SCHEMA.md mandates and flags pages that mix the two styles.

Can the audit run automatically on a schedule?

Yes, it is designed as a scheduled cloud routine. An early-exit check compares the last audited git commit against the current HEAD and skips the run entirely when nothing has changed.

Why does the audit report sha256 drift on raw source files?

Raw sources store a sha256 hash of their body at ingest time; a mismatch means the file was edited locally or the source changed. The skill flags this as P2 and asks whether to re-hash or revert, never silently re-hashing.

Does the wiki audit write report files to disk?

No, findings are presented directly in the chat session as a P0/P1/P2 report. The only file written is a lint entry appended to log.md after fixes are approved and committed.