screenshot-handling

Save screenshots to a dedicated screenshots/ directory with automated folder creation.

2|Updated Feb 13, 2026

Search Tags:#automation #testing #project management #screenshots #organization #visual assets

Ready to run

npx skills add https://github.com/pmarashian/cursor-agent-skills --skill screenshot-handling

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: screenshot-handling
Source: https://github.com/pmarashian/cursor-agent-skills/tree/main/screenshot-handling
Command: npx skills add https://github.com/pmarashian/cursor-agent-skills --skill screenshot-handling

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents clutter in your project root by ensuring all screenshots are automatically saved to a dedicated screenshots/ folder.

Core Features & Use Cases

Enforced Directory: Guarantees screenshots are never saved to the project root.
Automated Folder Creation: Creates the screenshots/ directory if it doesn't exist.
Use Case: When using tools like agent-browser, Playwright, or Puppeteer, this skill ensures all captured images are neatly organized, maintaining a clean project structure.

Quick Start

Use the screenshot-handling skill to capture a screenshot named 'mainmenu-verification.png' and save it to the 'screenshots/' directory.

Frequently Asked Questions about screenshot-handling

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

FAQPage Schema

How do I stop Playwright and Puppeteer screenshots from cluttering my project root?▼

To stop screenshots from cluttering your project root, enforce saving all captured images to a dedicated 'screenshots/' directory. This prevents visual assets from being saved in the root and automatically creates the required folder if it doesn't exist.

What is the best way to organize visual assets generated during automated testing?▼

The best way to organize visual assets generated during automated testing is to enforce a dedicated 'screenshots/' directory. This guarantees images from capture tools are neatly organized, maintaining a clean project structure and improving asset discoverability.

Does this screenshot organization approach work with agent-browser capture methods?▼

Yes, this screenshot organization approach works with agent-browser, Playwright, and Puppeteer. It provides clear guidelines for various capture methods, ensuring all images are automatically routed to the correct folder regardless of the tool used.

How do I automate folder creation for saving automated testing screenshots?▼

To automate folder creation for saving testing screenshots, use a skill that enforces a 'screenshots/' directory. It automatically creates the required folder if it doesn't exist before saving files, preventing missing directory errors.

Why are my Puppeteer screenshots saved in the project root instead of a dedicated folder?▼

Puppeteer screenshots are saved in the project root because a dedicated output path is not enforced. Without automated routing to a 'screenshots/' directory, the capture tool defaults to the current working directory, causing clutter.