screenshot

Capture screenshots of application windows

16 stars

Best use case

screenshot is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Capture screenshots of application windows

Teams using screenshot should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/screenshot/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/development/screenshot/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/screenshot/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How screenshot Compares

Feature / AgentscreenshotStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Capture screenshots of application windows

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Screenshot Skill

Capture screenshots of macOS application windows using ScreenCaptureKit.

## Usage

```bash
shotty <command> [options]
```

## Commands

| Command | Description |
|---------|-------------|
| `capture <app\|pid> [output.png]` | Screenshot an app's window(s) |
| `list` | List all capturable windows |
| `list-apps` | List running applications |

## Options

| Flag | Description |
|------|-------------|
| `--all` | Capture all windows (not just first) |
| `--json` | Output as JSON |
| `--no-frame` | Exclude window frame/shadow |

## When to Use

- User asks to "screenshot this conversation" or "capture this window"
- User wants visual verification of UI changes
- User needs to document current application state
- User asks to see what an app looks like

## Examples

Screenshot the current terminal:
```bash
shotty capture Ghostty /tmp/terminal.png
```

Screenshot a browser:
```bash
shotty capture Safari ~/Desktop/browser.png
```

Screenshot by PID:
```bash
shotty capture 12345 output.png
```

List available apps:
```bash
shotty list-apps
```

Capture all windows of an app:
```bash
shotty capture "VS Code" --all
```

## Workflow

1. If user doesn't specify an app, use `list-apps` to find the right target
2. Run `capture` with the app name or PID
3. Use the `Read` tool to view the resulting PNG and verify the capture
4. Report the file path to the user

## Notes

- Requires Screen Recording permission (System Settings → Privacy & Security → Screen Recording)
- App names are matched case-insensitively with substring support
- Default output is `screenshot.png` in current directory
- Use `--no-frame` for cleaner captures without window shadow

Related Skills

screenshots

16
from diegosouzapw/awesome-omni-skill

Generate marketing screenshots of your app using Playwright. Use when the user wants to create screenshots for Product Hunt, social media, landing pages, or documentation.

update-screenshots

16
from diegosouzapw/awesome-omni-skill

Download screenshot baselines from the latest CI run and commit them. Use when asked to update, accept, or refresh component screenshot baselines from CI, or after the screenshot-test GitHub Action reports differences. This skill should be run as a subagent.

android-screenshot-automation

16
from diegosouzapw/awesome-omni-skill

Setup automated screenshot capture for Play Store using Fastlane Screengrab

bgo

10
from diegosouzapw/awesome-omni-skill

Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.

Coding & Development

swift-human-guidelines

16
from diegosouzapw/awesome-omni-skill

Comprehensive Swift 6 and SwiftUI development guidelines for building iOS 26, iOS 18, iPadOS, macOS, watchOS, visionOS, and tvOS applications. Covers Foundation Models API, BGContinuedProcessingTask, Call Translation API, Liquid Glass design system, data-race safety, typed throws, synchronization primitives, SwiftUI/UIKit interoperability, zoom transitions, and document-based apps. Use when building new Apple platform apps, implementing Apple Intelligence features, optimizing performance with Swift 6 concurrency, following Apple Human Interface Guidelines, creating cross-platform applications, or working with iOS 26/18 APIs. Triggers on Swift code, SwiftUI views, Xcode projects, app architecture, background processing, translation features, Foundation Models, synchronization, actors, Sendable types, or modern Apple platform development.

swift-conventions

16
from diegosouzapw/awesome-omni-skill

Swift coding conventions and best practices for modern Swift development. Use when writing, reviewing, or refactoring Swift code to ensure consistency with naming conventions, access control, async/await patterns, and SwiftUI/framework best practices.

swift-concurrency

16
from diegosouzapw/awesome-omni-skill

Expert guidance on Swift Concurrency best practices, patterns, and implementation. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) concurrent code architecture or performance optimization, (8) concurrency-related linter warnings (SwiftLint or similar; e.g. async_without_await, Sendable/actor isolation/MainActor lint).

swedish-medications

16
from diegosouzapw/awesome-omni-skill

Look up Swedish medication information from FASS (Farmaceutiska Specialiteter i Sverige). Use when users ask about medications, drugs, läkemedel, dosages, side effects (biverkningar), interactions, or need to understand prescriptions in Sweden. Covers all medications approved for use in Sweden.

swe-programming-elixir-phoenix

16
from diegosouzapw/awesome-omni-skill

Phoenix Framework coding standards from authoritative docs/explanation/software-engineering/platform-web/tools/elixir-phoenix/ documentation

sw-tech-stack-planner

16
from diegosouzapw/awesome-omni-skill

Use when user wants a tech stack recommendation, technology choices, docker-compose setup, or architecture decisions for a software project – reads vision.md, user-stories.md, use-cases.md and generates requirements/tech-stack.yaml silently.

sveltekit

16
from diegosouzapw/awesome-omni-skill

Expert guidance for building modern, performant web applications with SvelteKit.

sveltekit-latest

16
from diegosouzapw/awesome-omni-skill

Quick-reference for SvelteKit + Svelte 5 development (Feb 2026)