agentleFS
SaehwanParkSaehwanPark/agent-skills-archive/skills/wayback-link-fallback/SKILL.md

wayback-link-fallback

Skill1 starsChanged 5 months agoMITView on GitHub

Use when a task depends on a dead, redirected, incomplete, version-specific, or historically changed web page and archived evidence from the Wayback Machine may recover the required source.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    If historical or unavailable content is needed, query captures for the exact original URL.

    line 14
  2. Distinctive:

    Verify current claims against a live primary source.

    line 22
  3. Distinctive:

    Avoid broad wildcard crawls or asset enumeration unless explicitly required.

    line 34
  4. Distinctive:

    If no reliable capture exists, try one narrower primary alternative: versioned official docs, a tagged source file, package registry, …

    line 38

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Wayback Link Fallback

Recover the smallest reliable archived source needed for the task and label it as historical evidence.

Workflow

  1. Try the original URL and determine whether the live content still answers the question.
  2. If historical or unavailable content is needed, query captures for the exact original URL. Prefer one narrow CDX query over manually opening many snapshots.
  3. Select a successful capture that matches the relevant date, product version, and MIME type; avoid login pages, soft 404s, consent screens, and unrelated redirects.
  4. Fetch raw archived content with the id_ form when possible to avoid archive UI and URL rewriting.
  5. Record the original URL, snapshot URL, capture timestamp, and any version or completeness uncertainty.
  6. Verify current claims against a live primary source. Never present an archive snapshot as current truth merely because it was retrievable.

For CDX parameters, capture selection details, and relative-link resolution, read capture and link handling.

Request discipline

  • Make the fewest requests that can answer the task.
  • Collapse duplicate digests in capture-heavy results.
  • Back off on slow, empty, 429, or 503 responses.
  • Cache useful timestamps and URLs in task-local notes instead of repeating requests.
  • Avoid broad wildcard crawls or asset enumeration unless explicitly required.

Failure handling

If no reliable capture exists, try one narrower primary alternative: versioned official docs, a tagged source file, package registry, release page, official mirror, or repository history. Keep fallback provenance explicit.

Report failure rather than relying on captures that are blocked, partial, mismatched to the target version, or missing required scripts, assets, schemas, or linked pages.

For legal, medical, financial, security-sensitive, or other high-stakes current claims, use archived content only as historical evidence and verify the present state with live authoritative sources.

Expected output

Include the original URL, archive URL, capture timestamp (YYYYMMDDhhmmss), relevant human date, why that capture was chosen, and all material uncertainty.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.