link-verification

Validate and verify Markdown links in documentation before publishing.

8|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/bordenet/superpowers-plus --skill link-verification-bordenet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-verification
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/wiki/link-verification
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill link-verification-bordenet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Links in documentation often become hallucinated or broken, leading to dead ends, misinformation, and wasted time. This skill ensures every URL or markdown link is validated before the content is published or committed.

Core Features & Use Cases

  • Batch verification of all markdown links in a document, producing a detailed report with pass/fail status.
  • Hard gating for internal wiki and repository links, blocking publication when critical links are invalid.
  • Regex extraction of markdown link syntax and bare URLs, supporting internal wiki pages, code references, issue tickets, and external sites.
  • Orchestrator integration as a mandatory step in the wiki‑orchestrator pipeline, providing automatic safety checks.

Quick Start

Ask the AI to verify all links in the draft wiki page before publishing.

Frequently Asked Questions about link-verification

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

FAQPage Schema
How do I check for broken or hallucinated links in markdown documentation?

Broken link verification scans markdown files to validate every URL using regex extraction, producing a detailed pass/fail report. This process catches hallucinated URLs in wiki pages and README files before you publish or commit content.

What is hard gating for internal wiki links and how does it work?

Hard gating blocks publication when internal wiki or repository links fail validation. It enforces that mandatory markdown links resolve correctly before content is committed or published.

Can I validate URLs in a README file before committing code?

You can validate URLs in a README file before committing by running batch verification. The tool extracts markdown link syntax and bare URLs, ensuring code reference sections and internal links resolve correctly to block invalid commits.

Does link verification work with bare URLs or only standard markdown link syntax?

Link verification works with both standard markdown link syntax and bare URLs. Regex extraction identifies all URL formats within your documentation to ensure comprehensive validation across internal wiki pages and external sites.

How do I stop hallucinated URLs from appearing in published wiki pages?

To stop hallucinated URLs in wiki pages, apply link verification as a mandatory pre-publication step. This validates all links and enforces a hard block on publication for any broken internal or repository links.

What are the limitations of automated markdown link validation?

Automated markdown link validation focuses strictly on URL resolution and does not verify the contextual accuracy of the linked content. It classifies link failures by type but primarily enforces hard blocks only for internal or repository links.