screen

Capture region screenshots and store them in a structured local library.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bosmadev/claude --skill screen-bosmadev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: screen
Source: https://github.com/bosmadev/claude/tree/main/skills/screen
Command: npx skills add https://github.com/bosmadev/claude --skill screen-bosmadev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Capturing and organizing visuals quickly can be tedious and error-prone; this skill streamlines region-based screenshot capture, storage, and lightweight management for bug reports, UI references, and design reviews.

Core Features & Use Cases

  • Capture region screenshots on demand and store them in a structured local library.
  • List, analyze, delete, and clean old screenshots to maintain an organized repository.
  • Use cases include bug reporting, UI references, and progress tracking during development.

Quick Start

Capture a region screenshot using the /screen command.

Frequently Asked Questions about screen

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

FAQPage Schema
How do I automate screenshot capture for bug reporting?

You can automate screenshot capture for bug reporting by triggering a command to grab specific UI regions and save them locally. This streamlines visual documentation by organizing captured UI states into a structured library for easy retrieval.

Can I capture a specific UI region for documentation without saving the whole screen?

Yes, capturing a specific UI region for documentation instead of the whole screen is supported. The skill executes region-based screenshot capture, allowing you to isolate exact UI elements for references and design reviews while storing them locally.

How do I manage and clean up old screenshots in my local library?

Managing and cleaning up old screenshots involves using built-in script operations to list, analyze, and delete stored captures. This maintains an organized repository by safely removing outdated UI references and bug replications through safety-guided deletion.

Does the screenshot capture process require external dependencies?

No, the screenshot capture process requires zero external dependencies. It operates entirely through managed local script operations, ensuring user control and recoverability without needing to install additional software libraries or frameworks.

What is the best way to track UI progress during development?

The best way to track UI progress during development is by capturing on-demand region screenshots into a structured local library. This allows you to compare UI states over time, directly complementing your bug replication and visual documentation workflows.