Broken Link CheckerSAFE
Open-source SEO, GEO, and marketing skills for AI agents.
Overview
Open-source SEO, GEO, and marketing skills for AI agents.
f08bca773eb5OBSERVED · 2026-10-08What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
---
name: broken-link-checker
argument-hint: "<URL to check, e.g. https://example.com>"
description: >
Scans a website to find broken links (404s, 500s). Crawls internal pages,
identifies broken outbound links, and reports source pages for easy fixing.
Use this when the user asks to "check for broken links", "find 404s",
"audit my links", or "is my site healthy".
---
# 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:
```bash
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!Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (5 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
f08bca773eb5full audit observations/trust-audit/skill/nowork-studio__broken-link-checker.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | f08bca773eb5 | SAFE | B | 89 | first audit |
Questions
What does the Broken Link Checker skill do?
Open-source SEO, GEO, and marketing skills for AI agents.
Is Broken Link Checker safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Broken Link Checker access on my machine?
The audit observed that it reaches the network. Each of those is consistent with what it says it does. Secrets in the source: none found.
How current is this page?
The grade is for one exact copy of the source (f08bca773eb5), read on 2026-10-08. The repository is watched, and a new audit runs when it changes — this is the first audit.