screenshot

Capture full desktops, application windows, or custom pixel regions across macOS, Linux, and Windows.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill screenshot-pear-commerce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: screenshot
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/screenshot
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill screenshot-pear-commerce

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires swift, scrot, gnome-screenshot, imagemagick, xdotool, powershell, and includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the hassle of manually looking up OS-specific screenshot commands and handling inconsistent capture workflows, making it easy to reliably capture full desktops, specific application windows, or custom pixel regions across macOS, Linux, and Windows.

Core Features & Use Cases

  • Cross-platform capture support: Take full-screen, app/window-specific, or pixel-region screenshots on any major desktop operating system.
  • Automated permission handling: Pre-flight checks for macOS Screen Recording permissions reduce repeated system prompts.
  • Flexible output options: Save screenshots to user-specified paths, OS default locations, or temporary directories for AI visual inspection.
  • Use Case: When comparing a Figma design to its implemented build, use this Skill to capture the running app window automatically, with all permission and OS-specific handling managed for you.

Quick Start

Ask the AI to capture a screenshot of your active application window and save it to a temporary folder for you to review.

Frequently Asked Questions about screenshot

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

FAQPage Schema
How do I capture a screenshot of a specific application window across different operating systems?

Capturing a screenshot of an application window across operating systems requires a unified workflow that automatically handles OS-specific commands and permissions for macOS, Linux, and Windows. This allows reliable full desktop, app window, or pixel region captures without manual command lookup.

Does taking a desktop screenshot on macOS require manual screen recording permission handling?

Taking a desktop screenshot on macOS does not require manual screen recording permission handling if using an automated workflow. Pre-flight checks reduce repeated system prompts by managing macOS Screen Recording permissions automatically before capturing the screen.

What is the best way to automate window capture for visual debugging and design-to-build comparison?

The best way to automate window capture for visual debugging and design-to-build comparison is to use a cross-platform workflow that captures the running app window and saves the output to a specified path, managing all OS-specific handling and permissions for you.

Can I save screenshots to a temporary directory for AI visual inspection tasks?

You can save screenshots to a temporary directory for AI visual inspection tasks. Flexible output options allow you to direct captures to user-specified paths, OS default locations, or temporary folders, satisfying the functional requirements of automated visual inspection.

Why does multi-display screenshot capture fail when using inconsistent OS commands?

Multi-display screenshot capture fails with inconsistent OS commands due to varying system APIs and missing permission checks. A unified cross-platform workflow resolves this by abstracting OS-specific commands and applying automated multi-display support across macOS, Linux, and Windows.