capture-all-pages

Captures high-resolution screenshots of all manual pages for translation QA verification.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/Takazudo/takazudomodular-manuals --skill capture-all-pages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture-all-pages
Source: https://github.com/Takazudo/takazudomodular-manuals/tree/main/.claude/skills/capture-all-pages
Command: npx skills add https://github.com/Takazudo/takazudomodular-manuals --skill capture-all-pages

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) components.

What problem does it solve?

This skill captures high-resolution screenshots of all manual pages from the OXI viewer to verify translations against page images, ensure layout consistency, and detect content mismatches.

Core Features & Use Cases

  • High-resolution batch capture (2000x1600) for translation QA and visual verification
  • Automated navigation across all pages and organized output under __inbox
  • Generates per-page PNGs and a summary.json with results
  • Use Case: QA teams can confirm that translations align with the original page images across multi-page manuals

Quick Start

Run the capture-all-pages skill to capture all pages: node .claude/skills/capture-all-pages/scripts/capture.js To capture a subset of pages: node .claude/skills/capture-all-pages/scripts/capture.js --pages 100 Use a custom base URL: node .claude/skills/capture-all-pages/scripts/capture.js --base-url http://zmanuals.localhost:3100/manuals/oxi-one-mk2/page

Frequently Asked Questions about capture-all-pages

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

FAQPage Schema
How do I capture high-resolution screenshots of manual pages for translation QA?

Capturing high-resolution screenshots for translation QA requires Playwright as a runtime dependency and a running dev server. The script automates navigation across pages and outputs PNGs to an __inbox directory along with a summary.json detailing results.

Can I capture a subset of pages instead of all manual pages at once?

Yes, you can capture a subset of pages by passing the --pages argument with a specific page count to the capture script. You can also use the --base-url argument to target a custom dev server URL for capturing pages.

Does Playwright work well for batch capturing screenshots at 2000x1600 resolution?

Playwright is used as the runtime dependency to batch capture screenshots at 2000x1600 high resolution. It automates browser navigation across all manual pages and ensures consistent high-fidelity rendering for visual translation verification.

What is the best way to verify layout consistency across multi-page manuals?

The best way to verify layout consistency is to batch capture high-resolution PNG screenshots of all manual pages and review them visually. The skill organizes outputs under an __inbox directory and generates a summary.json file detailing capture results for tracking.

Why do I need a running dev server to capture manual page screenshots?

You need a running dev server to capture manual page screenshots because the Playwright script navigates to live URLs to render and capture the pages accurately. A custom base URL can be specified to point the script to the correct local or remote server environment.