product-screenshots

Automates product screenshot capture and maintenance via Playwright and a registry.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/mdmagnuson-creator/yo-go --skill product-screenshots
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-screenshots
Source: https://github.com/mdmagnuson-creator/yo-go/tree/main/skills/product-screenshots
Command: npx skills add https://github.com/mdmagnuson-creator/yo-go --skill product-screenshots

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintaining up-to-date, consistent product visuals across marketing pages and support articles is labor-intensive and error-prone; this skill automates capturing and maintaining screenshots to ensure assets stay current after UI changes.

Core Features & Use Cases

  • Automated screenshot capture using Playwright to render pages at defined viewports and themes.
  • Registry-driven workflow that tracks, stores, and references screenshots for marketing and support.
  • Easy integration with marketing and support workflows by providing ready-to-use image assets and provenance.

Quick Start

Invoke the screenshot maintainer with a target URL and viewport to capture a new screenshot and update the registry.

Frequently Asked Questions about product-screenshots

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

FAQPage Schema
How do I automate capturing product screenshots for marketing pages after a UI refresh?▼

Automate product screenshot capture by defining a capture workflow with Playwright to render target URLs at specified viewports and themes, then storing the results in a centralized registry to keep marketing assets current after UI changes.

What's the best way to maintain up-to-date UI screenshots for support documentation?▼

Maintain support documentation screenshots using a registry-driven workflow that tracks, stores, and references captured UI visuals, ensuring assets stay consistent and current without manual intervention after interface updates.

Can I capture screenshots at different viewports and themes using Playwright?▼

Yes, screenshot capture using Playwright renders pages at defined viewports and themes, allowing you to capture consistent product visuals across multiple display configurations for marketing and support use.

How does a screenshot registry help manage visual assets for feature launches?▼

A screenshot registry tracks, stores, and references captured product visuals, providing ready-to-use image assets with provenance for feature launches, ensuring marketing and support teams access the latest updated screenshots.

What do I need to set up before automating product screenshot capture?▼

Before automating product screenshot capture, you need a defined capture workflow specifying target URLs and viewports, along with a centralized screenshot registry to store and reference the captured marketing and support assets.

Why does maintaining product visuals manually lead to outdated marketing screenshots?▼

Maintaining product visuals manually is labor-intensive and error-prone because UI changes require updated visuals across marketing pages and support articles, making it difficult to ensure all assets stay current without automation.