link-validation

Validate Markdown links, anchors, and cross-references across repository files.

13|3|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/Everyone-Needs-A-Copilot/claude-copilot --skill link-validation-everyone-needs-a-copilot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-validation
Source: https://github.com/Everyone-Needs-A-Copilot/claude-copilot/tree/main/templates/skills/link-validation
Command: npx skills add https://github.com/Everyone-Needs-A-Copilot/claude-copilot --skill link-validation-everyone-needs-a-copilot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures the integrity of documentation by detecting broken Markdown links, invalid anchors, and missing cross-references across a repository.

Core Features & Use Cases

  • Link validation: Detect broken links and missing anchors in Markdown files.
  • Anchor verification: Validate that internal headers exist for anchors like #section.
  • Cross-reference checks: Ensure file+anchor references resolve correctly across directories.
  • Use Case: When maintaining a shared docs folder, run this skill to automatically report all broken links and anchors, then auto-fix where possible.

Quick Start

Run the link-validation skill to scan your docs under docs/**/*.md and report any issues.

Frequently Asked Questions about link-validation

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

FAQPage Schema
How do I validate markdown links and cross-references in my documentation?

To validate markdown links, this skill analyzes internal links, anchors, and file+anchor references across Markdown files in a repository, reporting broken links and missing headings. It uses standard shell tools like grep, find, and sed to scan your docs directory.

What is the best way to find broken anchors and missing headings in Markdown files?

Finding broken anchors and missing headings requires verifying that internal headers exist for references like #section. This skill performs anchor verification and cross-reference checks across directories to ensure documentation integrity and generate a structured report.

Can I check internal markdown file and anchor references across multiple directories?

Yes, you can check internal markdown file and anchor references across directories. This skill performs cross-reference checks to ensure file+anchor references resolve correctly, validating that internal headers exist for anchors like #section throughout the repository.

Do I need any special dependencies to validate markdown documentation links?

No special dependencies are required to validate markdown documentation links. This skill requires only standard shell tools like grep, find, and sed, along with frontmatter-driven configuration, to generate a structured report with a summary and suggested fixes.

Why are my markdown cross-references not resolving correctly in a shared docs folder?

Markdown cross-references may not resolve correctly due to broken links, invalid anchors, or missing headings. This skill detects these issues by analyzing file and anchor references across Markdown files, then reporting broken links and providing suggested fixes.