/screenshot
Capture and analyze macOS screenshots. Trigger with "take a screenshot", "capture screen", "screenshot".
$ npx -y skills add wasabeef/claude-code-cookbook --skill screenshot --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/screenshot
Context preview
The summary Claude sees to decide when to auto-load this skill.
Capture and analyze macOS screenshots. Trigger with "take a screenshot", "capture screen", "screenshot".
SKILL.md
screenshot.SKILL.mddescription: 'Capture and analyze macOS screenshots. Trigger with "take a screenshot", "capture screen", "screenshot".'
allowed-tools:
- Bash(screencapture *)
Capture and analyze macOS screenshots
Capture screenshots on macOS and analyze the images.
Usage
/screenshot [options]
Options
- None: Select window (Claude will confirm options)
- `--window`: Capture a specific window
- `--full`: Capture the entire screen
- `--crop`: Select a region to capture
Basic Examples
# Capture and analyze a window
/screenshot --window
"Analyze the captured screen"
# Select a region and analyze
/screenshot --crop
"Explain the content of the selected region"
# Capture full screen and analyze
/screenshot --full
"Analyze the overall screen composition"
Collaboration with Claude
# No specific problem - situation analysis
/screenshot --crop
(Claude will automatically analyze screen content, explaining elements and composition)
# UI/UX problem analysis
/screenshot --window
"Propose problems and improvements for this UI"
# Error analysis
/screenshot --window
"Tell me the cause and solution for this error message"
# Design review
/screenshot --full
"Evaluate this design from a UX perspective"
# Code analysis
/screenshot --crop
"Point out problems in this code"
# Data visualization analysis
/screenshot --crop
"Analyze trends visible in this graph"
Detailed Examples
# Analysis from multiple perspectives
/screenshot --window
"Analyze this screen regarding:
1. UI consistency
2. Accessibility issues
3. Improvement proposals"
# Multiple captures for comparative analysis
/screenshot --window
# (Save before image)
# Make changes
/screenshot --window
# (Save after image)
"Compare before and after images, analyzing changes and improvement effects"
# Focus on specific elements
/screenshot --crop
"Evaluate whether the selected button design harmonizes with other elements"
Prohibited Items
- **Prohibited to say "captured" when no screenshot was taken**
- **Prohibited to attempt analysis of non-existent image files**
- **The `/screenshot` command does not actually capture screenshots**
Notes
- If no option is specified, please present the following choices:
"How would you like to capture the screenshot?
1. Select window (--window) → screencapture -W
2. Full screen (--full) → screencapture -x
3. Select region (--crop) → screencapture -i"
- Start image analysis after the user has executed the screencapture command
- Specifying specific problems or perspectives enables more focused analysis
Read more
description: 'Capture and analyze macOS screenshots. Trigger with "take a screenshot", "capture screen", "screenshot".' allowed-tools: - Bash(screencapture *)
Capture and analyze macOS screenshots
Capture screenshots on macOS and analyze the images.
Usage
/screenshot [options]
Options
- None: Select window (Claude will confirm options)
- `--window`: Capture a specific window
- `--full`: Capture the entire screen
- `--crop`: Select a region to capture
Basic Examples
# Capture and analyze a window /screenshot --window "Analyze the captured screen" # Select a region and analyze /screenshot --crop "Explain the content of the selected region" # Capture full screen and analyze /screenshot --full "Analyze the overall screen composition"
Collaboration with Claude
# No specific problem - situation analysis /screenshot --crop (Claude will automatically analyze screen content, explaining elements and composition) # UI/UX problem analysis /screenshot --window "Propose problems and improvements for this UI" # Error analysis /screenshot --window "Tell me the cause and solution for this error message" # Design review /screenshot --full "Evaluate this design from a UX perspective" # Code analysis /screenshot --crop "Point out problems in this code" # Data visualization analysis /screenshot --crop "Analyze trends visible in this graph"
Detailed Examples
# Analysis from multiple perspectives /screenshot --window "Analyze this screen regarding: 1. UI consistency 2. Accessibility issues 3. Improvement proposals" # Multiple captures for comparative analysis /screenshot --window # (Save before image) # Make changes /screenshot --window # (Save after image) "Compare before and after images, analyzing changes and improvement effects" # Focus on specific elements /screenshot --crop "Evaluate whether the selected button design harmonizes with other elements"
Prohibited Items
- **Prohibited to say "captured" when no screenshot was taken**
- **Prohibited to attempt analysis of non-existent image files**
- **The `/screenshot` command does not actually capture screenshots**
Notes
- If no option is specified, please present the following choices:
"How would you like to capture the screenshot? 1. Select window (--window) → screencapture -W 2. Full screen (--full) → screencapture -x 3. Select region (--crop) → screencapture -i"
- Start image analysis after the user has executed the screencapture command
- Specifying specific problems or perspectives enables more focused analysis
A collection of commands, roles, and automation scripts for Claude Code. Automate your workflow without unnecessary confirmations, allowing you to focus on what matters.
Repo: wasabeef/claude-code-cookbook
Other skills on claude-code-cookbook.
- /analyze-dependencies
Analyze project dependencies and evaluate architectural health. Trigger with "analyze dependencies", "detect circular dependencies", "architecture issues?", "check module coupling", "find layer violations". Generates dependency matrix, fan-in/fan-out analysis, and prioritized
Open skill - /analyze-performance
Performance analysis based on Core Web Vitals with UX scoring. Trigger with "analyze performance", "improve speed", "check Core Web Vitals", "page speed", "improve LCP", "identify performance issues".
Open skill - /check-fact
Verify information accuracy against codebase and documentation. Trigger with "is this correct?", "fact check", "verify this", "is this accurate?".
Open skill - /check-prompt
Evaluate and improve AI prompt quality. Trigger with "check this prompt", "evaluate prompt quality", "improve this prompt".
Open skill - /commit-message
Generate commit messages from staged changes. Trigger with "suggest commit message", "generate commit message", "what should the commit say?", "write commit message".
Open skill - /context7
Search technical documentation via Context7 MCP. Trigger with "check the docs", "look up documentation", "how to use this library?", "API reference".
Open skill

