Claude Doc Doctorv4.0.1

An engineering team maintains a large markdown knowledge base with hundreds of interlinked documents, and broken wiki-links and orphan pages accumulate over time. Running 'lint my docs' identifies all broken links, orphan pages, and missing frontmatter, then offers auto-fixes. The team re-runs the linter to get a before/after health score and track documentation quality over time.

A researcher or writer keeps a personal Obsidian-style vault of markdown notes and wants to keep it organized. The skill scans for thin articles, inconsistent tags, and bad filenames, then suggests outlines or auto-normalizes metadata. This transforms a messy notes folder into a well-structured, discoverable knowledge base.

A developer using Claude Code has a growing ~/.claude/ memory directory with stale entries, duplicate notes, and an outdated MEMORY.md index. Running 'lint my memory' audits frontmatter accuracy, flags entries older than 90 days, and finds duplicates. This keeps the agent's long-term memory reliable and reduces context bloat.

A technical writing team publishes API docs in markdown and needs to catch broken internal links and missing metadata before release. The skill runs a JSON-format lint, groups issues by severity, and auto-fixes broken links via fuzzy matching with user confirmation. Writers use the health score as a release gate for documentation quality.

An open source maintainer wants to ensure contributor-submitted markdown docs meet quality standards like kebab-case filenames and complete frontmatter. The skill scans the wiki/ or docs/ folder, offers auto-fixes for filenames and metadata, and verifies the changes with a re-run. This reduces manual review overhead and keeps the project docs consistent.

The core kb-lint CLI is free and open source, while a paid cloud dashboard offers team-wide documentation health tracking, historical score trends, and automated PR checks. Revenue comes from monthly subscriptions per repository or per seat. This aligns with the existing GitHub/PyPI distribution model.

Offer paid consulting engagements where experts use Doc Doctor to audit, clean up, and restructure large enterprise knowledge bases, especially for migrations to markdown-based systems. Revenue is generated through project-based fees and ongoing maintenance contracts.

Sell an enterprise license that bundles kb-lint with CI/CD pipelines, providing automated documentation quality gates, custom rule sets, and priority support. Revenue comes from annual license fees based on organization size and usage.