links-validate

Identify and fix broken links and invalid references in Markdown documents.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oogDZ/2 --skill links-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: links-validate
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/links-validate
Command: npx skills add https://github.com/oogDZ/2 --skill links-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates and ensures consistency of links across Markdown documents, helping prevent broken references after refactors, renames, or file moves.

Core Features & Use Cases

  • Link integrity checks: verify internal anchors, relative paths, and frontmatter-based references.
  • Refactor safety: detects broken links introduced by file renames or relocations.
  • Pre-commit readiness: provides a quick validation prior to committing changes.

Quick Start

Run the /links-validate command with an optional path to scan a subset of the project and optionally request JSON output.

Frequently Asked Questions about links-validate

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

FAQPage Schema
How do I validate Markdown links and fix broken references after renaming files?

To validate Markdown links after file renames, run the skill to detect broken internal anchors, relative paths, and frontmatter references, ensuring refactor safety and pre-commit readiness.

What is the best way to check Markdown anchor links and relative paths across multiple chapters?

The best way to check Markdown anchors and relative paths across multiple chapters is to scan interconnected documents, verifying frontmatter fields and internal references to ensure link integrity.

Can I get validation results for Markdown links in a structured JSON format?

Yes, you can request structured JSON output when validating Markdown links, which reports findings on broken anchors, invalid relative paths, and frontmatter references in a machine-readable format.

How do I scan a specific subset of my documentation project for invalid Markdown links?

To scan a specific subset of your documentation project for invalid Markdown links, run the validation command with an optional path argument to target the desired directory scope.

Does this Markdown link validator work with frontmatter-based references?

Yes, the link validator works with frontmatter-based references, verifying link integrity by checking frontmatter fields, internal anchors, and relative paths across your Markdown documents.