find-dead-links
Skill2 starsChanged 8 months agoMITView on GitHub
Find broken links and redirect chains with SEO impact assessment and pattern detection.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- check-integrationsSkill
- check-seoSkill
- compare-sitesSkill
- find-revenue-leaksSkill
- generate-analytics-specSkill
- growth-auditSkill
- growth-diffSkill
- map-funnelSkill
- suggest-schemaSkill
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
- Distinctive: line 17
Run the link checker:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
/find-dead-links
Audit a page for broken links and redirect chains with impact analysis.
Usage
/find-dead-links <url>Instructions
- Run the link checker:
cd /Users/sdm/Desktop/GrowthLint && python3 -c "import growthlint.cli; growthlint.cli.app()" -- check-links "$URL"- Add AI analysis:
- Pattern detection: Are broken links clustered? (e.g., all from a migration, all to a deprecated domain)
- SEO impact estimate: Which broken links are most damaging for SEO? (links in main nav vs footer)
- User experience impact: Which broken links are in the critical user path?
- Fix priority: Rank broken links by importance (CTA links > nav links > footer links > sidebar links)
- Redirect optimization: For long chains, suggest the direct URL to use instead
- Provide a prioritized fix list with copy-pasteable redirects or URL replacements.
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.

