What happens when I run the clear command?

The clear command deletes all .json cache files from the temporary wayback-cache directory, forcing all subsequent requests to fetch fresh data from the API.

Does the cache clear itself automatically?

Yes, cached entries expire automatically based on their TTL and are deleted when accessed after expiration.

How do I bypass the cache for a single request?

You can use the --no-cache flag with compatible scripts like check.ts or list.ts to skip the cache and fetch fresh data.

Where is the Wayback cache stored?

Cached responses are stored in your operating system's temporary directory under a 'wayback-cache' folder.

How long does the cache stay valid?

The TTL varies: Availability API data lasts 24 hours, CDX API data lasts 1 hour, and Save status polls expire in 30 seconds.

Wayback Cache Management

Name: Wayback Cache Management
Author: Mearman

byMearman

•

Web Scraping & Data Collection

Manages local API response caching for Wayback Machine operations to optimize performance and ensure data freshness.

About

The Wayback Cache Management skill provides specialized tools for controlling how Claude interacts with archived web data by managing a local tmpdir-based cache. It enables users to clear stale API responses, monitor cache health, and check storage locations, ensuring that archive-related tasks like snapshots and availability checks remain accurate and efficient. This skill is essential for developers working with the Wayback Machine who need fine-grained control over API rate limiting and data consistency through intelligent TTL management and manual cache overrides.

Key Features

Clear all cached Wayback Machine API responses with a single command
Secure SHA-256 hashing for unique cache key generation
Automatic TTL management for Availability, CDX, and Save APIs
Per-operation cache bypass using the --no-cache flag
Monitor cache status including file count and directory location
2 GitHub stars

Use Cases

Optimizing disk space by clearing temporary API response files
Refreshing stale archive data when new snapshots are expected
Debugging API responses by forcing fresh network requests without clearing the entire cache

About

Key Features

Clear all cached Wayback Machine API responses with a single command
Secure SHA-256 hashing for unique cache key generation
Automatic TTL management for Availability, CDX, and Save APIs
Per-operation cache bypass using the --no-cache flag
Monitor cache status including file count and directory location
2 GitHub stars

Use Cases

Optimizing disk space by clearing temporary API response files
Refreshing stale archive data when new snapshots are expected
Debugging API responses by forcing fresh network requests without clearing the entire cache