القائمة
Check if a URL is archived in the Wayback Machine. Use when the user asks to check archive status, verify if a page is saved, or find archived versions of a URL.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | wayback-check |
| description | Check if a URL is archived in the Wayback Machine. Use when the user asks to check archive status, verify if a page is saved, or find archived versions of a URL. |
Check if a URL has been archived by the Internet Archive's Wayback Machine.
npx tsx scripts/check.ts <url> [options]
| Argument | Required | Description |
|---|---|---|
url | Yes | The URL to check |
| Option | Description |
|---|---|
--no-raw | Include Wayback toolbar in archived URL |
--timestamp=DATE | Find snapshot closest to date (YYYYMMDD or YYYYMMDDhhmmss) |
--no-cache | Bypass cache and fetch fresh data from API |
When archived:
✓ Archived
Timestamp: January 1, 2024 (3 days ago)
URL: https://web.archive.org/web/20240101120000id_/https://example.com
When not archived:
✗ Not archived
Consider using wayback-submit to archive this URL.
npx tsx scripts/check.ts <url> [options]
Options:
--no-raw - Include Wayback toolbar in archived URL--timestamp=DATE - Find snapshot closest to date (YYYYMMDD or YYYYMMDDhhmmss)--no-cache - Bypass cache and fetch fresh data from APIRun from the wayback plugin directory: ~/.claude/plugins/cache/wayback/
https://archive.org/wayback/available?url={URL}
| Parameter | Required | Description |
|---|---|---|
url | Yes | The URL to check |
timestamp | No | Find snapshot closest to this date (YYYYMMDDhhmmss, partial dates OK) |
callback | No | JSONP callback for cross-domain requests |
Latest snapshot:
https://archive.org/wayback/available?url=https://example.com
Snapshot closest to a specific date:
https://archive.org/wayback/available?url=https://example.com×tamp=20200101
Archived - Response contains archived_snapshots.closest with:
available: trueurl: The archived URL (format: https://web.archive.org/web/{timestamp}/{original_url})timestamp: Archive timestamp (YYYYMMDDhhmmss format)status: HTTP status codeNot Archived - Response has empty archived_snapshots object.
By default, append id_ after the timestamp in URLs to get raw content without the Wayback toolbar:
https://web.archive.org/web/20240101120000/https://example.comhttps://web.archive.org/web/20240101120000id_/https://example.com| Modifier | URL Pattern | Description |
|---|---|---|
| (none) | /web/{ts}/ | Page with Wayback toolbar |
id_ | /web/{ts}id_/ | Raw page content (no toolbar) |
im_ | /web/{ts}im_/ | Screenshot image |
js_ | /web/{ts}js_/ | JavaScript content |
cs_ | /web/{ts}cs_/ | CSS content |
wayback-screenshot to retrieve visual screenshots of archived pageswayback-list to see all captures with filtering optionswayback-submit to create a new archive (with optional screenshot)Availability API responses are cached for 24 hours using the OS temporary directory (os.tmpdir()). Cache keys are generated from the URL and timestamp parameters using SHA-256 hashing. Cached responses expire automatically and are deleted on access.
Use wayback-cache to manage cached data:
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.
If the Wayback Machine API returns an error or is unavailable, retry after a brief delay. The API may be rate-limited during high traffic periods.
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.