dead-link-sweep

Identify dead URLs in INDEX tables and archive them with audit records.

8|1|Updated Apr 20, 2018
One-click install
npx skills add https://github.com/Executioner1939/awesome-engineering-research --skill dead-link-sweep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dead-link-sweep
Source: https://github.com/Executioner1939/awesome-engineering-research/tree/main/.claude/skills/dead-link-sweep
Command: npx skills add https://github.com/Executioner1939/awesome-engineering-research --skill dead-link-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

dead-link-sweep prevents your curated INDEX sources/tools lists from silently degrading by identifying dead URLs and archiving them with clear tombstones and optional Wayback references.

Core Features & Use Cases

  • Liveness probing: Scans active entries in INDEX/sources.md and optionally INDEX/tools.md using HTTP HEAD requests and classifies results (2xx, redirects, 4xx/5xx, DNS/SSL/connect failures, timeouts).
  • Deterministic archival with audit trail: Moves confirmed-dead rows into _archived/ instead of hard-deleting, adding last_seen and reason (and wayback when available).
  • Optional repo-state enrichment for tools: When targeting tools, fetches repository metadata to mark archived/stale repos based on archived status and pushed_at recency.
  • Operational reporting: Generates an _archived/sweep-report-<YYYY-MM-DD>.md summary and supports the standard link-sweep/<date> workflow.

Quick Start

Run dead-link-sweep to scan INDEX/sources.md and _archived-archive any confirmed-dead URLs with recorded reasons and a daily sweep report.

Frequently Asked Questions about dead-link-sweep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify and archive dead URLs in a markdown index file without losing history?

To archive dead URLs without losing history, scan your markdown index files using HTTP HEAD liveness probing and migrate confirmed-dead rows into an `_archived/` directory with `last_seen` and `reason` metadata.

What is the best way to audit link liveness and handle HTTP status classifications in a curated repository?

Link liveness auditing uses parallel HTTP HEAD checks with bounded concurrency and timeout/retry rules to classify URL states, detecting 4xx/5xx errors, DNS failures, and redirects before archiving broken entries.

How do I preserve dead links with Wayback references during index maintenance?

During index maintenance, dead links are preserved by moving broken rows into `_archived/` and optionally appending a Wayback lookup URL as a tombstone, ensuring an auditable history without hard-deleting entries.

Can I check repository metadata to mark archived or stale tools during a URL sweep?

Yes, when targeting tools, the sweep can fetch repository metadata to mark archived or stale repositories based on their archived status and `pushed_at` recency, enriching the standard URL liveness check.

What sweep report is generated after probing URLs for liveness and archiving dead entries?

After archiving dead entries, a sweep report named `_archived/sweep-report-<YYYY-MM-DD>.md` is generated, summarizing the confirmed-dead URLs, their failure reasons, and optional Wayback references for audit purposes.