page-screenshotter

Capture application pages and map features to pages in pages_manifest.json.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Swear4/agent_rules --skill page-screenshotter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: page-screenshotter
Source: https://github.com/Swear4/agent_rules/tree/main/agent-universal/skills/page-screenshotter
Command: npx skills add https://github.com/Swear4/agent_rules --skill page-screenshotter

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the capture of all application pages and establishes a static mapping from features to their corresponding pages, enabling a complete pages manifest for QA, analytics, and marketing workflows.

Core Features & Use Cases

  • Capture all pages in web or mobile apps and produce a pages_manifest.json.
  • Enrich features.json with a pages[] field to show where each feature is accessible.
  • Generate a consistent, slug-based output per page and provide deterministic artifacts for downstream tools.

Quick Start

Run the page-screenshotter skill to capture all capturable pages, map features to their pages, and generate a pages_manifest.json for downstream tooling.

Frequently Asked Questions about page-screenshotter

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

FAQPage Schema
How do I automate capturing screenshots of all application pages for QA testing?▼

This Skill automates capturing application pages by generating a deterministic pages_manifest.json file, mapping features to their respective pages for end-to-end QA and marketing readiness.

Does Playwright support full-page screenshot capture for both web and mobile apps?▼

Yes, Playwright is used by this Skill to perform deterministic full-page capture for both web and mobile apps, generating slug-based outputs and optional artifact hosting for downstream workflows.

What is the best way to map application features to their corresponding pages?▼

The best way to map features to pages is using this Skill to enrich your features.json file with a pages[] field, establishing a static mapping that shows exactly where each feature is accessible.

How do I generate a pages manifest for downstream analytics workflows?▼

You generate a pages manifest by running this Skill during Phase 5 of the audit pipeline, which captures all capturable pages and outputs a structured pages_manifest.json for downstream analytics tooling.

Can I use automated screenshots to prepare marketing assets for my web app?▼

Yes, you can use this Skill to capture all pages of your web app, producing deterministic full-page screenshots and slug-based artifacts suitable for marketing readiness and downstream asset generation.

What are the limitations of automating screenshots for complex application states?▼

This Skill handles deterministic full-page capture and slug generation for captable pages, but mapping features to pages requires a baseline features.json to properly enrich with accessible page data.