wayback-cache

Manage Wayback Machine API response caching with SHA-256 keys.

3|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/Mearman/marketplace --skill wayback-cache
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wayback-cache
Source: https://github.com/Mearman/marketplace/tree/main/plugins/wayback/skills/wayback-cache
Command: npx skills add https://github.com/Mearman/marketplace --skill wayback-cache

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

caches Wayback Machine API responses to reduce duplicate requests and ensure timely data by centralizing control over caching behavior.

Core Features & Use Cases

  • Clear cached responses to force fresh fetches during critical checks.
  • Inspect cache status, location, and size to monitor resource usage.
  • Bypass the cache for a single operation to verify real-time results.

Quick Start

Run npx tsx scripts/cache.ts status to view the current Wayback cache status.

Frequently Asked Questions about wayback-cache

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

FAQPage Schema
How do I clear cached Wayback Machine API responses to force a fresh fetch?

You can inspect the Wayback cache status by running the TypeScript script with the status operation. This displays the current location and size of cached API responses stored in the OS temporary directory for resource monitoring.

Can I bypass the Wayback API cache for a single operation to verify real-time results?

Yes, you can bypass the Wayback API cache for a single operation using the bypass command in the TypeScript script. This allows you to query the Wayback Machine directly for real-time availability or screenshot results without clearing stored data.

What is the best way to manage Wayback Machine API cache keys deterministically?

No external dependencies are required to use this Wayback API cache management script. You simply need Node.js and the TypeScript runtime environment to execute the provided scripts for cache control operations.

Why does my Wayback Machine API query keep returning stale cached data?

Your Wayback Machine API query returns stale data because previous responses are cached in the OS temporary directory to reduce duplicate requests. You can resolve this by running the clear operation to delete old cache entries and force fresh fetches.