docs-links
Skill8 starsChanged 11 days agoMITView on GitHub
Checking markdown links and anchors after a docs edit. Use for docs, markdown link, anchor, broken link, cross-reference.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- local-installSkill
- verify-changeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Run python verify_docs_links.py -> "All N links verified successfully!" -> done.
≈ “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.
Files
House skill — established by dz-runner setup mode from this repo's own evidence, then owned by its maintainers. Correct it in place; setup never overwrites a skill that exists.
- Run
python verify_docs_links.py-> "All N links verified successfully!" -> done. - A red run prints each broken link with its file and line number -> fix the target path or the anchor in the file it names, then re-run.
- The script resolves relative markdown links, relative file paths and
#anchorreferences inside the same file -> an anchor rename breaks the link that names it. - It scans every
*.mdin the repo (README,docs/,examples/,CHANGELOG.md) and skips.venvand.claude-task-master-> a new doc directory needs no extra configuration. - The gate does not check links -> run this after any edit under
docs/,examples/or a README, before the gate.
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
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.

