wt-screenshot-frames

Batch-captures screenshots from structured placeholders in Markdown blog series using Playwright and Microsoft Edge.

1|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/Sampi314/Sam-Plugin-Marketplace --skill wt-screenshot-frames
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wt-screenshot-frames
Source: https://github.com/Sampi314/Sam-Plugin-Marketplace/tree/main/Writing%20Tools/skills/wt-screenshot-frames
Command: npx skills add https://github.com/Sampi314/Sam-Plugin-Marketplace --skill wt-screenshot-frames

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill eliminates the hours of manual work required to capture screenshots for multi-part blog series, where each post contains dozens of structured placeholder blocks specifying the target URL, image subject, and save filename for each screenshot.

Core Features & Use Cases

  • Automated Placeholder Parsing: Scans all markdown files in a blog series folder to extract screenshot placeholder blocks into a structured JSON manifest, skipping non-screenshot types handled by other tooling.
  • Progress Tracking: Generates a markdown checklist grouped by blog part to track which screenshots are already captured and which are pending.
  • Interactive Batch Capture: Uses Playwright to open each screenshot URL in Microsoft Edge, lets you adjust zoom, scroll position, and login state, then saves the viewport to the correct per-part folder with the specified filename.
  • Use Case: For a 61-part technical blog series like "The Analyst's Guide to GitHub" with hundreds of screenshot placeholders, this skill reduces manual screenshot work to a single streamlined interactive session.

Quick Start

Use the wt-screenshot-frames skill to batch capture all screenshot placeholders from your blog series folder, saving each image to the correct per-part directory with the specified filename.

Frequently Asked Questions about wt-screenshot-frames

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

FAQPage Schema
How do I automate batch screenshot capture for a multi-part blog series?

Batch screenshot capture for a blog series is automated by parsing structured placeholder blocks in markdown files and interactively capturing viewport screenshots via Playwright, saving each image to the correct per-part folder.

Can I use Playwright with Microsoft Edge to interactively adjust viewport screenshots?

Yes, Playwright opens each target URL in Microsoft Edge, allowing you to manually adjust zoom levels, scroll positions, and login states before saving the viewport screenshot.

How do I extract screenshot URLs and filenames from markdown placeholders?

Markdown placeholder blocks specifying screenshot URLs, subjects, and target filenames are automatically parsed into a structured JSON manifest, while skipping non-screenshot placeholder types handled by separate tooling.

Do I need Python 3.10+ and Playwright to run screenshot automation for technical writing?

Yes, running this screenshot automation requires Python 3.10 or higher, Playwright, and Microsoft Edge to execute the interactive runner that captures and saves viewport screenshots.

What is the best way to track screenshot progress across a long-form technical blog workflow?

Progress tracking is handled by generating a markdown checklist grouped by blog part, allowing you to monitor which screenshots are already captured and which remain pending.

Are there limitations when batch capturing blog screenshots with structured placeholders?

This tool only processes structured screenshot placeholders and skips non-screenshot placeholder types, meaning non-screenshot image blocks must be handled by separate tooling.