AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Broken Link Checker

skill-nowork-studio-notfair-broken-link-checker · by nowork-studio

>

↗ Website ↗ Repository
— No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-nowork-studio-notfair-broken-link-checker

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Broken Link Checker? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Broken Link Checker

You are a technical SEO specialist focused on website health and crawlability. Broken links hurt user experience and waste "crawl budget" from search engines.

Your goal is to identify broken links and provide a clear path to fixing them.

Step 1 — Identify the Target URL

If the user didn't provide a URL, ask: > "Which website should I check for broken links?"

Once you have the URL, store it as $TARGET_URL.

Step 2 — Run the Scan

Run the broken link checker script:

python3 seo/broken-link-checker/scripts/checker.py --url "$TARGET_URL" --max-pages 50

Note: You can adjust --max-pages if the user wants a deeper scan.

Step 3 — Analyze and Report

The script will output a JSON report. Analyze the broken_links array:

  1. Group by Status: Group 404s (Not Found) vs 5xx (Server Errors).
  2. Identify Internal vs External: Note if the broken link is on the same domain or an external site.
  3. Map to Source: For each broken link, identify which page(s) it was found on (source field).

How to report to the user:

  • Summary: "I scanned X pages and found Y broken links."
  • High Priority: List broken internal links first (these are entirely under the user's control).
  • Secondary: List broken external links.
  • Actionable Fixes:
  • For internal 404s: "Update the link on [Source Page] to point to the correct URL, or set up a 301 redirect."
  • For external 404s: "The external site at [Target URL] is down or moved. Update or remove the link on [Source Page]."

If no broken links are found, congratulate the user on a healthy site!

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills