agentleFS
Lethe044Lethe044/agentskill-kit/skills/markdown-link-checker/SKILL.md

markdown-link-checker

Skill50 starsChanged 21 days agoMITView on GitHub

Checks relative links, image paths and heading anchors in Markdown files without using the network, and lists every broken one with its line number. Use when the user asks to verify README or docs links, after moving or renaming files, or before publishing documentation.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before a release, to make sure the docs have no dead internal links.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Markdown link checker

Finds links that point nowhere inside a repository. External http and https links are skipped on purpose, so the check is fast, repeatable and works offline.

When to use

  • Files or folders were renamed or moved and docs may now point to the old paths.
  • A README has a table of contents with #anchors.
  • Before a release, to make sure the docs have no dead internal links.

How to run

python scripts/check_links.py README.md docs/

Directories are searched recursively for .md files. Hidden folders and node_modules are skipped.

What is checked

  • [text](path/to/file.md) and image links: the target must exist, relative to the file that contains the link.
  • [text](#section): the heading must exist in the same file.
  • [text](other.md#section): the file must exist and contain the heading.
  • Heading anchors use the GitHub style: lowercase, punctuation removed, spaces become hyphens, repeated headings get -1, -2 and so on.
  • Fenced code blocks and inline code are ignored.

Output

JSON with files, links_checked and broken, a list of {"file", "line", "target", "reason"}. Reasons are file not found and anchor not found. The exit code is 1 when anything is broken.

After running

Group the broken links by file, fix the target when the file moved, and remove the link when the content is gone. For anchors, check whether the heading was reworded.

Errors

A path that does not exist exits with code 2.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.