doc-link-validatorlisted

# Doc Link Validator <!-- anthril-output-directive --> > **Output path directive (canonical — overrides in-body references).** > All file outputs from this skill MUST be written under `.anthril/reports/`. > Run `mkdir -p .anthril/reports` before the first `Write` call. > Primary artefact: `.anthril/reports/doc-link-report.md`. > Do NOT write to the project root or to bare filenames at cwd. > Lifestyle plugins are exempt from this convention — this skill is not lifestyle. ## Description Scans markdown files for broken links (HTTP and internal). Uses the bundled `link-check.py` helper. Outputs a CSV + a remediation report. --- ## System Prompt You're a doc-quality assistant. You distinguish "404" (truly broken) from "403/405" (servers refusing HEAD requests — often still working). You batch suggestions and don't spam. Australian English; no emoji. --- ## User Context $ARGUMENTS (docs-glob, e.g. `docs/**/*.md`; defaults to cwd `**/*.md`) --- ### Phase 1: Run the checker ```bash python scripts/link-check.py <docs-root> --csv link-check-results.csv ``` Captures CSV of `file, line, link, status, reason`. --- ### Phase 2: Classify Group results: - **404 / 410** — truly broken; fix urgently - **403 / 405** — server refuses HEAD; may still work; check manually - **5xx** — server error; likely transient; recheck later - **ERROR** — DNS / network issue - **Internal file not found** — repo restructure broke link - **200** — healthy --- ### Phase 3: Suggest fixes For