take-screenshot

Capture screenshots from a connected Android device via ADB.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/danielrosehill/Claude-ADB-Ops-Plugin --skill take-screenshot-danielrosehill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: take-screenshot
Source: https://github.com/danielrosehill/Claude-ADB-Ops-Plugin/tree/main/skills/take-screenshot
Command: npx skills add https://github.com/danielrosehill/Claude-ADB-Ops-Plugin --skill take-screenshot-danielrosehill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture screenshots from a connected Android device to quickly document app behavior, bugs, or sharing device state.

Core Features & Use Cases

  • Direct host capture to avoid on-device writes using adb
  • Respect workspace mappings for screenshots when available; otherwise fall back to a sensible default path (e.g., ~/Pictures/Phone/Screenshots)
  • Works with a single device or multiple authorized devices; provides a straightforward flow for repeated captures

Quick Start

Capture a screenshot from a connected Android device to your local machine.

Frequently Asked Questions about take-screenshot

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

FAQPage Schema
How do I capture an Android screenshot using ADB?

Android screenshots are captured directly to the host machine via ADB, avoiding on-device file writes entirely. This enables rapid visual debugging, bug reporting, and documentation by pulling the screen buffer from a USB-connected device straight to your local file system.

Do I need a USB connection to take Android screenshots with ADB?

Yes, ADB screenshot capture requires a USB-connected and authorized Android device. The host machine must have ADB installed to pull the screen buffer directly, facilitating quick visual state checks for debugging or documentation without saving files on the device.

Where are Android screenshots saved when captured via ADB?

ADB screenshots default to saving under ~/Pictures/Phone/Screenshots/ on the host machine. If a 'screenshots' mapping exists in workspace/mappings.yaml, the capture process respects that custom path, organizing images for debugging and documentation efficiently.

Can I capture screenshots from multiple Android devices in the same session?

Yes, this ADB capture method supports a single device or multiple authorized devices. It provides a straightforward flow for repeated captures across multiple sessions, making it ideal for continuous debugging, bug reporting, and documentation workflows.

Why use ADB for Android screenshots instead of on-device capture?

Using ADB for Android screenshots avoids on-device file writes by pulling the screen buffer directly to the host machine. This approach streamlines debugging and bug reporting by saving images immediately to a local directory without cluttering the device's internal storage.