菜单
Retrieve screenshots from the Wayback Machine. Use when the user wants to see how a webpage looked, get a visual snapshot, find archived screenshots, or view historical page appearance.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user needs help with path queries, JSON transformations, schema validation, or safe JSON editing workflows. Triggered by questions about JSON operations, data extraction, file merging, or validation strategies.
Scan project dependencies for known vulnerabilities. Automatically detect and parse package files (package.json, requirements.txt, Gemfile, go.mod, pom.xml) and check all dependencies against the CVE database. Use when you want to audit a project for security vulnerabilities, check if dependencies have known CVEs, or generate a vulnerability report for compliance.
Search for Common Vulnerabilities and Exposures (CVEs) by ID (e.g., CVE-2024-1086) or by product name (e.g., OpenSSL, Apache Tomcat). Get detailed vulnerability information including severity scores, affected software versions, and references. Use when the user wants to look up CVE information, check if a product has known vulnerabilities, or research security issues.
Validate a JSON file against the schema referenced in its $schema property. Use when the user asks to check JSON against its own schema, validate self-describing JSON, auto-validate JSON files, or verify JSON with embedded schema reference.
Validate JSON data against a JSON Schema. Use when the user asks to validate JSON against a schema, check if JSON conforms to a schema, test JSON data validity, or verify JSON structure matches a schema definition.
Validate that a JSON Schema is well-formed and conforms to the JSON Schema specification. Use when the user asks to check if a schema is valid, verify schema syntax, validate schema structure, or check a JSON Schema file for errors.
| name | wayback-screenshot |
| description | Retrieve screenshots from the Wayback Machine. Use when the user wants to see how a webpage looked, get a visual snapshot, find archived screenshots, or view historical page appearance. |
Access existing screenshots stored by the Wayback Machine.
npx tsx scripts/screenshot.ts <url> [options]
| Argument | Required | Description |
|---|---|---|
url | Yes | The URL to find screenshots for |
| Option | Description |
|---|---|
--timestamp=DATE | Get screenshot from specific capture (YYYYMMDDhhmmss) |
--list | List available screenshots for URL |
--download=PATH | Download screenshot to file |
--no-cache | Bypass cache and fetch fresh data from API |
Screenshots for: https://example.com/
January 15, 2024 12:34 (3 days ago)
https://web.archive.org/web/20240115123456im_/https://example.com/
December 1, 2023 08:00 (46 days ago)
https://web.archive.org/web/20231201080000im_/https://example.com/
Total: 2 screenshot(s)
npx tsx scripts/screenshot.ts <url> [options]
Options:
--timestamp=DATE - Get screenshot from specific capture (YYYYMMDDhhmmss)--list - List available screenshots for URL--download=PATH - Download screenshot to file--no-cache - Bypass cache and fetch fresh data from APIRun from the wayback plugin directory: ~/.claude/plugins/cache/wayback/
https://web.archive.org/screenshot/{URL}
Get the most recent screenshot:
https://web.archive.org/screenshot/https://example.com/
Get screenshot from a specific capture:
https://web.archive.org/web/{timestamp}im_/https://example.com/
The im_ modifier returns the screenshot image for that timestamp.
Use CDX API with wildcard to find all screenshots:
https://web.archive.org/cdx/search/cdx?url=web.archive.org/screenshot/https://example.com/*&output=json
Or browse visually:
https://web.archive.org/web/*/https://web.archive.org/screenshot/https://example.com/*
When viewing any archived page:
When submitting with capture_screenshot=1, the response includes:
{
"status": "success",
"screenshot": "https://web.archive.org/web/20240115123456im_/https://example.com/"
}
## Caveats
- **Not all captures have screenshots** - depends on whether `capture_screenshot=1` was used during archiving
- **Undocumented feature** - may be unreliable or change without notice
- **Indexing delays** - newly captured screenshots may not appear immediately
- **Coverage varies** - older archives typically don't have screenshots
## Caching
Availability API responses are cached for 24 hours using the OS temporary directory (`os.tmpdir()`). Cache keys are generated from the URL using SHA-256 hashing. Cached responses expire automatically and are deleted on access.
Use `wayback-cache` to manage cached data:
```bash
npx tsx scripts/cache.ts clear # Clear all cache
npx tsx scripts/cache.ts status # Show cache status
See wayback-cache skill for complete cache management documentation.
wayback-submit --capture-screenshot to create a new screenshotwayback-check to verify if a URL is archivedwayback-list to see all captures (not just those with screenshots)