from ctx41
Scan project markdown for broken internal links, missing images, and unreachable external URLs; produce a clear report and suggested fixes before docs releases.
CTX Link Check scans a repository's documentation (markdown files) to find broken internal links, missing images, and external URLs that return errors or time out. It runs a two-pass internal/external check plus image verification and outputs a human-readable report with locations and suggested fixes.
Use before documentation releases, after renaming or moving pages, during audits (/_ctx-audit), or when users report 404s. It's intended for projects with docs/, doc/, documentation/, or similar directories, and falls back to scanning root .md files if needed.
Best for agents that can read repository files and perform HTTP requests (bash/curl-capable assistants, CI bots, or documentation tooling agents).
CTX Link Check is a documentation link auditor that scans markdown files for broken internal links, missing images, and unreachable external URLs. It uses two-pass execution (internal file checks + external HTTP HEAD/GET) with a third pass for images. No bundled scripts — the skill relies entirely on the agent using Bash(curl), Read, Grep, and Glob to execute. Well-structured instructions with clear output format and sensible defaults (skip localhost/example URLs, timeouts on external checks, treat external failures as warnings not errors).
Security is strong: only uses curl/Read/Grep/Glob, no credential handling, no destructive operations, no network calls to suspicious hosts. External checks treat failures as warnings (correct approach). No shell injection risk since there are no scripts. Code quality is good — instructions are clear and step-by-step, but the skill is purely instructional with no automation scripts, so execution quality depends on the agent. Architecture is decent but missing references/ or scripts/ directories, uses non-standard 'allowed-tools' frontmatter, and the integration with /_ctx-audit is context-specific to the ctx project. Usefulness is solid — link checking is a common real need for doc-heavy projects, though many alternatives exist.
