link-validator

Validate markdown links for portability across Claude Code skill deployments.

62|10|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/terrylica/cc-skills --skill link-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-validator
Source: https://github.com/terrylica/cc-skills/tree/main/plugins/link-tools/skills/link-validator
Command: npx skills add https://github.com/terrylica/cc-skills --skill link-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Validates markdown links for portability, ensuring relative paths and cross-installation compatibility.

Core Features & Use Cases

  • Detect absolute repo paths in links and flag portability issues
  • Identify and report code blocks and inline links that require attention
  • Output a clear report to inform fixes

Quick Start

Run the validator on a skill directory: uv run scripts/validate_links.py plugins/your-skill/

Frequently Asked Questions about link-validator

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

FAQPage Schema
How do I validate markdown links for portability across Claude Code skill installations?

Markdown link validation checks that links use relative paths instead of absolute repo paths, ensuring skills work consistently when installed in different environments. Run the validator on your skill directory to detect portability issues and get structured reports with fixes.

What makes a markdown link non-portable in Claude Code skills?

Absolute repo paths in links break portability because they reference fixed locations that don't exist in other installations. Relative paths and external URLs remain valid across deployments, making them portable.

Can I convert absolute paths to relative paths in my skill's markdown automatically?

The validator detects absolute paths and reports them with suggested fixes, but conversion requires manual updates. Use the structured violation reports to identify and replace absolute paths with relative references.

How do I prepare a skill for distribution to other Claude Code users?

Run link validation to audit all markdown references, fix absolute paths and broken references, and verify relative and parent directory links work correctly. This ensures cross-installation compatibility before publishing.

What types of links does the validator treat as valid?

Relative paths, parent directory references, external URLs, and anchor links are treated as valid. Only absolute repo paths are flagged as portability violations.

What output does the link validator provide?

The validator produces a structured violation report with standardized exit codes, flagged links, their locations in code blocks or inline content, and suggested fixes for each issue.