link-checker-agent

Audit and fix broken documentation links across Markdown and source files.

5|3|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/richfrem/agent-plugins-skills --skill link-checker-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-checker-agent
Source: https://github.com/richfrem/agent-plugins-skills/tree/main/plugins/link-checker/skills/link-checker-agent
Command: npx skills add https://github.com/richfrem/agent-plugins-skills --skill link-checker-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Documentation often suffers from broken links, outdated references, and inconsistent guidance across large repos. This skill provides automated validation, auditing, and repair workflows to maintain documentation hygiene.

Core Features & Use Cases

  • Deterministic 5-step pipeline: Inventory, Extract, Audit, Fix, Report.
  • Auto-fix of unambiguous link references and generation of human-facing reports.
  • Safe, isolated execution with guidance on when to commit changes across repositories.

Quick Start

Trigger the link-checker-agent to inventory files, extract references, audit for broken paths, auto-fix unambiguous issues, and generate a report.

Frequently Asked Questions about link-checker-agent

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

FAQPage Schema
How do I find and fix broken links in Markdown documentation across multiple repositories?

To find and fix broken links in Markdown documentation, this agent runs a deterministic 5-step pipeline that inventories files, extracts references, audits gaps, auto-fixes unambiguous matches, and generates reports across multi-repo environments.

What is the best way to automate documentation link validation for large repositories?

Automating documentation link validation is best handled by a pipeline that extracts links from source files, audits for broken paths, and safely auto-fixes unambiguous references while flagging ambiguous issues for manual review.

Can I automatically repair documentation links without causing incorrect updates?

You can automatically repair documentation links safely because the pipeline only applies automated fixes to unambiguous matches, isolating uncertain references into an unfixable_links_report.md for manual review.

How do I audit outdated references and broken paths in my source files?

Auditing outdated references and broken paths involves performing a gap audit on extracted links from source files, identifying mismatches, and outputting the results into a structured broken_links.json artifact for tracking.

Does the link checker generate reports for unfixable documentation issues?

The link checker does generate reports for unfixable documentation issues, specifically producing a human-facing unfixable_links_report.md file alongside a broken_links.json artifact to track all unresolved references.

When should I manually commit repository changes after automated link fixing?

You should manually commit repository changes after automated link fixing only after reviewing the generated reports and unfixable links, following the safe, isolated execution guidance to ensure documentation hygiene across repos.