Claude Doc Doctor

v4.0.1

Say 'lint my docs' to scan your markdown KB for broken links, orphan pages, and missing metadata — then auto-fix them.

0· 104·0 current·0 all-time
bySingYee@singggggyee
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description match the requested binaries and actions: python3 is required and the skill installs/uses a Python CLI (kb-lint) to lint and auto-fix markdown. No unrelated credentials, config paths, or network-only services are requested. One minor inconsistency: the install spec lists kind: uv package: kb-lint while the runtime instructions use pip as a fallback; this is explainable (platform installer vs. pip) but worth noting.
Instruction Scope
SKILL.md explicitly instructs scanning project folders (docs/, wiki/, etc.) and, in 'memory' mode, ~/.claude/. It runs kb-lint CLI and, if missing, runs pip install kb-lint. The skill will rename files, update references, read git history to infer creation dates, and propose or perform auto-fixes. Those actions are within scope for an auto-fixer, but they are materially destructive (renames/edits). The doc includes safety rules (always show changes before applying, confirm fuzzy matches, never fabricate content), which mitigates risk if followed. Users should expect file I/O and git access.
Install Mechanism
Install spec uses an 'uv' package installer for kb-lint; the runtime fallback installs via pip. Installing a third-party Python package from PyPI is a common and expected mechanism for a Python CLI, but it does execute package installation on the host (network fetch, files written to disk, potential post-install scripts). There are no direct downloads from unknown/personal URLs in the spec.
Credentials
The skill requests no environment variables or credentials. It does access user files and git history when run (including optional ~/.claude/), which is proportional to a linter that can operate on local KB/memory. No unexplained secrets or broad service credentials are requested.
Persistence & Privilege
always is false and the skill does not request persistent platform privileges. It installs a package into the host environment when run (per install spec / pip fallback), but it does not try to modify other skills or global agent config per the provided instructions.
Assessment
This skill appears to do what it says, but it will read and modify files in your repo (and optionally your Claude memory at ~/.claude/), and may install a Python package. Before installing or running: 1) Review the kb-lint project (homepage/PyPI source) to confirm you trust it. 2) Prefer running pip install inside a virtual environment (or inspect the package) instead of global install. 3) Back up or use git so you can review/undo changes; run in 'show changes / dry-run' mode first. 4) Be cautious when scanning your home directory (~/.claude/) because it can expose personal data—only run memory-mode if you intend it. 5) Note the small inconsistency between the 'uv' install spec and the SKILL.md's pip fallback; confirm how your platform will install the kb-lint package. If you want extra assurance, run kb-lint manually on a test copy of your docs before granting the skill write permission.

Like a lobster shell, security has layers — review code before you run it.

latestvk97cz278a758m5z2186n6bpzcd846cg0

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🔍 Clawdis
OSmacOS · Linux
Binspython3

Install

uvuv tool install kb-lint

Comments